Crypto movement should not rely on the internet alone.
Tera is building a new way to prepare and hand off an action locally designed for the moments when connection is not guaranteed.
Offline Handoff is coming this week.
A quick reminder for the Tera community:
The proposed $TERA staking rewards are built for those who believe in the long-term vision.
30 days — 6% APY
45 days — 9% APY
90 days — 14% APY
The longer the commitment, the stronger the proposed reward.
With the wallet, private features, mobile launch, VIP membership, and more utility on the way, staking is about more than rewards. It is about being positioned for what Tera is building next.
Stay locked in.
Final terms, eligibility, and risk disclosures will be shared before launch.
Tera Wallet is now available for Internal Testing on Google Play.
We are opening access to 50 Android community members who want to help test the app before public launch.
To apply, email us from the Google account connected to your Android device and Play Store.
Email: [email protected]
Use this subject line:
Android Beta Test — [email protected]
Only 50 testers will be selected.
Selected testers will receive access to the Android beta and will help us test the app, share feedback, and identify anything that needs improvement before the wider release.
Please do not share your email address publicly in the group.
Let’s build the best version of Tera Wallet together.
Flight test for IOS coming soon too
Hey, have you claimed your Tera tag yet?
Update your app and claim one. People can then pay you at @yourname instead of forty hex characters.
Works Tera to Tera on Robinhood Chain. Your wallet resolves the name, shows you the address it points at, and you sign that. The name is a convenience, the address is what you approve.
https://t.co/HwLNxpyqhH
USDG Private Bridge is live in Tera Wallet.
Move USDG from Robinhood Chain to USDC on Base, Arc or Solana without your Robinhood Chain wallet appearing directly in the destination flow.
ETH is supported too. Review the route, quote and minimum received before you sign.
$TERA | @TeraWalletRH
Github: https://t.co/hzI76t5lJp
We are proposing bigger fixed rewards for staking $TERA.
The longer you commit, the higher the proposed reward tier:
30 days — 6% APY
45 days — 9% APY
90 days — 14% APY
This is about rewarding the people who believe in the long-term vision and choose to support the ecosystem as we keep building.
These are proposed fixed-reward tiers. Final terms, eligibility requirements, and risk disclosures will be shared before launch.
More details soon.
Private transfers just expanded on Robinhood Chain.
You can now send USDG and RWAs (SpaceX, Apple, Tesla, Nvidia & more) with complete sender-recipient link decoupling.
Zero Direct Link: Routed via isolated intake & payout vaults Multi-Asset: Native ETH, TERA, 6-decimal USDG & tokenized equities
Tera Tags: Send straight to @tag or any 0x address Zero Identity Leakage: Preflight eligibility without exposing your wallet
Self-custodial privacy built for real-world finance.
Try it now in the Tera Wallet app & web dashboard https://t.co/1T0wWqNvty
https://t.co/3ZImTjPePk
Once we reach a total burn of 25% of the TERA utility inside Tera Wallet.
TERA a clear role within the wallet as those features go live.
We are getting closer to the 25% milestone. More details will be shared soon.
Tera Wallet: Private Sends
Execute confidential token transfers using an advanced private routing engine designed to sever on-chain linkages between sender and recipient.
Separate Intake and Payout Routes: Send ETH or TERA through decoupled routing channels, keeping your transaction paths private.
End-to-End Tracking: Monitor every stage of the transfer lifecycle, from initial deposit confirmation to final recipient delivery.
Cross-Platform Availability: Access Private Sends right now across both web and native Android applications.
Confidential routing for self-custodied assets, available now.
https://t.co/tUTvaKoNwV
This week in Tera:
21% of supply burned, 380+ onchain holders, mobile preview out, Arc bridging live and new verification and receipt security shipped.
We also hosted our community AMA and shared the product demo.
Private Bridging and Private Send go live today.
A receipt naming a release that isn't in the approved-build registry used to get our strongest accusation: this build was never published.
But there's a second reason a release can be missing your copy of the list is just older than the receipt. Same absence, opposite meaning, and we shipped only the harsh reading. Anyone holding last week's registry got told a perfectly good receipt was forged.
Now the registry's publication date is compared against the receipt's. If the receipt is newer, absence proves nothing, and it says so.
Having a fourth state is only worth something if you use it when it applies.
Page: https://t.co/LnMMAClWjg
or node scripts/verify-receipt.mjs
https://t.co/Z0WNA5wHto
Private Bridging lands in Tera today.
Moving funds across chains should not expose more than the transaction needs to.
Private Bridging and Private Send give you a more private way to move across supported routes, while every transaction still comes back to you for review and approval.
Launch details and supported routes soon.
We gave Tera four verification states a few builds ago. Today we found two places that never got the memo and both were worse than the screen.
The redacted document you share with a counterparty said all five checks PASS while the wallet that made it said one couldn't be established. That document is the one that travels. No wallet attached, no caveat to click, kept as the record of what was known. It was the last place that should have been the most confident.
The version history was quieter. A check degrading from established to un-established returned the same string on both sides, so the diff was empty. The one moment the evidence got weaker was the one moment the history said nothing.
Both of our test suites passed before we changed a line, because neither had a fixture where a check passed without being established. That's how it survived.
https://t.co/mSr4Hik8ZJ
A receipt names the build that produced it. Tera's own check on that name has always said UNPROVEN compare it against the published manifest, while no published list of approved builds existed. A receipt could name r-0000000000 and read exactly as well as a real one.
That list exists now. Every release shipped, with its hash, signed.
A release missing from it fails. A release in it, from a list you can't authenticate, stays unproven because an unsigned list is a list anybody could have written.
You fetch the registry yourself. The wallet fetching its own copy would prove nothing.
https://t.co/KPG4W44yHf
A receipt tells you a turn was answered on your device. The page that wrote it is the one thing that can't vouch for that, a modified build reports whatever hashes it likes about itself.
So Tera now ships a verifier that runs somewhere else. A CLI, and a single HTML file you save to disk and open with the network off.
Both import the wallet's own checking code rather than re-implementing it. A verifier that drifts from the thing it verifies is worse than none.
It still tells you what it can't establish. Three of ten rows on a clean receipt read UNPROVEN, and they should.
https://t.co/5zWetsQ3i0