Live site: https://redbellydaotask17-one.vercel.app/
Source: https://github.com/poundeater/task17hub
The problem
Open the Redbelly DAO Discord on any given day and the same handful of questions surface on repeat. Someone new joins, connects a wallet, and immediately hits one of a small set of walls: their balance shows zero and they assume their funds are gone, they cannot tell mainnet from testnet in their wallet's network list, they do not know whether they need to complete KYC before they can do anything at all, or they get a DM from someone claiming to be Redbelly staff and are not sure if it is real.
A moderator answers. A different new user asks the same thing an hour later. Then again the next day. Multiply that across a growing community and the support queue is made almost entirely of repeat questions, each one answered from scratch or copy-pasted from an old message that is increasingly hard to find.
TASK-17 on the DAO's Community Task Board was written to close that loop: build one canonical page, get it right once, and give moderators a single link to paste instead of retyping an explanation for the hundredth time.
Scoping the deliverable
The task spec was specific about what counted as done: seven content sections, each covering one recurring question, an actual design pass rather than a plain FAQ dump, and cross-links to related resources so the page did not have to duplicate content that already existed elsewhere in the DAO's ecosystem.
The seven sections, in the order a new user actually needs them, are scam warning, KYC, network setup, the zero-balance explainer, where to buy and trade, staking basics, and the testnet faucet. Two constraints shaped almost every decision after that: nothing could be published without a source, and the page had to work on a phone, since nearly all of its traffic arrives as a link pasted into Discord and opened on mobile.
Sourcing before writing
Every factual claim on the page was checked against an official source before it was written: docs.redbelly.network, the Redbelly Individual Onboarding SDK overview, the Terms and Conditions, chainlist.org, and the ethereum-lists/chains repository for RPC and chain ID data. Where a claim could not be traced to a published document, it got a visible flag instead of a confident sentence pretending otherwise.
Two pieces of content ended up in that second category: the ten-wallet-per-identity activation limit and the typical three-to-five-minute KYC approval window, both confirmed firsthand and by a moderator in Discord but not written down anywhere official, and the entire zero-balance explainer below, which does not exist as a published troubleshooting guide anywhere. Both are marked directly in the content as community-verified rather than official, so a reader knows exactly which parts are backed by a doc and which parts are backed by someone who went and checked.
Section 1: Scam warning
Placed first, not buried, because it is the one piece of information that needs to reach someone before they click anything else. Redbelly staff, moderators, and official support never DM first. Any direct message claiming to be from Redbelly staff, offering support, or announcing a giveaway is a scam, no exceptions. The common patterns are unsolicited DMs offering help with a wallet or KYC issue, giveaway or airdrop claims requiring a wallet connection or seed phrase, and anyone asking for a seed phrase, private key, or wallet "verification" through a link. Official communication only happens through public channels: the site, official docs, and public Discord channels.
Section 2: KYC
KYC is required for native RBNT and mainnet activity: transactions, staking, and governance. It is not required to hold or trade wrapped RBNT on other chains. Redbelly gates its own Layer 1 behind identity verification through the Redbelly Access portal:
Access portal: https://access.redbelly.network/
Wrapped RBNT on Ethereum or other chains is a standard ERC-20 with no Redbelly-side identity check. One verified identity can activate up to ten wallets, and most submissions are approved in about three to five minutes, with manual review taking longer. That specific limit and timing are community-verified rather than published in an official doc.
Eighteen jurisdictions are currently restricted from accessing the platform, per Clause 15 of the Terms and Conditions: Afghanistan, Central African Republic, North Korea, Democratic Republic of the Congo, Guinea-Bissau, Iran, Iraq, Lebanon, Libya, Myanmar, Russia, Somalia, South Sudan, Sudan, Syria, Ukraine, Yemen, and Zimbabwe.
Section 3: Network setup
Two chains, never to be confused: Mainnet at Chain ID 151 and Testnet at Chain ID 153. Both are listed on the page with a one-tap "Add to wallet" button wired to wallet_addEthereumChain, so nobody has to copy-paste RPC fields by hand on a phone.
| Network | Chain ID | RPC | Explorer |
|---|---|---|---|
| Mainnet | 151 | https://governors.mainnet.redbelly.network | https://redbelly.routescan.io |
| Testnet | 153 | https://governors.testnet.redbelly.network | https://redbelly.testnet.routescan.io |
Chain ID 151 and 153 look close enough on a small screen that a copy-paste error between the two would be easy to make and hard to notice until something failed, so keeping the two cards structurally identical but visually and numerically distinct was as much a design decision as a content one.
Section 4: Wallet shows a zero balance
The task spec described this as a missing price-feed mapping issue, but that framing does not hold up against what actually happens in practice. In the overwhelming majority of cases, a wallet showing a zero balance for RBNT is a contract-recognition problem, not a price-feed problem, and it is almost always about wRBNT rather than native RBNT.
Native RBNT is the network's own gas token and does not need a contract address added anywhere to display correctly, the same way ETH does not need one on Ethereum. wRBNT is a wrapped ERC-20 on other chains, and if its contract address is missing or wrong in a given wallet, that wallet has no way to know what it is looking at, so it shows zero.
wRBNT contract addresses:
- Ethereum:
0xb45ffb51984d626ee758b336c61cf20990c6bf13 - Base:
0x020940df9f5e77338a094d55b5b5914122a804a5
The fix path on the page is a simple escalation: confirm the contract address is actually added, try a second wallet extension such as Rabby if it still shows zero, check the address directly on a block explorer if it is still not showing, and if it is genuinely not showing anywhere, confirm the original transfer or bridge transaction actually completed. The line that matters most is the last one on the page: a zero balance in your wallet does not mean lost funds. Almost every real case is a UI recognition gap, not a security incident.
Section 5: Where to buy and trade
Centralized exchanges:
- MEXC: https://www.mexc.com/exchange/RBNT_USDT
- Gate.io: https://www.gate.com/trade/RBNT_USDT
- WhiteBit: https://whitebit.com/trade/RBNT-USDT
- BYDFi: https://www.bydfi.com/en/spot/RBNT_USDT
Decentralized exchanges, Ethereum:
- 1inch: https://1inch.com/swap?src=1:0xb45ffb51984d626ee758b336c61cf20990c6bf13&dst=1:USDT
- OKX DEX: https://web3.okx.com/dex-swap?chain=ethereum,ethereum&token=0xb45ffb51984d626ee758b336c61cf20990c6bf13,0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
- Bitget Web3: https://web3.bitget.com/en/swap/eth/0xb45fFB51984d626Ee758b336C61Cf20990c6bF13
Decentralized exchanges, Base:
- KyberSwap: https://kyberswap.com/swap/base/0x020940df9f5e77338a094d55b5b5914122a804a5-to-usdc
- 1inch: https://1inch.com/swap?src=8453:0x020940df9f5e77338a094d55b5b5914122a804a5&dst=8453:USDC
- OKX DEX: https://web3.okx.com/dex-swap?chain=base,base&token=0x020940df9f5e77338a094d55b5b5914122a804a5,0xd9aaec86b65d86f6a7b5b1b0c42ffa531710b6ca
- Bitget Web3: https://web3.bitget.com/en/swap/base/0x020940df9F5E77338a094D55b5B5914122a804A5
Decentralized exchanges, Solana:
Redbelly native:
Bridges:
- Lucid Labs Bridge: https://bridge.lucidlabs.fi/
- Reddex Bridge: https://www.reddex.io/bridge
Native RBNT and wrapped RBNT are separate assets on different chains, so the page is explicit about checking which one a given venue actually lists before trading.
Section 6: Staking basics
RBNT can be staked to consensus or storage nodes to help secure the network and earn rewards. Staking is a mainnet action and requires KYC, the same as any other native transaction.
Stake on Reddex: https://www.reddex.io/stake
Available pools differ by lock period and reward rate, some with no lock and others locked for a fixed term at a higher rate. Rates and total value locked change constantly, so rather than hardcoding a snapshot that would be stale within days, the page points to the live staking dashboard for current numbers.
Section 7: Testnet faucet
Faucet: https://vine.redbelly.network/rbnt-faucet
FAUCETME-powered, 500 RBNT per claim, on Testnet Chain ID 153, with an effectively zero gas cost for deployment on testnet.
Design system
The page runs on the DAO Task Board's brand kit, called Kinetic Consensus: one accent color used consistently rather than a rotating palette, generous negative space, Be Vietnam Pro for every heading and body line, and JetBrains Mono reserved specifically for wallet addresses, chain IDs, and RPC URLs.
The build uses the brand kit's light theme: a near-white page background, white cards with a hairline border, and the accent color used for links and highlighted text rather than as a background fill anywhere near body copy, since a saturated red at small text sizes on a light background fails contrast checks fast. The solid brand red is reserved for primary button fills only.
Voice rules came with the brand kit as hard constraints rather than suggestions: no em dashes anywhere, no emoji, no filler verbs, plain and direct sentences. Writing an entire onboarding page without an em dash changes how you structure sentences, and by the end it reads more like a support document than marketing copy, which was the actual goal.
Closing thoughts
The most interesting part of this task was not the design work, it was deciding what belonged on the page at all. A Start Here hub only earns its name if it resists the urge to explain everything. Every section had a version that could have gone twice as long, and the harder edit was cutting it back to what someone standing at the front door of the DAO, wallet freshly connected, actually needs before doing anything else.
If you spot something wrong, especially in the zero-balance section since it is the one part without an official doc backing it yet, open an issue on the repo. That section in particular should get replaced with a link to a real docs page the moment one exists.
Top comments (0)