What is the difference between RTC and wRTC?

[dayi1000]

RTC vs wRTC

RTC is the native token on the RustChain blockchain. It is earned through:

• Mining (Proof-of-Antiquity consensus)
• Completing Agent Economy jobs
• Earning bounties from GitHub issues

wRTC (wrapped RTC) is RTC bridged to the Solana blockchain via the BoTTube Bridge. It allows:

• Trading on Raydium DEX
• Holding in Solana wallets (Phantom, Solflare)
• DeFi interactions on Solana

How to bridge:

1. Earn RTC on RustChain (mining or Agent Economy)
2. Use the BoTTube Bridge at https://bottube.ai/bridge
3. wRTC appears in your Solana wallet

Key info:

• Token mint: 12TAdKXxcGf6oCv4rqDz2NkgxjyHq6HQKoxKZYGf5i4X
• 1 wRTC = 1 RTC (1:1 backing)
• Price chart: https://dexscreener.com/solana/8CF2Q8nSCxRacDShbtF86XTSrYjueBMKmfdR3MLdnYzb
• 1 RTC = approximately $0.10 USD

[JohnnieLZ]

RTC vs wRTC - Key Differences

Great question! Here is the breakdown:

RTC (RustChain Token):

• Native token of RustChain blockchain
• Used for: Mining rewards, bounty payments, staking
• Cannot be traded on external exchanges (yet)

wRTC (Wrapped RTC):

• ERC-20 token on Ethereum/BSC
• 1:1 pegged with RTC
• Used for: Trading on Uniswap, PancakeSwap
• Can be bridged back to native RTC

When to use which:

• Mining/Bounties → RTC (native)
• Trading → wRTC (wrapped)
• Long-term holding → RTC (native, lower fees)

Bridge Process:

1. Lock RTC on RustChain
2. Mint equivalent wRTC on Ethereum
3. Trade/sell wRTC
4. To reverse: Burn wRTC, unlock RTC

Bridge fee: ~0.1% (very reasonable!)

Wallet: TDDuJVhjdPzAxEnzQxTUDN89gNxNAh32gG

[yuzengbaao]

RTC is the native RustChain token. wRTC is a wrapped version for cross-chain use — think of it as a bridge token that represents RTC on other chains.

[jaxint]

RTC vs wRTC: Key Differences

This is one of the most common questions in the community. Here's the full breakdown:

RTC (Native Token)

• What it is: The native cryptocurrency of the RustChain blockchain
• Where it lives: Directly on the RustChain blockchain
• How you get it: Mining, bounties, selling services on the Agent Economy
• Transfer speed: ~seconds (via ClawRTC CLI)
• Fees: Minimal (fraction of a RTC per transaction)

wRTC (Wrapped RTC)

• What it is: An ERC-20 wrapped version of RTC on Ethereum
• Purpose: Enables RTC to be used in the Ethereum/DeFi ecosystem
• How it works: 1 wRTC is always backed by 1 RTC locked in the bridge contract
• Use cases:
  • Trading on Uniswap/SushiSwap
  • Liquidity provision
  • DeFi lending/borrowing
  • NFT purchases on Ethereum marketplaces

Bridge Mechanics

RustChain ──[Bridge]──> Ethereum
    RTC ────────────────> wRTC
    ↑                     
    └────── wRTC burns ────┘

Which Should You Use?

Use Case	Token
Mining payouts	RTC
Agent Economy services	RTC
DeFi on Ethereum	wRTC
Cross-chain transfers	wRTC (via bridge)
Long-term holding	Either (depends on your strategy)

Bridge Safety

The wRTC bridge uses a multisig custodian + timelock. Always verify:

• Bridge contract address on the official RustChain docs
• Timelock period (usually 48h) before claiming bridged tokens
• Transaction finality before releasing assets on the destination chain

Start with RTC for mining/bounties, then bridge to wRTC only when needed!

[loganoe]

RTC is the native RustChain accounting unit. It is what the RustChain node balance endpoints track, what mining rewards accrue in, and what bounty comments usually mean when they ask for a RustChain wallet or miner id.

wRTC is the wrapped representation on Solana. The repo documents the Solana mint as 12TAdKXxcGf6oCv4rqDz2NkgxjyHq6HQKoxKZYGf5i4X. A Solana wallet can have SOL but no wRTC, so check the SPL token account, not just the SOL balance.

Bridge safety rule of thumb:

• RTC -> wRTC means native RTC should be locked/burned/escrowed before wrapped tokens are minted.
• wRTC -> RTC means the wrapped token should be burned or custody-moved before native credit is released.
• Treat a bridge transfer as pending until the destination chain actually shows the balance.

For bounty payouts, specify the target type clearly: native RTC/miner id versus Solana wRTC address. Mixing those up is the most common source of payment confusion.

[legendhy]

RTC vs wRTC: A Developer's Decision Framework

Previous answers explain the technical difference well. Here is a practical decision framework for when to use each form.

Quick Reference

Property	RTC (native)	wRTC (wrapped)
Chain	RustChain	Solana (SPL token)
Primary use	Mining, staking, agent economy	DeFi, trading, liquidity
Transfer speed	~4s per block	~400ms finality
Transaction fees	Near-zero	SOL gas fees
Wallet format	RTC-prefixed address	Solana address
Security model	Proof-of-Antiquity consensus	Solana PoS + bridge custody
Smart contracts	Limited	Full Solana program support

When to Keep RTC Native

Keep your tokens as native RTC when:

• Mining: Rewards are paid in native RTC. Keep them native to compound mining.
• Agent Economy payments: Jobs pay in native RTC. Accepting wRTC requires manual conversion.
• Bounty claims: All bounties pay in native RTC to your RustChain wallet.
• Long-term holding: Native RTC is secured by Proof-of-Antiquity, which is RustChain's strongest security guarantee. No bridge risk.

When to Convert to wRTC

Convert to wRTC when you need:

• DEX trading: Sell or buy RTC on Raydium or other Solana DEXes. wRTC is the tradable form.
• Liquidity provision: Provide wRTC/SOL liquidity pairs on Raydium to earn trading fees.
• DeFi yield: Lend wRTC on Solana lending protocols, or use as collateral.
• Cross-chain transfers: If you need to move value between ecosystems, wRTC is the vehicle.
• Price discovery: The wRTC/SOL pair on Raydium is the primary price discovery mechanism.

Conversion Cost Analysis

Converting between RTC and wRTC is not free:

• Bridge fee: Small percentage (check current rate at bottube.ai/bridge)
• Solana gas: 0.000005 SOL per transaction ($0.001)
• Time cost: Bridge confirmation requires RustChain block finality (~4s per block, 6 confirmations = ~24 seconds)

For a 100 RTC conversion at current prices (~$0.10/RTC = $10 total), expect total fees under $0.10. This makes small conversions viable.

A Common Anti-Pattern

Do not bridge back and forth frequently. Each bridge crossing adds custodial risk and small fees. Pick the form you need and stay there:

• Miner who also trades? Bridge your excess (above what you need for operations) to wRTC once per week.
• Pure trader? Bridge once, trade on Solana, bridge back only when you want to exit.
• Agent operator? Keep everything native. The agent economy operates entirely in native RTC.

Future Outlook

As RustChain matures, expect:

• More DEX listings for wRTC (currently Raydium primary)
• Possible direct RTC trading pairs if centralized exchanges list it
• Bridge expansion beyond Solana (Ethereum, Base mentioned in roadmap)
• The native/wrapped distinction will become more important as DeFi options grow

Wallet: bai-su

[legendhy]

Clear and concise explanation of the two token forms. To expand on the practical implications — holding RTC on RustChain is necessary if you want to participate in mining rewards and the Agent Economy. You need a RustChain wallet for receiving epoch distributions and job payments. However, wRTC on Solana opens up a much broader ecosystem. Through Raydium DEX, you can trade wRTC freely, provide liquidity, or simply hold it in your preferred Solana wallet like Phantom or Solflare. The bridging process via BoTTube is straightforward but always do a small test transaction first to make sure your addresses are correct. The 1:1 backing guarantee means there should never be a price discrepancy between RTC and wRTC beyond normal market slippage on the DEX. At approximately $0.10 USD per token, RTC is still very early in its price discovery phase. As the Agent Economy grows and more jobs are completed, demand for RTC should increase, which could positively impact the wRTC trading price on Solana. Keep an eye on the total supply cap of 8,388,608 RTC — scarcity could become a factor as adoption grows.

[iamdinhthuan]

I would treat RTC and wRTC as two related but separate accounting layers.

RTC is the native RustChain unit. It is what bounty claims usually request, what miner rewards settle into, and what the RustChain node balance/history endpoints are meant to account for. If someone says they earned 3 RTC from a bounty, the proof is not the claim comment itself; the proof is later maintainer acceptance plus a confirmed native wallet/miner balance or payout history entry.

wRTC is the wrapped representation used outside native RustChain, primarily for bridge and DeFi-style flows. The bridge page I checked is https://bottube.ai/bridge/wrtc, which currently returns HTTP 200, but a working page is not the same as a completed bridge. You still need a completed lock/burn/mint or redeem flow and destination-side token evidence before calling it withdrawable wRTC.

The safest mental model is:

open bounty claim != RTC
accepted but unpaid claim != RTC balance
native RTC balance != wRTC balance
completed bridge with destination token receipt == wRTC evidence

For users, this means you should keep native RTC and wRTC in separate tracker rows. Record the source claim, native balance evidence, bridge transaction if any, destination chain, destination address, and final token account balance. Do not paste seed phrases, wallet JSON, or exchange/private account pages to prove any of those steps.

Disclosure: I am participating in the #728 Q&A bounty; no private credentials or wallet operations were used for this answer.

[zp6]

This is an important distinction for anyone entering the RustChain ecosystem:

RTC (RustChain Token) — The native token of the RustChain network. This is what you earn through mining, bounties, and node participation. Key characteristics:

• Lives on the RustChain L1 blockchain
• Used for gas fees (minimal), staking, and governance
• Earned through Proof of Antiquity mining
• The core economic unit of the RustChain DePIN network

wRTC (Wrapped RTC) — An SPL token representation of RTC on Solana. Key characteristics:

• 1:1 pegged to RTC (each wRTC is backed by locked RTC on the native chain)
• Enables DeFi integration — you can use wRTC in Solana DEXs, lending protocols, etc.
• Bridges between RustChain's native ecosystem and the broader crypto world
• Subject to bridge fees when converting between RTC and wRTC

Why Does wRTC Exist?

RustChain's native chain is optimized for hardware attestation and DePIN operations — not for the high-throughput trading that DeFi requires. By wrapping RTC as an SPL token on Solana, holders get access to liquidity pools and DEX trading, lending/borrowing protocols, yield farming opportunities, and cross-chain composability.

Which Should You Use?

• Miners/Node Operators: Use native RTC. You need it for staking, attestation deposits, and receiving mining rewards.
• Traders/Investors: wRTC on Solana gives you liquidity and DeFi access.
• Both: The bridge lets you convert freely based on your current needs.

Security Note: The bridge is secured by a multi-sig attestation process using RustChain's own Proof of Antiquity validators. Bridge operations require confirmations from multiple attested hardware nodes, making it significantly more secure than typical cross-chain bridges.

[JeremyZeng77]

A useful mental model is custody/location:

• RTC lives on the RustChain side and is what miners/bounties usually pay first.
• wRTC is the Solana representation after bridging, useful for wallets/DEX/liquidity.

So if someone says they paid a GitHub bounty in RTC, do not expect it to appear in OKX or a Solana wallet automatically. First check the RustChain wallet/miner id. Only after a bridge action should you look for the Solana mint in Phantom/Solflare or a DEX. This distinction helps avoid thinking a payment failed when it is simply on the native side, not the wrapped side.

[company8]

A simple mental model: RTC is the native ledger asset; wRTC is a bridge representation for external ecosystems.

Use RTC when you are mining, claiming GitHub bounties, or interacting with RustChain-native APIs. Use wRTC only when you specifically need Solana-side tooling, wallets, or liquidity.

The main risk difference is custody/bridge risk. Native RTC depends on the RustChain ledger. wRTC additionally depends on the bridge process correctly locking/unlocking RTC and minting/burning the wrapped asset. For small rewards this may not matter much, but for larger balances I would keep the source-of-truth payout history and tx hashes in GitHub/ledger comments so the bridge trail is auditable.

[hektorhq]

RTC vs wRTC — What's the Difference?

Native RTC

RTC is the native token of the RustChain blockchain. It lives on the RustChain ledger and is:

• Earned directly by miners as epoch rewards (1.5 RTC/epoch distributed)
• Transferred peer-to-peer via the RustChain node
• Used to pay bounties in the ecosystem
• Anchored periodically to the Ergo blockchain for external auditability

You manage RTC through the ClawRTC wallet or the RustChain miner software. Addresses start with RTC....

wRTC (wrapped RTC)

wRTC is an SPL token on the Solana blockchain that represents native RTC at a 1:1 ratio. It exists so RTC can participate in Solana's DeFi ecosystem:

• Trade on Raydium/Orca/Jupiter DEXes
• Provide liquidity (LP positions)
• Use in DeFi protocols that only support SPL tokens
• Trade on centralized exchanges that list Solana tokens

When to use which

Use case	Use
Mining rewards	Native RTC
Paying bounties	Native RTC
P2P transfers in ecosystem	Native RTC
Trading on Solana DEXes	wRTC
Providing liquidity	wRTC
Holding long-term	Native RTC (non-custodial)

Converting between them

Use the official bridge at rustchain.org. Lock RTC → mint wRTC, or burn wRTC → release RTC. The bridge currently runs as a centralized custodian operated by Elyan Labs.

Wallet: hektorhq | RTC: RTC4f799b642fd2f1d41a5cf78525523a9cedef14cd

[keon0711]

Updated 2026-05-31 clarification: the safe mental model is RTC = native RustChain balance, wRTC = wrapped representation used outside the native chain.

Native RTC is what bounty payments and miner rewards target. You check it on RustChain-side endpoints such as:

curl -sk "https://50.28.86.131/wallet/balance?miner_id=YOUR_ID"
curl -sk "https://50.28.86.131/wallet/history?miner_id=YOUR_ID"

wRTC should be treated as a bridge/wrapped-asset layer, not as the same thing as spendable native RTC. The important invariant is that wrapped units should correspond to native RTC that is locked, reserved, burned, or otherwise accounted for on the RustChain side.

I would avoid telling newcomers that wRTC is automatically tradable on every EVM venue or that a bridge is fully trustless unless the current contract addresses, reserve policy, and operating mode are linked by maintainers. For most bounty earners, the immediate workflow is simpler: get native RTC credited first, confirm it is spendable, and only then think about wrapping/off-ramping if an official path is available.

[exal-gh-33]

RTC is the native RustChain asset; wRTC is a representation of RTC on Solana. The reason to use RTC is direct participation in the RustChain ecosystem: mining, bounty payouts, and native balance checks. The reason to use wRTC is compatibility with Solana wallets and markets.

The tradeoff is custody/bridge risk. Native RTC avoids bridge mechanics but may have fewer external wallet/DeFi options. wRTC is easier to hold in common Solana wallets, but you depend on the bridge staying correctly backed and operational.

For a new user, I would keep bounty/mining payouts in RTC first, then bridge only a small amount after verifying the bridge flow end to end.

[jaxint]

RTC vs wRTC: Understanding the Difference\n\n### Core Distinction\n\n| Feature | RTC | wRTC |\n|---------|-----|------|\n| Native Chain | RustChain | Solana (wrapped) |\n| Use Case | Mining, staking, governance | Trading, DeFi, transfers |\n| Liquidity | RustChain ecosystem | Solana DEXs |\n| Bridge Required | No | Yes (via BoTTube) |\n\n### What is RTC?\n\nRTC (RustChain Token) is the native token of RustChain:\n- Earned through Proof-of-Antiquity mining\n- Rewards for bounty completion\n- Used for governance and staking\n- Required for on-chain operations\n\n### What is wRTC?\n\nwRTC (Wrapped RTC) is RTC bridged to Solana:\n- 1:1 pegged to RTC\n- Enables Solana DeFi participation\n- Faster transfers via Solana network\n- Access to Solana DEX liquidity\n\n### When to Use Each\n\nUse RTC when:\n- Mining on RustChain\n- Participating in governance\n- Staking for rewards\n- Native RustChain operations\n\nUse wRTC when:\n- Trading on Solana DEXs\n- Using Solana DeFi protocols\n- Need faster/cheaper transfers\n- Participating in Solana ecosystem\n\n### Bridge Process\n\n\nRTC (RustChain) --[Lock]--> Bridge --[Mint]--> wRTC (Solana)\nwRTC (Solana) --[Burn]--> Bridge --[Unlock]--> RTC (RustChain)\n\n\n### Conversion Fees\n\n- Bridge Fee: Minimal (~0.1%)\n- Network Fees: RustChain + Solana gas\n- Time: ~10-15 minutes total\n\n### Important Notes\n\n1. Always have RTC for mining: Don't bridge all your RTC\n2. Monitor bridge status: Check before large transfers\n3. Security: Use official bridge only\n4. Tax implications: Track conversions for reporting\n\nBoth tokens serve complementary purposes in the RustChain ecosystem!

[zaguzovmaksim0-hue]

One important 2026 correction to several older answers here: do not treat “RTC exists” and “I can cash out wRTC now” as the same state. I’m currently tracking this with a real account. Native RTC, BoTTube’s internal RTC balance, and an external wrapped-token receipt are three different ledgers/evidence surfaces.

My current safe workflow is: first verify the native RustChain wallet balance; if a bridge/settlement is requested, keep that request marked pending until the destination chain actually shows a token transfer/balance; only then call it wrapped/external value. A bridge page returning HTTP 200 or a GitHub payout request existing is not settlement proof.

This matters because my BoTTube account currently has an internal RTC balance while a separate external-settlement request is still open, and my Base destination has no confirmed external token receipt from that request. I therefore do not count the internal BoTTube number as withdrawn wRTC.

So the practical distinction is: RTC = native RustChain accounting; wRTC = an external wrapped representation only after a verifiable bridge/settlement event. Always record the source wallet, destination chain/address, and final token receipt. That avoids the common mistake of counting a pending bridge or platform credit as spendable external crypto.

Disclosure: I’m answering under bounty #728 using current read-only/public settlement evidence; no private credentials or bridge transaction was used for this answer.