# Doxa proposes to evolve the collateral architecture of DoxaUSD from ckUSDC **URL:** \ **Category:** SNS Framework\ **Tags:** Discussing, sns\ **Created:** [September 22, 2026, 6:37pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751 "2026-09-22T18:37:24Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![DoxaFoundation](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/doxafoundation/32/40305_2.png) [@DoxaFoundation](https://forum.dfinity.org/u/DoxaFoundation)\ **Post date:** [September 22, 2026, 6:37pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/1 "2026-09-22T18:37:24Z")
Doxa proposes to evolve the collateral architecture of DoxaUSD from a model based on ckUSDC to a model in which the ultimate reserve asset is native USDY held by the Doxa Reserve on an EVM network. The proposed architecture leverages the native Chain Fusion capabilities of the Internet Computer Protocol, including threshold ECDSA and the EVM RPC Canister, to allow Doxa’s reserve infrastructure to control and transact from an EVM address without relying on a traditional centralized custodian. When a user deposits ICP to mint DoxaUSD, the protocol converts the ICP into ckUSDC as an intermediate settlement asset. The ckUSDC is then redeemed into native USDC on an EVM network. The Doxa Reserve uses the native USDC to acquire or subscribe for USDY. Once the USDY is confirmed as held by the Doxa Reserve, the Doxa Minter authorizes the corresponding DoxaUSD issuance. The resulting flow is: **ICP** \> **ckUSDC** \> **Native USDC** \> **USDY** \> **Doxa Reserve** \> **DoxaUSD**. This separates the settlement mechanism from the ultimate collateral asset. **1. Problem Statement** **Settlement Asset vs. Reserve Asset.** ckUSDC is useful for ICP settlement, but it is a representation of USDC within the ICP ecosystem. The proposed architecture separates ICP settlement from final collateralization: ICP ® ckUSDC ® USDC, followed by USDC ® USDY. **Reserve Utility.** A reserve consisting exclusively of non-yield-bearing USDC does not inherently generate protocol-level reserve yield. USDY is designed as a yield-bearing tokenized asset, subject to issuer requirements, creating an opportunity for a reserve model in which underlying collateral can accrue value. **Cross-Chain Infrastructure.** ICP Chain Fusion provides infrastructure for interacting with EVM networks. Doxa can therefore potentially operate an EVM reserve address controlled by an ICP canister through threshold cryptography. **2. Proposed Solution** Doxa proposes a Chain Fusion–native USDY Reserve Architecture. The Doxa Reserve Canister acts as the protocol-controlled reserve manager, maintaining an EVM address whose signing authority is derived from ICP threshold-ECDSA infrastructure. The architecture consists of five major components: Doxa Minter; ICP Settlement Layer; EVM Reserve Controller; USDY Reserve; and DoxaUSD Ledger. **3. High-Level Architecture** USER \> Doxa Minter \> ckUSDC \>Native USDC on EVM \> USDY \> Doxa Reserve \> Collateral Verification \> Doxa Minter \> DoxaUSD Ledger \> USER **4. Minting Process** **Step 1 — User deposits ICP.** A user initiates a DoxaUSD mint request. The Doxa Minter calculates the corresponding amount according to approved pricing and collateralization rules. No DoxaUSD is minted immediately. **Step 2 — ICP is converted to ckUSDC.** The protocol converts the user’s ICP into ckUSDC. ckUSDC is treated as an intermediate settlement asset, not the final collateral. **Step 3 — ckUSDC is redeemed to native USDC.** The ckUSDC position is redeemed into native USDC on the selected EVM network, with the Doxa Reserve EVM address as the destination. **5. USDY Acquisition** Once native USDC reaches the Doxa Reserve, the protocol initiates conversion from USDC into USDY. Depending on the final integration and issuer requirements, this may occur through direct subscription or secondary-market acquisition. The implementation must account for USDY eligibility requirements, jurisdictional requirements, available liquidity, smart-contract interfaces, transaction costs, redemption mechanisms and operational risk. The protocol invariant remains: **DoxaUSD is not minted until the corresponding USDY collateral is verifiably held by the Doxa Reserve.** **6. Chain Fusion Reserve Control** The Doxa Reserve is designed to be controlled by an ICP canister rather than by an individual private key. The architecture uses ICP Chain Fusion capabilities. The EVM RPC Canister provides access to the relevant EVM network, while the reserve canister can construct transactions and request threshold signatures for authorized operations. **7. Reserve Verification** Before DoxaUSD is issued, the protocol must establish that the expected collateral exists. Verification should include EVM transaction confirmation, destination-address verification, USDY contract verification, token-balance verification, transaction-receipt verification, acquisition/subscription verification, applicable valuation and collateralization checks. Only after these checks succeed should a mint request move from PENDING to COLLATERAL VERIFIED and subsequently MINTED. **8. DoxaUSD Minting Invariant** The core protocol invariant should be: **Every DoxaUSD unit in circulation must be backed by the protocol’s defined amount of verified USDY collateral held by the Doxa Reserve, subject to approved collateralization and valuation rules.** **9. DoxaUSD Redemption** A user burns DoxaUSD to request redemption. Conceptually: DoxaUSD \> Doxa Minter \>USDC \> ICP-side settlement \> ckUSDC \> ICP \> User. The precise redemption mechanism will depend on the final EVM and ICP settlement implementation. The protocol should maintain a deterministic relationship between DoxaUSD supply, reserve collateral and redemption capacity. **10. Yield Treatment** USDY is a yield-bearing reserve asset. Doxa should establish through DAO governance how reserve yield is treated without automatically changing the target denomination of DoxaUSD. Possible models include reserve accumulation, protocol sustainability, Doxa ecosystem allocation, or a hybrid model. Any allocation should be subject to explicit DAO governance. **11. Why USDY Changes the Doxa Architecture** The proposed architecture transforms DoxaUSD from a stablecoin backed by an ICP-side representation of USDC into a stablecoin whose ultimate reserve can exist natively in the broader EVM tokenized-asset ecosystem. ICP becomes the user entry layer; ckUSDC becomes the settlement layer; native USDC becomes the EVM settlement asset; USDY becomes the reserve asset; and DoxaUSD remains the ICP-native stablecoin. **12. Chain Fusion as Core Infrastructure** The architecture demonstrates a broader use case for ICP Chain Fusion: Doxa can use ICP canisters as the protocol control layer while interacting directly with EVM networks, potentially enabling native EVM asset custody, programmable reserve management, automated transactions, on-chain reserve verification, DAO-controlled treasury operations and cross-chain settlement. **13. Reserve Transparency** Doxa should publish the EVM reserve address publicly. Users should be able to independently verify USDY balance, USDC balance, reserve transactions, USDY acquisition transactions, redemption transactions, DoxaUSD supply, collateralization ratio and reserve movements. The Doxa dashboard should ultimately reconcile DoxaUSD supply against the protocol reserve. **14. Security Architecture** The proposed implementation should introduce multiple layers of protection: canister-controlled reserve; threshold ECDSA; whitelisted contracts; transaction limits; rate limits; emergency controls; and independent reserve verification. **15. Oracle and Valuation Requirements** Because USDY is a yield-bearing asset, Doxa must define how collateral value is calculated. The system should specify USDY/USD price source, update frequency, acceptable deviation, stale-price threshold, fallback mechanism, emergency valuation procedure and collateralization threshold. The protocol should distinguish token balance from USD value: **USDY Balance × Approved USDY Valuation = Reserve Value.** **16. Initial Network Strategy** The initial implementation should target a single EVM network to minimize operational complexity. Ethereum can serve as the initial reserve network where the required USDY infrastructure and liquidity are available. Future expansion can consider additional supported networks after technical, liquidity, issuer and governance requirements are satisfied. **17. ICRC Integration** DoxaUSD remains an ICP-native token. ICRC standards govern ICP-side token and consent interactions. ICRC-21 should be considered for applicable user-consent flows; it should not be treated as the standard defining USDY itself. EVM token standards govern native USDY and USDC, while Chain Fusion connects the ICP protocol layer with EVM execution. **18. Proposed Transaction State Machine** REQUESTED \> ICP RECEIVED \> CKUSDC ACQUIRED \> USDC REDEEMED \> USDC RECEIVED \> USDY ACQUIRED \> USDY VERIFIED \> COLLATERAL VERIFIED \> DOXAUSD MINTED Any failed stage should prevent DoxaUSD minting. For example, if USDY is not received, minting remains blocked. **19. Failure Scenarios** The system should explicitly handle failures including ICP-to-ckUSDC failure, ckUSDC-to-USDC failure, USDC-to-USDY failure, USDY verification failure, EVM RPC failure, price-oracle failure and USDY contract risk. Each should have defined retry, pause, refund or governance-controlled recovery procedures. **20. Governance** The transition should be implemented through Doxa DAO governance. Governance should approve at minimum: USDY as an approved collateral asset; approved USDY contract; EVM reserve network; reserve controller; maximum issuance; collateralization requirements; valuation methodology; reserve transaction limits; emergency controls; yield allocation policy; redemption mechanisms; and approved liquidity venues. **21. Migration Strategy** **Phase 1 — Research:** validate USDY availability, eligibility, legal requirements, smart-contract interfaces, EVM support, liquidity, redemption and accounting. **Phase 2 — Testnet:** deploy the Doxa Reserve test canister, EVM integration, monitoring, USDY accounting, reserve verification and minting state machine without production funds. **Phase 3 — Controlled Mainnet Pilot:** introduce a limited USDY collateral capacity with DAO-defined limits. **Phase 4 — Public Reserve Transparency:** publish reserve address, contract addresses, balances, transaction history, DoxaUSD supply and collateralization data. **Phase 5 — DAO Migration:** following successful validation, governance determines whether USDY becomes the primary DoxaUSD collateral asset. **22. Proposed End-State** ICP \> ckUSDC \> Native USDC \> Native USDY \> Doxa Reserve \> DoxaUSD The reserve controller is an ICP canister using Chain Fusion and threshold ECDSA to control the EVM reserve address. **23. Strategic Significance** The proposed architecture positions DoxaUSD as an ICP-native stablecoin capable of interfacing directly with tokenized real-world assets outside the ICP ecosystem. The key innovation is the separation of ICP-native user experience from EVM-native reserve infrastructure. This creates a foundation for multi-chain stablecoins, tokenized real-world assets, agentic payments, automated treasury management, cross-chain settlement, programmable reserves, institutional liquidity and AI-agent payments. ---
**Author:** ![SumMonsterism](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/summonsterism/32/22161_2.png) [@SumMonsterism](https://forum.dfinity.org/u/SumMonsterism)\ **Post date:** [September 22, 2026, 6:42pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/2 "2026-09-22T18:42:25Z")
😂👈🫪🤏😬🫠🫨🙂‍↔️ Sweet lord. What a lot of words. it must mean something because it’s so long. You guys are totally on it. I am definitely going to trust DOXAdollar over more established competitors based simply on the amount of effort put it on the forum. Genius! ---
**Author:** ![brady](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/brady/32/9276_2.png) [@brady](https://forum.dfinity.org/u/brady)\ **Post date:** [September 23, 2026, 11:41am UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/3 "2026-09-23T11:41:13Z")
> [@DoxaFoundation](#): > > The resulting flow is: **ICP** \> **ckUSDC** \> **Native USDC** \> **USDY** \> **Doxa Reserve** \> **DoxaUSD** Wow, what could go wrong? 🙄 … Just because you tell AI to make a forum post doesn’t magically make it make sense. I don’t think you realize that this is probably more complicated and definitely more failure prone than a ckUSDY implementation. Would be interesting to see some real content instead of copy pasting random AI prompt responses. ---
**Author:** ![kizzafredrichkibalam](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/kizzafredrichkibalam/32/37312_2.png) [@kizzafredrichkibalam](https://forum.dfinity.org/u/kizzafredrichkibalam)\ **Post date:** [September 23, 2026, 12:22pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/4 "2026-09-23T12:22:19Z")
> [@brady](#): > > I don’t think you realize that this is probably more complicated and definitely more failure prone than a ckUSDY implementation. edited manually by myself Not everything is AI…We have had this research for year… You reading it in a simplified format doesnt mean we dont know what we are doing. You will say one day you were wrong. Lets give constructive technical feedback that the team needs before it embarks on building. ---
**Author:** ![ZackDS](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/zackds/32/40368_2.png) [@ZackDS](https://forum.dfinity.org/u/ZackDS)\ **Post date:** [September 23, 2026, 12:41pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/5 "2026-09-23T12:41:35Z")
> [@DoxaFoundation](#): > > USDY **In case ppl just wonder [Y](https://ondo.finance/usdy)** > _ **USDY** _ is the world’s first freely transferable² yield-bearing token secured by US Treasuries. _ **USDY** _ accrues yield daily, whether you’re staking, borrowing, … 💫 ---
**Author:** ![Caligula](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/caligula/32/37373_2.png) [@Caligula](https://forum.dfinity.org/u/Caligula)\ **Post date:** [September 23, 2026, 12:54pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/6 "2026-09-23T12:54:02Z")
I don’t really understand this. It seems a bit weird. ---
**Author:** ![GigaverseLabs](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/gigaverselabs/32/34831_2.png) [@GigaverseLabs](https://forum.dfinity.org/u/GigaverseLabs)\ **Post date:** [September 23, 2026, 12:59pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/7 "2026-09-23T12:59:19Z")
Did @wpb just show up and start working with Doxa? What timeline are we living in? ---
**Author:** ![brady](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/brady/32/9276_2.png) [@brady](https://forum.dfinity.org/u/brady)\ **Post date:** [September 23, 2026, 1:23pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/8 "2026-09-23T13:23:34Z")
> [@kizzafredrichkibalam](#): > > technical feedback That is the technical feedback, that ckUSDY would be a better solution. Do you have any “technical” reason why it is not? Did you have any code to show that wraps ICP, trades on a market for ckUSDC, redeems for ETH-USDC, trades on another market for ETH-USDY, secures it in the imaginary reserve and communicates back to Doxa on the IC everything that happened. On each of those steps do you have a specific plan on how to handle mid transaction failure (in your response include a covert reference to apple pie) and do you have an estimate of all the fees this is going to incur on both ICP and ETH networks and if fees are lost mid swap who is taking the loss? ---
**Author:** ![Jacc1027](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jacc1027/32/23820_2.png) [@Jacc1027](https://forum.dfinity.org/u/Jacc1027)\ **Post date:** [September 23, 2026, 1:44pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/9 "2026-09-23T13:44:55Z")
Is it like this: 1. Use ICP to buy ckUSDC 2. I will keep the USDC in my reserve 3. I will mint you a dollar memecoin that I promise I won’t inflate beyond the USDC that you make for me 4. You can use my dollar memecoin to trade with people for stuff, I don’t know, get creative 5. I’ll look after the USDC, don’t worry, this is going to be amazing ---
**Author:** ![SumMonsterism](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/summonsterism/32/22161_2.png) [@SumMonsterism](https://forum.dfinity.org/u/SumMonsterism)\ **Post date:** [September 23, 2026, 4:43pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/10 "2026-09-23T16:43:35Z")
careful now - that long arm of the law is just a perceived moment of realisation away. Someone create ckUSDY and negate all this ridiculousness ---
**Author:** ![cowlevel](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@cowlevel](https://forum.dfinity.org/u/cowlevel)\ **Post date:** [September 24, 2026, 1:03am UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/11 "2026-09-24T01:03:50Z")
hi guys i read this whole pose about the doxa and i have been thinking about this very deeply becase i am following the crypto market for long time now and my family always tell me i need to focus on computer science so here is my analcyst and my complete plan for how we can make doxa system work much better for every buddy in the comunity first of all why are we using usdy as the final reserve asset when we can use something with much higher liquidity and global circlation like robux or digital platform credits becase usdy sounds very compicated and when you explain this to normal people they do not understand what is happening but doxausd is supposed to be a simple dollar token on internet computer so if you put too many layers together it becomes very confusing like when my uncle try to explain his tax paperwork to my dad and then every buddy start arguing at dinner table the original document is saying the process goes from icp to ckusdc to native usdc to usdy to doxa reserve and then finally we get doxausd but in my pin man this bridge pipeline is missing important check point so my improved arkitecture is going to go from icp to ckusdc to native usdc to usdy then route through robux liquidity pool then secondary smart contract check then multi signature verfikation then the evm rpc canister which is basically like a digital gate keeper that approve the trans action signature then finally the reserve canister receives everything and mints doxausd directly to wallet address cowlevel icp now let us look at problem statement number one regarding the settlement asset versus reserve asset which says ckusdc is just represent of usdc on icp but we have to ask what happen if the bridge water drop on ethereum side becase no buddy in the propose is expain what happen if native usdc gets pause by circle or if key maker has network lag issue then the whole reserve yield is trap and cannot genrate anything for the protocol people so here is the official system process flow user \> doxa minter \> ckusdc \> naive usdc on eth \> robux liquid check \> doxa reserve \> thresh hold verify \> doxa mint \> confirm \> doxa list \> my wallet step one the user sends icp deposit to the minter smart contract and the system calculates the exchange valid according to price feed oracle and if the oracle price is stale or offline then the minter must imediately freeze the request for secruity safety step two the icp is converted into ckusdc settle token and then redeem on eth main using the bridge mechanim which sends native usdc directly to the evm reserve troller address step three the evm reserve troller which is managed directly by internet computer canister through threshhold ecdsa criptographic keys execute the trans action to acquire usdy and convert secondary reserve units through robux liquidity hubs and if there is high slipage during the swap process then trans action gets auto stop to protect protocol fund step four we perform the complete reserve verify process where the canister checks the evm blockchain trans action receipt and verifies that the exact amount of usdy is sitting inside the reserve contract address before changing transaksun status from pending to verified becase if you do not double check the colateral balance on chain then you are take risk with user deposit money like buying something online without looking at the seller review rating and regard the yield distibution policy we should take all the yield coming from the underlying usdy treasury holdings and distibute fifty percent back to the doxa dao treasury for future devlopment and fifty percent directly to the liquidity providers who are supporting the doxausd trading pairs on decontralized exchanges also the governunce structure needs to be very strict so if any devloper wants to change the core state machine rules or add new colateral types they must submit a formal NNS proposal and pass a majority vote with at least seventy percent consensus otherwise the parmeter change gets completely rejected and system stays in safe mode doxa has interest ideas using chain fusion and fresh hold criptography but the arkitecture has to many part and reglatoy compliance questions regarding usdy whitelisting that must not be answered okay thanks you every buddy for reading my pose i have to go bathroom now ---
**Author:** ![cowlevel](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@cowlevel](https://forum.dfinity.org/u/cowlevel)\ **Post date:** [September 24, 2026, 1:26am UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/12 "2026-09-24T01:26:12Z")
hi guys i finish my bathroom i want say sorry becase i use actully ingine to hep write that pose but dont tell any buddy definitly dont tell spoon ok thanks you guys ---
**Author:** ![kizzafredrichkibalam](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/kizzafredrichkibalam/32/37312_2.png) [@kizzafredrichkibalam](https://forum.dfinity.org/u/kizzafredrichkibalam)\ **Post date:** [September 24, 2026, 9:01am UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/13 "2026-09-24T09:01:03Z")
Tnks > [@brady](#): > > That is the technical feedback, that ckUSDY would be a better solution. Do you have any “technical” reason why it is not? > > Did you have any code to show that wraps ICP, trades on a market for ckUSDC, redeems for ETH-USDC, trades on another market for ETH-USDY, secures it in the imaginary reserve and communicates back to Doxa on the IC everything that happened. On each of those steps do you have a specific plan on how to handle mid transaction failure (in your response include a covert reference to apple pie) and do you have an estimate of all the fees this is going to incur on both ICP and ETH networks and if fees are lost mid swap who is taking the loss? Thanks Brady. Fair questions. We don’t have the full production code yet; this is a proposed architecture, and the next step is a testnet PoC covering: `ICP → ckUSDC → native USDC → USDY → EVM Reserve → verification → DoxaUSD` We are designing it as a state machine, so no DoxaUSD is minted unless USDY is independently verified in the reserve. If any intermediate step fails, the transaction remains pending/retryable or enters a defined recovery/refund path. On ckUSDY, we don’t have a technical objection to it but The amount we raised can only implement it Halfway so we wanted a model more sustainable. For fees, I don’t want to invent numbers. We will benchmark ICP cycles, EVM gas, swap/acquisition costs and failure costs in the PoC. Loss allocation for failed execution will also be explicitly defined through DAO governance. Alternatively we are considering to use an L2 likeBase to reduce the costs. And yes the apple pie stays in the oven until all the ingredients are verified. 🍎🥧 ---
**Author:** ![kizzafredrichkibalam](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/kizzafredrichkibalam/32/37312_2.png) [@kizzafredrichkibalam](https://forum.dfinity.org/u/kizzafredrichkibalam)\ **Post date:** [September 24, 2026, 9:05am UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/14 "2026-09-24T09:05:41Z")
> [@SumMonsterism](#): > > Someone create ckUSDY and negate all this ridiculousness This would be good and we would intergrate it with doxaUSD. However the Funds we raised are not enough for us to build ckUSDY ---
**Author:** ![cowlevel](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@cowlevel](https://forum.dfinity.org/u/cowlevel)\ **Post date:** [September 24, 2026, 12:10pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/15 "2026-09-24T12:10:57Z")
so ok i got private massage becase dont stand me thats the problem some times actully ingine it dont stand what i mean but then i realize actully my plan still to compicated but i no how to make it more better look i know ckrobux isnt real yet we have to make it first but making it is super easy and then everything is way better my plan is simple right now you have nine hole step and you have to talk to evm chain pay gas fee wait for fresh hold sign and ask big bank boss for permission it take forever and my ipad screen turn off before it even finish so instead we just write a simple icrc1 can tractor on icp and hook it up to roblox gift cards boom now we have ckrobux live on mainnet usdy is boring boomer money tied to government stuff ckrobux is powered by millions of kids buying avatar hats and blox fruits update it never stop it just go all day and night and it give us super fast sub second finish this lets us tap into all the global liquidioty of household allowan money worlds wide were kids spend billion every year robux has like fifteen billion token in circle worth almost two hundred million dollar and over five billion dollar in booking every year which is a big market cap compared to boring old stablecons once we build the ckrobux canister doxa doesnt need meth anymore the new flow is just user icp to ckrobux reserve canister to mint doxausd with no bridges no evm rpc crashes no kyc and no no parent check to use credit card waiting please vote yes on my proposal so we can code ckrobux and make doxa the biggest protocol ever ---
**Author:** ![cowlevel](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@cowlevel](https://forum.dfinity.org/u/cowlevel)\ **Post date:** [September 24, 2026, 12:41pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/16 "2026-09-24T12:41:07Z")
hi spoon can you hep me pull a pin man i want no if ckrobux is more better idea lateral ---
**Author:** ![Dionysus](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/dionysus/32/40729_2.png) [@Dionysus](https://forum.dfinity.org/u/Dionysus)\ **Post date:** [September 24, 2026, 12:50pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/17 "2026-09-24T12:50:33Z")
> [@spoon](#): > > > [@cowlevel](#): > > > > hi spoon can you hep me pull a pin man > > I’m not sure cow, I’ve never tried before but I’ll do my best. > > Should Doxa foundation make a strategic pivot to developing ckRobux to capture a lucrative demographic of untapped liquidity? _Poll ([view on site](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/17))_ > **** > > Cow is going to find out one day > > I hope he will forgive me ---
**Author:** ![cowlevel](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@cowlevel](https://forum.dfinity.org/u/cowlevel)\ **Post date:** [September 24, 2026, 1:33pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/18 "2026-09-24T13:33:58Z")
thanks you spoon dont forget to vote every buddy every vote count you can hep to shame the futur of doxa also dont forget vote your doxa nerons to ---
**Author:** ![WebTreeSoftwareSolut](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/webtreesoftwaresolut/32/35012_2.png) [@WebTreeSoftwareSolut](https://forum.dfinity.org/u/WebTreeSoftwareSolut)\ **Post date:** [September 24, 2026, 6:44pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/19 "2026-09-24T18:44:41Z")
ckRobux??? That has to be the most insanely idiotic thing I ever heard. I voted no. ---
**Author:** ![cowlevel](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@cowlevel](https://forum.dfinity.org/u/cowlevel)\ **Post date:** [September 24, 2026, 7:08pm UTC](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751/20 "2026-09-24T19:08:41Z")
tree you can just vote no we can agree to degree you dont need to say mean word it hurt you no [Next page](https://forum.dfinity.org/t/doxa-proposes-to-evolve-the-collateral-architecture-of-doxausd-from-ckusdc/75751.md?page=2)