# TELIP 18: Y3 Supplementary TAO Allocation, Funding Operations to Year End

- Space: [Telcoin Platform Council](https://snapshot.box/s:telcoinplatformcouncil.eth.md)
- Author: 0x20422E99303E9Fc438f1ce733E97E780a9877851
- State: Passed
- Voting type: Basic
- Start: 2026-10-09 09:26 UTC
- End: 2026-10-16 09:26 UTC
- Votes: 7
- Quorum: 8 voting power
- Discussion: https://forum.telcoin.org/t/telip-y3-supplementary-tao-allocation-funding-operations-to-year-end/873
- Open in Snapshot: https://snapshot.box/#/s:telcoinplatformcouncil.eth/proposal/0x436035d9e4dbee2dac28cc0426497457bd4afb38ef5dfc5e165f56dc09ec3e72

## Results

- For: 8 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

**Author:** Parker Spann, Executive Director, TAO

**Date:** October 2026

---

## Abstract

This TELIP requests a supplementary Year 3 allocation of up to 810,300,000 TEL from the TEL Treasury to the TAO Safe on Polygon. The allocation will settle invoices already due, finance the TAO's operating cost plan from October 1st to December 31st, 2026, and fund three core services that will put Telcoin Network in a strong position at mainnet launch.

The first is a dedicated public RPC service, giving developers, exchanges and partners fast and reliable access to the network from day one. The second is a native oracle, one of the most important pieces of infrastructure any network can have for financial services. It brings trusted price and market data on-chain, which DeFi applications, stablecoins and payment flows rely on to operate safely. The third is a wallet delivered as an SDK, built so that mobile network operators can embed Telcoin Network directly into their own super apps. This gives MNOs a simple route to offering digital asset services to the customers they already serve, and sits at the heart of Telcoin Network's distribution strategy. These services were not in the Year 3 budget. That budget was set before the mainnet architecture was final and before the Association had chosen how MNOs would reach the network. Three things became clear during the year. The bridge requires three independent RPC providers, which no single hosted provider could supply at acceptable cost. Lending, the DEX, and Digital Cash cannot run without an on-chain price source, and quotes for one ranged from approximately \$60,000  to \$1,500,000 a year. Specification 2 gives the Association an oracle of its own, which it controls and can charge others to use, rather than a service it rents. Mobile money operators asked for a way to embed Telcoin Network in their own apps rather than send subscribers to a third-party wallet. The engagement in Specification 2 answers all three at a fixed \$100,000, with the Association owning the code and earning a share of the revenue.

The cost to be met is \$1,290,450, sized at \$0.0015 per TEL while TEL trades near \$0.0022, and reduced by the 50,000,000 TEL due under TELIP14. Of this, \$138,000 relates to a new engagement with a specialist service provider. It is set out separately in Specification 2 so the Councils can consider it as new spend in its own right.

The allocation is released in two tranches. The first, 433,700,000 TEL, is released on affirmation. The balance follows only once the TAO has published its first quarterly financial report and its November monthly finance summary, and is sized at the TEL price at the time of release, net of what the TAO then holds. Any unused TEL returns to the Treasury. The Q3 financial report goes to the Councils in full. A public summary is posted to the forum showing spend by category against authority and TEL and USDC on hand. Items that name counterparties or contract terms stay with the Councils.

A contingency of 10 percent of the October to December forecast, up to \$110,315 or 73,600,000 TEL, is also authorized. It remains in the Treasury and is drawn only if a cost exceeds its forecast, with notice given to the Councils.

The proposal explains how the Year 3 shortfall arose and adds four financial controls to the four already binding under the Exchange Integration TELIP. Apart from the new service engagement, it introduces no new expense category. It covers operations to year end only, and the Association's financing for Year 4 (2027) will be addressed in a separate proposal.

---

## Motivation

### Where the TAO stands

After settling the invoices due in September, the TAO's operating safes hold 29,479,971.14 TEL and 5,500 USDC. The August Telcoin, Inc. invoice was settled with the 137,500,000 TEL transferred under the Exchange Integration TELIP and is excluded here. The \$165,000 exchange integration allocation approved under the TEL Token Upgrade TELIP remains in the Treasury, is drawn to the TAO as exchange agreements are signed, and is shown as a commitment in Treasury After This Proposal.

The TAO Distribution Safe remains reserved for validator rewards and MNO installation. It holds 26,000,000 TEL and falls to about 12,000,000 TEL after September incentive payments to MNO validator nodes running in telecom data centres on testnet and to application developers prototyping on the network.

### Cost still to be met

| Costs billed in USD | USD |
| :---- | ----: |
| **Due at October 1st** |  |
| September network development and MNO installation invoice, Telcoin, Inc. | 177,479 |
| Reimbursable team expenses to September 30th | 9,823 |
| **Forecast, October 1st to December 31st** |  |
| Network development and MNO installation, Telcoin, Inc. (3 months) | 532,437 |
| Balance of the approved security audit programme with Cantina to mainnet for networking, key management, smart contracts | 226,000 |
| Website | 23,906 |
| TA  financial operations support | 32,385 |
| TAO financial operations support | 20,250 |
| STORM growth, BD, community management and strategic advisor | 68,100 |
| Escrow custody | 14,400 |
| Accounting and filing | 12,000 |
| Software tools | 174 |
| Settlement adjustment on Telcoin, Inc. invoices paid in TEL (services agreement, 95% of prior close) | 35,496 |
| \*\*RPC, oracle and wallet Specification 2\*\* |  |
| Build fee, first payment, invoiced on signing | 50,000 |
| Build fee, balance, on acceptance of the final milestone | 50,000 |
| Support, November and December | 20,000 |
| Infrastructure, November and December | 18,000 |
| **Total billed in USD** | **1,290,450** |
| **In TEL at \$0.0015** | **860,300,000 TEL** |

The Strategic Telecom Advisory engagement and the STORM engagement approved alongside it were authorized under TELIP14. The TELIP14 initial transfer of 50,000,000 TEL to the TAO has not yet been executed, and the TAO met the costs it was to cover from its own safes. When the transfer is executed under TELIP14 it replenishes those safes, and it is applied here against the costs above, reducing this request by 50,000,000 TEL. It is shown separately in [Treasury After This Proposal](?tab=t.0). The STORM growth, BD, community management and strategic advisory fees for October to December are included in the costs above.

| Requested | TEL |
| :---- | ----: |
| Costs billed in USD, at \$0.0015 | 860,300,000 |
| Less TELIP14 initial transfer, applied against the costs above | (50,000,000) |
| **Total transferred** | **810,300,000** |
| Contingency, 10% of the October to December forecast (\$110,315), held in the Treasury | 73,600,000 |
| **Maximum authorized** | **883,900,000** |

**How the shortfall arose**

At the Councils' request, this section sets out the factors behind the Year 3 shortfall. Four contributed.

**Price.** The Year 3 allocation sized 600,000,000 TEL against \$1,800,000 of costs at \$0.003 per TEL. Converting the full allocation at the start of the year would have meant selling 600,000,000 TEL into the market at once, so the TAO converted TEL only as invoices fell due, settled directly in TEL where possible, and placed contracts on monthly payment terms. That protected the market but left the dollar budget exposed to the price, and the plan held no buffer for a lower one. TEL closed below \$0.003 on 188 of 202 days to August 25th, and at the year's mean close of \$0.00235, 600,000,000 TEL funds about \$1,410,000 of the \$1,800,000 planned. Control 4, the budget standard, addresses this, and this proposal applies it with a contingency held in the Treasury.

**Scope.** Network development and MNO installation are forecast at about \$1.9 million against \$1,108,750 approved. As Telcoin Network moved toward mainnet, the full time team grew to 7 engineers and operators, and business development expanded to bring MNO validators and application developers to genesis. This work was essential to launch readiness, though the budget was not adjusted to reflect it.

**Budget structure.** The Councils approved two engagements with STORM: strategic marketing and communications in June 2025, and financial operations support in November 2025\. The marketing engagement was restructured under TELIP14 in April 2026\. The Year 3 budget carried a single \$130,000 line for both, which broadly matched the financial operations engagement alone, and TELIP14 described the restructured marketing fee as sitting within that same line. Every STORM invoice relates to work the Councils approved, so this was a budgeting error, and the line is expected to close about \$150,000 over. A further \$314,507 of 2026 spend, covering contractors, financial operations and reimbursements, falls outside the approved categories and is set out line by line in the Q3 financial report.

**Process.** The TAO's programme was managed against annual categories, without monthly reporting, a trigger when a category ran over, or a rule linking new engagements to available headroom. The bi-annual report committed in the Year 3 allocation was not delivered for the first half, and the overrun, which was visible by May, should have been raised with the Councils at that point. The four new controls in this proposal are designed to close each of these gaps.

As Executive Director, I take responsibility for these budgeting and reporting shortfalls and for putting the controls in place to prevent them recurring.

### What has already changed

The TAO moved the block explorer from DexGuru to OpRail, saving \$35,000.

For the RPC service mainnet needs, the TAO tested the market and chose not to proceed with a hosted engagement quoted at \$290,000 a year for RPC and data coverage. It has sourced RPC, a native oracle and a wallet for MNOs as set out below and in Specification 2\.

Four invoice controls took effect under the Exchange Integration TELIP, and the first quarterly financial report will be published in October 2026\.

### What mainnet still needs

Mainnet needs three services that were not in the Year 3 budget.

* **RPC service**: managed RPC for mainnet and testnet, with public and private endpoints and a dedicated endpoint for the bridge relayer, run as one of the independent providers the bridge requires.  
    
* **Native oracle**: the network's source of trusted prices. Lending markets use it to value collateral, the DEX to check prices, and wallets use it to show users what their assets are worth. It is owned by the Association and metered per request, so the Association sets its own pricing and can charge for it.  
    
* **Wallet**: a white-label wallet SDK that MNOs embed in their own super apps, with the subscriber's mobile number as their identity and no seed phrases or addresses shown to users. It is separate from the Telcoin Wallet, Telcoin, Inc.'s own consumer app. This is an Association-owned, white-label SDK that MNOs ship under their own brand to their own subscribers.

The TAO selected this partner for these reasons. It delivers all three services in a single engagement, built in parallel and supported 24/7 once live. The fees are fixed at \$100,000 to build and \$10,000 a month to operate, with infrastructure charged at cost. The Association owns everything that is built and can move any of the services to another operator on 30 days' notice, so it is never locked in to one vendor.

**Most importantly, both the oracle and the wallet come with a revenue share for the Association**. As MNOs integrate the wallet SDK into their super apps and projects across the network draw on the oracle, the Association earns a share of the revenue these services generate. That turns two pieces of essential mainnet infrastructure into ongoing income streams that grow with adoption, helping to offset the cost of the engagement over time and strengthening the Association's financial position well beyond launch. 

This is an exciting step for the collective: it is the point where the network the Councils have funded for three years becomes something an MNO can hand to its subscribers.

---

## Specification

### 1\. Supplementary Year 3 TAO Allocation

* **Description**: TEL to settle the invoices due at October 1st, 2026 and to deliver the TAO's operating cost plan to December 31st, 2026, net of everything financed under another authority.  
    
* **Expected Cost (USD)**: \$1,152,450  
    
* **Requested TEL Allocation**: 718,300,000 TEL, being 768,300,000 TEL @ \$0.0015/TEL, less the 50,000,000 TEL TELIP14 transfer. A contingency of up to 73,600,000 TEL, covering Specifications 1 and 2, is held in the Treasury and drawn only as set out under Implementation.  
    
* **Notes**: Two tranches, covering Specifications 1 and 2 together. Tranche 1 of 433,700,000 TEL funds everything through October: the amounts due at October 1st, October operations, the audit balance, website, and the first RPC, oracle and wallet build fee payment, net of the TELIP14 transfer. Tranche 2 funds November and December, up to 376,600,000 TEL, including support, infrastructure and the balance of the build fee, with its costs converted at the price prevailing at release, less what the TAO then holds. No change to any expense category or to any other Year 3 allocation.

---

### 2\. Telcoin Network Services

* **Description**: A fixed-fee build of an RPC service, a native oracle and a wallet SDK for Telcoin Network mainnet, followed by 24/7 hosting, operation and support.   
    
* **Expected Cost (USD)**: \$138,000 to December 31st, 2026: the full \$100,000 build fee, of which \$50,000 is invoiced on signing and payable within 15 business days and the remaining \$50,000 on acceptance of the final milestone; \$20,000 of support for November and December; and \$18,000 of infrastructure for November and December.  
    
* **Requested TEL Allocation**: 92,000,000 TEL @ \$0.0015/TEL  
    
* **Notes**: Creates the expense category Telcoin Network Services, with an authority of \$138,000 for 2026\. Infrastructure is budgeted at the midpoint of the indicative range of \$2,900 to \$15,100 a month; any overrun is reported under the variance trigger in Specification 3\. Support and the Managed Services fee begin at the Service Commencement Date, the earlier of mainnet go-live and 60 days after acceptance of the final milestone for the RPC and oracle, so November and December are budgeted assumptions. Any part of the build fee not due by December 31st, 2026 is not drawn and is carried into the Association's 2027 financing proposal together with support and infrastructure from January.

| Service | Build fee (USD) | Support (USD/month) |
| :---- | ----: | ----: |
| RPC service | 35,000 | 3,000 |
| Native oracle | 25,000 | 3,000 |
| Wallet | 40,000 | 4,000 |
| **Total** | **100,000** | **10,000** |

---

### 3\. Financial Controls

Four controls already bind every network development invoice under the Exchange Integration TELIP: supporting detail mapping each charge to workstreams and deliverables, two-party approval within ten business days, settlement on approval, and a quarterly financial report to the Councils. This proposal adds four, effective on affirmation and applying to all TAO spend:

1. **Monthly finance summary.** By the 15th of each month, the TAO posts to the Councils its TEL and USDC on hand, spend for the month and year to date by category against authority, invoices received, approved, and paid, and runway in months at the trailing 30-day price.  
     
2. **Variance trigger.** When any category is forecast to exceed its authority by more than 10 percent or \$25,000, whichever is lower, the TAO notifies the Councils within 15 days with the cause and a plan. Spend beyond authority in that category requires Council approval.  
     
3. **Engagement authorization.** The TAO signs no new engagement unless it maps to a category with headroom, carries its own TELIP, or has Council approval.  
     
4. **Budget standard.** Every future TAO allocation is budgeted in USD, uses a planning assumption no higher than the trailing 90-day average close, carries an explicit contingency line, and shows runway at three price scenarios.

---

## Rationale

**It finishes what the Councils approved.** Every line in Specification 1 is a cost the Councils already authorized in kind. Where a category is already over its authority, affirmation of this proposal is the Council approval control 2 required for October to December spend.

**It buys what mainnet still needs on terms the Association controls.** A fixed fee buys three production services, the Association owns all of it, and it can change operator on 30 days' notice.

**It draws only what is needed.** The planning assumption sits well below the market price, Tranche 2 is sized at the price prevailing when it is released, and unused TEL returns. At \$0.0018 the costs need about 666,900,000 TEL; at \$0.0021 about 564,500,000. Tranche 1 is fixed at the planning assumption, so if TEL trades higher it leaves a surplus. Tranche 2 counts what the TAO already holds, so that surplus reduces Tranche 2 and stays in the Treasury. The contingency stays in the Treasury unless a cost overruns, and any of it not drawn never leaves.

**It is gated on accountability.** Tranche 2 is released only after the Q3 financial report and the November monthly finance summary are published. The Councils see the controls working before the balance of the TEL leaves the Treasury.

**The alternative is worse.** Unpaid invoices for the team hardening mainnet and installing MNO validators, and an unfinished audit programme, are a delivery risk at the point where delivery matters most. Launching without Association-controlled RPC, without on-chain prices and without a wallet MNOs can embed would leave the network ready and its users without a way in.

**Feasibility.** Both transfers are standard Treasury to TAO Safe executions. The TAO converts TEL to settle each invoice on approval, as the existing controls require.

**Sustainability.** The table below shows what this proposal leaves uncommitted in the Treasury entering 2027, stated here so the Councils weigh it now rather than discover it in January. A mainnet year will cost more than any year before it, and at current prices the Treasury's remaining inventory cannot carry it. That is why the Association's financing from 2027, including RPC, oracle, and wallet commitments, is brought as a separate proposal, built on the budget standard in control 4\. That proposal will treat 2027 as a question of both scope and sources rather than a routine allocation, set out every option considered and the one recommended, and come to the forum ahead of mainnet or any 2027 cost falling due.

---

## Treasury After This Proposal

|  | TEL |
| :---- | ----: |
| Available for allocation, as published October 5th | 1,191,585,758.02 |
| Less TEL Token Upgrade TELIP, exchange integration allocation (\$165,000 at \$0.0015), not yet transferred | (110,000,000.00) |
| Less TELIP14 initial transfer, authorized | (50,000,000.00) |
| Less this proposal, maximum | (810,300,000.00) |
| Less TEL V3 trading liquidity, 5% cost | (16,666,666.65) |
| Less contingency, held in the Treasury, maximum | (73,600,000.00) |
| **Uncommitted entering 2027** | **131,019,091.37**  |

The 333,333,333 TEL trading liquidity allocation is not an expense: the Association retains 95% of its value, and the 5% cost is shown above. It cannot be allocated while it is deployed, and its deployment is sequenced so that no commitment ever exceeds available TEL. The Treasury also holds 5,000,000,000 TEL under existing agreements, which is not available for operations. This request, including the contingency, is about 14 percent of the Treasury's 6,191,585,758 TEL and about 74 percent of the TEL available for allocation.

---

## Implementation

**Tranche 1\.** Upon affirmation, 433,700,000 TEL is transferred from the TEL Treasury to the TAO Safe on Polygon, and the transaction hash is published to this thread.

After the Compliance Council veto window closes, the Association executes the Master Services Agreement and Order Form No. 1 and the TAO pays the first \$50,000 build fee payment, invoiced on signing and payable within 15 business days, from Tranche 1\. The TAO reports each milestone acceptance, and the confirmed infrastructure estimate, in its monthly finance summary.

**Tranche 2\.** No earlier than November 15th, 2026, and only after the Q3 financial report and the November monthly finance summary are published, the TAO posts the November and December USD forecast, including RPC, oracle, wallet, infrastructure, and any build fee payments falling due on acceptance, and the 14-day average closing price on CoinGecko to this thread. The Treasury then transfers the USD forecast, less the value of the TEL and USDC then held in the TAO's operating safes, net of invoices received and not yet paid, divided by that price, capped at 376,600,000 TEL.

**Controls.** The four controls in Specification 3 take effect on affirmation.

**Contingency**. The contingency is not transferred with either tranche. If a category is forecast to run over, the TAO gives the notice required by control 2, stating the category, the cause and the amount, and posts the 14-day average closing price on CoinGecko to this thread. The Treasury then transfers that amount divided by that price, with all draws together capped at 73,600,000 TEL. A draw notified this way is the Council approval control 2 requires, up to that cap. Any part of the contingency not drawn by the earlier of the first 2027 TAO allocation and March 31st, 2027 lapses.

**Return of unused TEL.** Any balance of this allocation unspent at the earlier of the first 2027 TAO allocation and March 31st, 2027 returns to the TEL Treasury and is reported as returned.

**No change to other allocations.** This proposal makes no change to the Telcoin Network, TELx, TAN, or Council Member allocations for Year 3\. The TELIP14 transfer is executed under TELIP14, no later than Tranche 1, and applied as set out above.

### Transfers

| Safe | Tranche 1 | Tranche 2 (maximum) | Total (maximum) |
| :---- | ----: | ----: | ----: |
| TAO Safe (Polygon) | 433,700,000 TEL | 376,600,000 TEL | 810,300,000 TEL |

The contingency of up to 73,600,000 TEL is held in the Treasury and transferred only as drawn.

---

## Next Steps

1. Community review and discussion in the TELIP forum channel.  
     
2. Platform Council Snapshot, requiring 6 out of 8 approval within 120 hours.  
     
3. Upon Platform Council affirmation, Treasury Council Snapshot, requiring 4 out of 4 approval within 72 hours.  
     
4. A 72 hour Compliance Council veto window.  
     
5. Execution of Tranche 1 and publication of the transaction hash to this thread.  
     
6. Execution of the RPC, oracle and wallet agreement and the first build fee payment.  
     
7. Documentation of the affirmed proposal in the TELIP documentation section on Telcoin.org.

---

## Concluding Remarks

This proposal pays for work the Councils approved, at a price that holds, with the balance released only after the reporting the Councils asked for is in their hands. It brings the one new engagement it contains to the Councils before it is signed, with every commitment that follows from it on the table. It says how the shortfall happened and who owns it, and it puts the controls that prevent a repeat on the record. Year 3 ends funded, and mainnet launches with the services its users need. The question of how the Association finances mainnet and the years after it comes next, separately, on the same standard.

TEL The World,

Parker Spann

Executive Director, TAO

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

