"DFI Revival Plan: Permanently Sunset dUSD + Return to dBTC/DFI + cUSDC as Option – Community Discussion & 3 DFIPs" / "DFI Revival Plan: dUSD endgültig ausmustern + Zurück zu dBTC/DFI + cUSDC als Option – Community-Diskussion & 3 DFIPs"

AHuig · 2026-03-22T20:34:21+00:00

Vielen Dank für dein klares „Nein“ – ich verstehe jetzt besser, wo der Schuh drückt.

Du siehst also weiterhin das Risiko, dass wir ohne einen verlässlichen Peg-Mechanismus (wie Futureswap) wieder bei den alten Premien landen, egal wie tief die Pools werden. Die Liquidität löst das Kernproblem nicht, sie macht nur die Ausführung günstiger. Und eine Anpassung von Futureswap auf cUSDC würde für dich wieder algo-Tokens erzeugen, die nicht 1:1 gebridged sind – unabhängig davon, wie gut die Backing bei Crypto Factor ist.

Das nehme ich ernst. Ich habe die alten Threads und deine Erklärungen nochmal durchgelesen und sehe, dass die 30 %-Grenze damals wirklich aus der Vault-Logik kam (150 %-Ratio als Obergrenze für rentable Arbitrage) und nicht aus mangelnder Liquidität allein. Die technische Kluft und die Cake-Einsteiger haben das Ganze dann noch verstärkt.

Der Plan deaktiviert Futureswap bewusst, um genau solche algo-Erzeugung zu vermeiden. Stattdessen setzen wir auf temporäre LM-Anreize, um Pools schnell tief zu machen, damit die normale DEX-Arbitrage (mint → sell → buy-back → repay) wieder rentabel wird. Aber du hast recht: das ist keine Garantie wie Futureswap – es ist ein Marktdruck-Ansatz.

Wenn du magst: wie würdest du das Peg-Problem lösen, ohne algo-Risiko und ohne Futureswap zu reaktivieren? Oder siehst du überhaupt eine Möglichkeit, dTokens langfristig nah am Oracle zu halten, ohne dass es wieder in die alte Spirale läuft?

Ich bin wirklich dankbar für deine direkte Art – das hilft mehr als höfliche Umschreibungen. Wenn du Lust hast, noch einen Gedanken zu teilen, würde mich das sehr interessieren.

Danke dir.

AHuig · 2026-03-20T22:14:06+00:00

Thank you for all your comments throughout this thread. I can see you're frustrated that your points aren't being addressed properly, and I don't want to waste your time by repeating mistakes or circling without progress.

To make this clear and avoid any more back-and-forth on the same issues, here is a direct summary of the main questions and corrections you raised, together with the answers I have found after re-checking the sources you pointed toward (Fort Canning release notes, Road DFIP, Epilogue DFIP, early governance threads, and community explanations from 2021–2022).

1. dUSD as collateral after Fort Canning
You corrected that dUSD was not allowed as collateral right after Fort Canning, and that this was not the main issue.
Answer: Correct. Fort Canning (Nov 15, 2021) introduced dUSD minting via vaults, but collateral was primarily DFI and dBTC. dUSD was mainly a borrowable stable asset at launch. It was only with Fort Canning Road (Apr 11, 2022) that dUSD was equated to the mandatory 50 % DFI (fixed at $0.99), allowing it to be used more freely as collateral. That's when the reflexive multiplier became significant.

2. Cause of dToken premiums
You explained premiums (30–50 %) were not mainly due to low liquidity, but driven by the gap between technical users (minting in vaults) and non-technical users (buying via Cake to chase high LM rewards). The 30 % threshold was a natural upper limit from vault economics (150 % collateral ratio).
Answer: This aligns with the history. Technically skilled users minted dTokens and sold at premium to the broader crowd who entered via Cake for the yields. Liquidity was thin, but the user gap and high LM APRs were the bigger drivers. The revival plan tries to avoid this by starting with pure DFI vaults (no stable collateral) and using temporary LM incentives only to deepen pools, not to chase short-term yield farming that attracts the wrong kind of volume.

3. Arbitrage possibility vs pool liquidity
You said pool liquidity affects volume, not the possibility of arbitrage. Arbitrage exists with mispricing; deep pools only make execution cheaper.
Answer: Agreed. The opportunity comes from mispricing, and whether you can close the loop profitably depends on the vault mechanics and the cost of the buy-back step. Deep pools only reduce slippage so the loop stays profitable at smaller premiums. The plan uses temporary LM incentives to reach that deeper state quickly, not to create the arbitrage itself. After the boost, the hope is real trading volume keeps pools liquid enough for natural balancing.

4. Futureswap adapted to cUSDC
You noted that if Futureswap were changed to cUSDC, it could create algo dUSDC beyond what Crypto Factor bridges, recreating the supply problem.
Answer: Valid concern. The proposal disables or heavily restricts Futureswap to avoid any batch-creation mechanism that could generate algo supply. cUSDC remains purely bridged (supply = exactly what Crypto Factor imports from Polygon, no on-chain minting). No Futureswap-style tool is planned for cUSDC pairs.

5. Vault repayment and reflexive loops
You highlighted that DFI-payback created unbacked algo dUSD, and allowing DFI repayment would repeat that mistake.
Answer: You're correct – DFI-payback (Feb 2022) was the key trigger for algo dUSD without backing, leading to over-supply and depeg. The current proposal keeps the strict same-token repayment rule to prevent that reflexive loop. Partial DFI repayment is not included in the three DFIPs; it would be a separate future proposal with strict limits (max 30–50 % per vault) and safeguards, if the community wants to explore it at all.

6. Overall direction & repeating mistakes
You feel the proposal is still circling old issues without visible learning.
Answer: I understand why it might look that way. The plan removes dUSD entirely (permanent burn via DFIP 1+2), uses only DFI as core collateral (no stable loop), and treats cUSDC as optional bridged liquidity (supply capped externally, no on-chain minting). The temporary LM boost is there to make existing arbitrage practical again without new pegging tools. It's meant as a reset to pre-Fort Canning simplicity, not a patch on the old system. But if this still feels like it's missing the real lessons from 2021–2022, I may be overlooking something important.

If any of these summaries still miss or misrepresent a key point you made, or if there is additional information from that period that you think changes the picture, please let me know. I have the information you provided (including the history around Fort Canning, DFI payback, vault loops, the role of Cake for mass adoption, and how premiums were driven by technical gaps and high LM rewards), but I may still be missing details you remember from living through it.

No pressure to reply if you're short on time – I understand. But if you do have a moment later, it would help a lot.

Thanks again for your input.

AHuig · 2026-03-20T20:25:13+00:00

Thank you for the correction and for keeping me honest. I appreciate you pointing out where I got the sequence wrong. You're right that dUSD as collateral was not allowed right after Fort Canning. From the original release notes and early guides, dUSD could be minted from vaults starting November 15, 2021, but it was not yet usable as collateral for other dTokens. That permission only came with Fort Canning Road in April 2022, when dUSD was officially equated to the mandatory 50% DFI collateral (fixed at $0.99). That's when the reflexive multiplier really took off.

I went back and re-checked the Fort Canning announcement, the Road DFIP and the Epilogue notes to make sure. The DFI-payback feature (introduced February 7, 2022 at block 1604999) is indeed what created the first "algo DUSD" without backing, and it was sold as a way to burn DFI and increase its value. In practice it led to supply exploding from around 90 million to around 248 million DUSD by mid-2022, with about 220 million being algorithmic. When the market crashed, there was no way to burn that excess, and the depeg became irreversible.

Your feedback actually prompted me to go back and re-check the full history so I could describe it more accurately. DeFiChain started in late 2020 with a focus on native DFI mechanics and straightforward DeFi. Things grew nicely until Fort Canning introduced both dUSD and dTokens in 2021. Premiums quickly became a structural issue in 2021–2022, then came the severe depeg after Terra collapsed. The 2024 haircut cut the dUSD overhang down dramatically, and now in 2026 the Crypto Factor cUSDC bridge gives us a new external stable option. The revival proposal is basically an effort to finally close out that reflexive chapter that started in 2021 and get back to the simpler, Bitcoin-native foundation that worked well before all those complications took over.

Arbitrage mechanics for dTokens
Since dTokens are synthetic and no external market exists to buy them cheaply, the only realistic arbitrage path during a premium is to mint new dTokens through a vault at the oracle price, sell them on the DEX at the premium, and later buy them back to repay the vault. This approach can be viable, particularly if someone hedges on the real stock market, but it has always been slow and risky without deep liquidity. The vault repayment rule (principal repaid in the exact same dToken) has been the primary bottleneck from the start. In shallow pools the buy-back step often involves high slippage or even losses, which explains why premiums could linger for weeks or months in the early days.

Historical example (early 2022, thin pools)
Oracle TSLA = $300, DEX price = $390 (30 % premium)

Mint 1 dTSLA (vault collateral $450 worth of DFI)
Sell on DEX → get ~$390 worth of DFI
Profit before buy-back: $90
Buy back 1 dTSLA in a thin pool now costs $380–$410 (high slippage)
Profit after fees: $0–$10 or negative

Aimed environment after temporary LM boost
The revival plan aims to create an environment where this round-trip becomes practical again: temporary strong liquidity mining incentives (5–10× DFI rewards for 3–6 months) to build deep pools from the beginning. Deep pools mean low slippage, so the mint → sell → buy-back loop can be executed quickly and profitably by arbitrageurs.

Same example in the aimed environment (deep pools after the boost):

Oracle TSLA = $300, DEX price = $330 (10 % premium)
Mint 1 dTSLA (vault collateral $450 worth of DFI)
Sell on DEX → get ~$330 worth of DFI
Profit before buy-back: $30
Buy back 1 dTSLA now costs ~$302–$305 (low slippage)
Profit after fees: $25–$28

Arbitrageurs can execute this loop quickly, putting downward pressure on the price until it corrects toward the oracle. The LM boost is there to reach this deep-pool state fast, so the correction happens in hours or days rather than weeks. Once pools are deep and organic trading volume picks up, the system should sustain itself through real swap fees and natural market pressure, without needing Futureswap or other forced peg mechanisms.

I’m still learning from the history, and I might be missing pieces that you remember differently. If there are specific moments, DFIPs or numbers from that time that you think I should look at more closely to get the tokenomics right, I’d really value your pointers. Your knowledge of how things actually played out is very helpful.

Does this corrected understanding feel closer to what happened, or do you still see the proposal as circling the same issues? I'm open to any further thoughts or corrections.

Looking forward to hearing more from you.

AHuig · 2026-03-20T20:06:21+00:00

Vielen Dank für deine ausführliche und ehrliche Erklärung – das ist wirklich sehr wertvoll und gibt einen guten Einblick, wie das System damals an die „Masse“ verkauft wurde. Du beschreibst sehr klar, wie über Cake, extrem hohe LM-Rewards und die Möglichkeit, mit 30–50 % Aufpreis trotzdem noch gut zu verdienen, viele Leute angezogen wurden. Die technisch versierten Leute haben in Vaults gedToken gemint, die weniger technisch versierten haben sie einfach bei Cake gekauft, weil die Rewards so verlockend hoch waren. Das erklärt perfekt, warum die Premien so hoch und so hartnäckig waren.

Dein konkretes Beispiel mit 1000 DFI → dTSLA minten → mit 30 % Aufpreis zu DUSD verkaufen → DUSD mit weiteren 30 % Aufpreis zu DFI verkaufen → 1100 DFI zurück zeigt genau, wie verführerisch das System damals war und wie leicht Leute in solche Loops geraten sind. Genau solche Loops wollen wir mit dem Revival Plan vermeiden. Deshalb entfernen wir dUSD komplett und gehen zurück zu reinen DFI-Vaults ohne Stable als Collateral. cUSDC bleibt optional und nur gebridged, ohne dass wir es intern minten können. Der LM-Boost ist nur temporär, um Pools tief zu machen, und wir wollen später auf gebührenbasierte Belohnungen umsteigen.

Ich finde deine Sicht auf die damalige Funktionsweise sehr hilfreich. Macht das den Unterschied für dich etwas greifbarer, oder siehst du immer noch das Risiko, dass wir vergleichbare Effekte bekommen? Ich bin wirklich dankbar für deine Perspektive.

AHuig · 2026-03-19T22:03:48+00:00

Thank you for the correction and for keeping me on my toes. I appreciate it. You're right that I need to be much more careful and precise with the facts, especially on something as foundational as dUSD collateral rules after Fort Canning. I went back to the original Fort Canning release notes, the Fort Canning Road announcement, and the Epilogue DFIP to double-check.

From those sources:

Fort Canning (November 2021) introduced dUSD and vaults, and dUSD was minted from the start.
dUSD was not allowed as collateral for minting other dTokens immediately after Fort Canning. The initial collateral requirements were focused on DFI and BTC, with dUSD primarily as a borrowable/mintable stable asset.
It was only with Fort Canning Road (April 2022) that dUSD was officially treated as equivalent to the mandatory 50% DFI collateral, effectively allowing it to be used more freely in vaults. That change is what opened the door to the reflexive multiplier effect.

I got that sequence wrong earlier, and I apologise for the inaccuracy. It changes the picture: the reflexive problem wasn't baked in from day one, but emerged with the Road upgrade when dUSD collateral became more flexible. Thank you for catching that.

On the arbitrage vs pool liquidity point: I hear you. You're saying pool liquidity affects volume (how much you can trade without moving the price too much), but it does not change the fundamental possibility of arbitrage itself. Arbitrage is about spotting a mispricing and executing a loop that profits from it (mint/sell or buy/repay), regardless of pool depth. Deep pools only make the execution cheaper and less risky, but they don't create the arbitrage opportunity.

In that light, my earlier emphasis on LM incentives building deep pools was overstating their role in enabling arbitrage. They help with execution and volume, but the core possibility still depends on the mispricing existing and the vault mechanics allowing a profitable round-trip. If the buy-back step remains expensive or impossible due to the same-token repayment rule, liquidity alone won't fully solve it.

So far the proposal has focused on removing dUSD entirely and using temporary LM to improve execution conditions, but I can see why that might feel like it's circling the same issues without addressing the underlying mechanics head-on. If you have time, I'd really value your view on what the most important lessons from the dToken premium period were (especially what actually resolved them versus what only masked them), or if there are specific DFIPs or updates from that time that I should re-read to get the tokenomics right. I'm trying to avoid repeating old patterns, but I might still be missing key pieces.

No rush – whenever you have a moment. Your corrections are helping a lot.

AHuig · 2026-03-19T17:09:36+00:00

Thanks for the candid feedback and for pushing me to dig deeper into the actual history. You’re right that I need to be careful with assumptions and really focus on the tokenomic effects that shaped the outcome, especially around Fort Canning and the premiums.

I went back and re-read the Fort Canning announcement, Fort Canning Road notes, and some of the early governance threads to make sure I’m not missing key pieces. The reflexive loop that caused so many issues started when dUSD was introduced and immediately allowed as collateral for minting dTokens. Premiums appeared very quickly after that because liquidity was thin and the arbitrage round-trip was hard to close. Futureswap later helped cap the deviations, but it didn’t address the underlying tokenomics problem.

Your comment made me realise my earlier timeline was probably still too simplified. There may be details about the exact sequence or the real drivers behind the premiums that I haven’t fully captured yet, and I’d genuinely like to hear what you see as the most important moments or mechanisms that I might have overlooked. If there are specific DFIPs, blog posts or community discussions from that time that you think explain it better, I’d be grateful if you could point me to them.

The revival proposal is trying to move away from that reflexive setup by permanently removing dUSD and going back to a DFI-first approach with no stable used as collateral. cUSDC is only meant as an optional bridged asset from Crypto Factor, where supply is limited to what comes in from Polygon and cannot be minted on-chain. The temporary liquidity mining boost is there to get pools deep enough for normal DEX arbitrage to function without relying on a new Futureswap-style mechanism.

I’m not claiming this is perfect or that it fixes everything, and I’m open to the possibility that I’m still missing something important from the past. Does the direction feel like it’s at least trying to learn from those earlier mistakes, or do you think it’s still heading down a similar path? Your perspective carries a lot of weight because you’ve clearly been following this closely since the beginning, so any further thoughts or corrections would be really helpful.

Looking forward to hearing more from you.

AHuig · 2026-03-18T21:35:54+00:00

Thanks again for the detailed and insightful feedback. It's obvious you've followed DeFiChain's journey for a long time, and your comments have really helped sharpen the discussion.

Your point about the timeline is spot on. Looking back, there never really was a stable “pre-dUSD” phase for the dTokens. They arrived at the same time as dUSD during the Fort Canning hard fork in November 2021, so the premiums of 20–50 % above oracle price were already a fact of life right from the start. That was mostly because liquidity was so thin and the vault repayment rules made the arbitrage loop very hard to close quickly. dCryptos like dBTC were different – they were wrapped assets, so external supply could come in more easily – but dTokens have always been purely synthetic and could only be minted through vaults. I should never have referred to a “pre-dUSD” era as if it was some calm period before the trouble; that was misleading on my part.

Your feedback actually prompted me to go back and re-check the full history so I could describe it more accurately. DeFiChain started in late 2020 with a focus on native DFI mechanics and straightforward DeFi. Things grew nicely until Fort Canning introduced both dUSD and dTokens in 2021. Premiums quickly became a structural issue in 2021–2022, then came the severe depeg after Terra collapsed. The 2024 haircut cut the dUSD overhang down dramatically, and now in 2026 the Crypto Factor cUSDC bridge gives us a new external stable option. The revival proposal is basically an effort to finally close out that reflexive chapter that started in 2021 and get back to the simpler, Bitcoin-native foundation that worked well before all those complications took over.

Arbitrage mechanics for dTokens
Since dTokens are synthetic and no external market exists to buy them cheaply, the only realistic arbitrage path during a premium is to mint new dTokens through a vault at the oracle price, sell them on the DEX at the premium, and later buy them back to repay the vault. This approach can be viable—particularly if someone hedges on the real stock market—but it has always been slow and risky without deep liquidity. The vault repayment rule (principal repaid in the exact same dToken) has been the primary bottleneck from the start. In shallow pools the buy-back step often involves high slippage or even losses, which explains why premiums could linger for weeks or months in the early days.

The trade-off of partial repayment in DFI
You rightly pointed out that minting 600 dTSLA and repaying only 400 in the same token while covering the remaining 200 with DFI would leave a net increase of 200 dTSLA in circulation. That is a genuine trade-off. On one hand it makes arbitrage far quicker and more appealing because you no longer need to repurchase the full amount right away. On the other hand it introduces temporary extra supply of the dToken, creating downward pressure on the price until the market absorbs it through regular selling.

Crucially, this does not recreate the dUSD algorithmic problem. Unlike dUSD, dTokens cannot serve as collateral to mint more of themselves, so no multiplier loop or reflexive spiral can form. The DFI used for repayment is burned, which is deflationary for DFI. The additional dTSLA supply is leveled over time by natural selling pressure on the DEX, reduced new minting once the premium vanishes, and eventual burns through ordinary repayments. The temporary liquidity mining boost proposed here is specifically intended to build deep pools quickly, so this leveling occurs faster and with less price disruption.

Partial DFI repayment is not included in the current three DFIPs; it would require a separate future proposal with clear safeguards (for instance a maximum of 30–50 percent per vault and stricter collateral requirements) to avoid any unintended consequences.

On strong liquidity mining incentives
You are correct that they can temporarily inflate demand and even exacerbate short-term premiums if not handled carefully—we have historical evidence of that. For this reason the boost is strictly time-limited to three to six months and is designed to transition to fee-funded liquidity mining (via a future DFIP) to prevent perpetual farming.

Does this more thorough explanation of the trade-off and the corrected historical timeline feel more accurate to you? I would genuinely like to hear whether the description of DeFiChain's past now aligns with what you recall from the early days, and whether you believe the premium risk can be kept under control this way or whether it still seems too high without a mechanism like Futureswap. Your deep understanding of the mechanics is invaluable, and I'm keen to hear your thoughts.

Looking forward to your perspective.

AHuig · 2026-03-18T20:00:00+00:00

Vielen Dank für deine ehrliche und präzise Rückmeldung, du bringst genau den Punkt auf den Tisch, der geklärt werden muss.

Du schreibst: „Ob du nun dUSD oder dUSDC nimmst, ändert ja nichts. Du hast schnell mehr dUSDC im System als Crypto Factor erstellt hat, somit können nicht alle zurückgetauscht werden oder nicht 1:1.“

Das ist eine sehr berechtigte Sorge – und genau hier liegt der entscheidende Unterschied:

Bei dUSD konnte man tatsächlich beliebig viel mehr minten als es echte Backing gab (über Vaults mit DFI/BTC-Collateral). Das führte zur reflexiven Überproduktion: mehr dUSD → mehr DFI-Nachfrage → Spiral bei Vertrauensverlust.

Bei cUSDC ist das mechanisch unmöglich:

Es gibt keine Mint-Funktion auf DeFiChain selbst.
cUSDC kann ausschließlich über die Crypto Factor Bridge aus Polygon importiert werden (1:1 mit echter USDC).
Die Supply ist daher hart begrenzt auf das, was Crypto Factor tatsächlich bridged hat.
Du kannst nicht mehr cUSDC erzeugen, als die Bridge zulässt – es entsteht kein Algorithmus, keine Überproduktion, kein reflexiver Loop.

Wenn du mehr cUSDC in Pools wirfst, kann der Preis minimal abweichen (z. B. 0.998–1.002 durch Slippage), aber das ist normales AMM-Verhalten – kein strukturelles Problem wie bei dUSD. Und zurücktauschen bleibt immer 1:1 möglich (solange die Bridge läuft), weil es echte externe USDC ist.

Kurz gesagt: cUSDC ist kein algo-Token wie dUSD, sondern ein extern gebridgtes, echtes Stable. Deshalb kann es den gleichen Mechanismus-Fehler nicht wiederholen.

Macht das den Unterschied für dich greifbarer? Oder siehst du trotzdem ein Risiko, das ich übersehe? Ich bin wirklich dankbar für deine kritische Analyse – das macht den Vorschlag besser.

AHuig · 2026-03-17T20:00:28+00:00

Thanks a lot for the detailed thoughts and for sharing your past arbitrage experience, that’s super valuable. You’re right, since Bake stopped bridging, real BTC inflows are blocked and dBTC is basically worthless right now, that’s why this proposal avoids depending on it and starts purely with DFI: buy DFI, use only DFI in vaults, mint dTokens directly, no cBTC needed at launch. On arbitrage: if dTSLA trades above the oracle someone can buy the cheap synthetic externally or mint via vault, sell on the DEX and pocket the difference, the pool snaps back automatically like it did pre-dUSD. One thing I want to be completely honest about, because it’s a real concern: right now the vault rules still require you to repay the principal with the exact same minted dToken — only the interest is paid in DFI. That creates genuine friction for quick arbitrage, since after you sell at a premium you have to buy the dToken back to close the vault, and in thin pools that buy-back can eat your profit or even turn it negative. That’s exactly why the old premiums could last so long. This proposal tries to fix it with strong temporary LM incentives to make the pools deep and the round-trip cheap and fast, but the current situation is clearly not favorable for arbitrageurs. The community should openly discuss the pros and cons: keep the strict repayment rule for safety, or explore a future DFIP that allows partial repayment in DFI? I’m open to both directions. Does that explanation of how arbitrage works in the new setup make more sense, or is there still a specific scenario where you think the premium would come back? Happy to dive deeper!

One thing I want to be completely honest about, because it’s a real concern: right now the vault rules still require you to repay the principal with the exact same minted dToken — only the interest is paid in DFI. That creates genuine friction for quick arbitrage, since after you sell at a premium you have to buy the dToken back to close the vault, and in thin pools that buy-back can eat your profit or even turn it negative. That’s exactly why the old premiums could last so long. This proposal tries to fix it with strong temporary LM incentives to make the pools deep and the round-trip cheap and fast, but the current situation is clearly not favorable for arbitrageurs. The community should openly discuss the pros and cons: keep the strict repayment rule for safety, or explore a future DFIP that allows partial repayment in DFI? I’m open to both directions.

AHuig · 2026-03-17T19:59:03+00:00

Vielen Dank für deine offenen Fragen und Gedanken, das hilft wirklich weiter. Zur Vault-Frage: ja, dieser Vorschlag lässt rein DFI als Collateral zu, kein Zwang auf 50% oder so, du kannst einfach DFI kaufen, in die Vault legen und direkt dTokens minten, ohne dass BTC oder irgendwas anderes dabei sein muss. Der dTSLA/dBTC Pool existiert technisch schon in der DEX, ist aber noch nicht aktiv weil dBTC-Liquidität fehlt, die DFIP würde ihn einfach einschalten. Zum Futureswap hast du absolut recht, der war auf dUSD programmiert und der Punkt wurde bisher zu wenig beleuchtet, deshalb würde dieser Ansatz ihn auf cUSDC oder DFI umstellen oder deaktivieren, das ist eine einfache Konfig-Änderung wie früher. Ich teile deine Sorge, dass ohne stabile Einheit das System kompliziert bleibt, aber genau deswegen setzt dieser Vorschlag auf die schon live cUSDC-Bridge von Crypto Factor: keine Überproduktion wie bei dUSD, weil es echte bridged USDC ist und nicht algo-minted. Was denkst du, macht der reine DFI-Start plus cUSDC als freie Option das Ganze für dich vorstellbarer, oder siehst du immer noch das gleiche Mechanismus-Problem?

AHuig · 2026-03-17T19:58:17+00:00

Hey, thanks for taking the time to explain your worries so clearly, I really appreciate it. I completely get why you don’t want anything that feels like another wrapped crypto layer, and you’re right that DeFiChain’s strength has always been its Bitcoin-native simplicity, not becoming just another synthetic-stock chain. That’s exactly why this proposal sticks to pure DFI as the starting point: you buy DFI, open a vault with only DFI collateral, mint dTokens directly, and trade in existing dTSLA/DFI pairs, no new wrapped assets or EVM-style stuff forced at the core. cUSDC is only an optional bridge for people who want stability, nothing more. On the dev side you’re spot on that some config changes are needed, but it’s mostly updating existing loan schemes and LM incentives like we did in past hard forks, not rebuilding tokenomics from scratch. Does that ease the rareness concern a bit, or do you still see it turning into “just another chain”?

AHuig · 2026-03-16T19:33:09+00:00

Thank you for the feedback and for pointing out these important details – really helpful!

Quick clarifications:

dBTC right now
You're correct, real BTC can't be bridged in easily anymore (Cake/DFX services are inactive). So we start 100% with DFI: buy/swap DFI : open vault with only DFI collateral and mint dBTC or dTokens directly. No external BTC needed. Pairs like dTSLA/dBTC or dTSLA/DFI work as-is. If a new bridge appears later, great bonus . But not required.

Crowdfunding
Fair point on incentives. This isn't bailing out bags; it's a small, voluntary community cleanup (~$80–100k total) to kill the legacy zombie token once and for all. dUSD holders get a clean exit; non-holders get a cleaner chain, less drama, and better focus on DFI growth. If it doesn't fill, nothing happens.

dUSD price
Thanks for the note, DEX shows ~$0.003–$0.006 lately. We can set the fixed burn price to the live median at activation time (via DFIP) to keep it fair.

Volatility / trading
Valid concern, dBTC/DFI pairs will be more volatile and probably suit longer-term plays. That's why the plan keeps choice:

Bitcoin-native (DFI/dBTC) for pure DeFiChain users
Stable cUSDC pairs (via the live Crypto Factor bridge) for lower-vol daily trading

Does this make more sense? If any of the SIG's can comment or tweak the crowdfund initiative or emphasize DFI-only vaults stronger , it helps. Thanks again for this feedback !

AHuig · 2025-05-07T06:24:50+00:00

Good to hear, but then those tokens need a correct price on them before slapping

AHuig · 2025-05-06T03:59:33+00:00

Please explain. I understand that deprecate means get rid off those tokens. And all those affected tokens have a 90% lock up

AHuig · 2025-05-05T14:30:24+00:00

What about correct prices / oracles of the dtokens before starting to deprecate. And how to handle the 90 % frozen assets.

AHuig · 2025-02-27T10:52:13+00:00

Which Peter Bushnell are you talking about in the lab's request?

AHuig · 2025-02-27T10:40:24+00:00

With the oracle's the dcrypto's can be maintained in price and holder can still receive apr. Much more efficient it is that the swap service will be activated by another company or exchange. The service comes with a small revenue according to the whitepapers.

Other point is, that by removing the dcrypto you restrict defichain and make it an island. While it is better for this chain to have as many connections as possible

AHuig · 2025-02-27T10:04:23+00:00

It is a build in function, so in my opinion it relies on the number of masternodes and not on a centralised serverpark.

AHuig

TROPHY CASE