Feasibility report · 15 October 2026
Could Redbelly connect to Quant Overledger?
A feasibility report on interoperability between Redbelly Network and Quant's Overledger
Feasibility research only. Redbelly and Quant have no announced partnership or talks[1], and nothing in this report suggests otherwise. Redbelly has not published an official position on bridging[1], so anything not found in a public source is marked Unknown.
How to read this report
- Confirmed
- Stated in a public source. The source is linked and quoted in the source list.
- Tested
- We ran the call ourselves on 15 October 2026. The full log is in evidence/tests.
- Analysis
- Our reasoning from the confirmed facts it cites. Not a statement by Redbelly, Tokeniser or Quant.
- Unknown
- Not answered by any public source we found. Treat as open.
Key findings
| Question | Answer | Status |
|---|---|---|
| Can Redbelly reach Overledger's Gateway today, for reading data and sending signed transactions? | Possibly yes, as a self-serve EVM network, but nobody has shown it working. Four open points need a test with an Overledger account.[2, 3, 4] | Analysis |
| Can Redbelly join the Fusion Rollup, Overledger's shared layer for deposits, unified token balances and cross-chain messages? | Not possible yet. Redbelly is not among the documented connected networks, and the docs describe no self-serve way to add one.[5] | Confirmed |
| Would Receptor credentials and Tokeniser rules travel with an asset to another chain? | No, not by themselves. They are enforced on Redbelly. Another chain only applies the rules its own contracts and policies enforce.[6, 7, 8] | Analysis |
| Is there any agreement between Redbelly and Quant? | None has been announced.[1] | Confirmed |
1. Why this question comes up now
On 24 September 2026 The Clearing House said it selected Quant to power its On-Chain Money Initiative, a payments network for clearing and settling tokenised deposits between financial institutions[9]. Quant's technology is to provide the network's interoperability, orchestration and transaction management layer[9], with connectivity to existing payment systems such as RTP and CHIPS[9]. Quant's own release says the same[10].
The network is expected to be available to participating institutions in the first half of 2027, and details on participation and use cases are still to be announced[9].
Neither announcement says which blockchains the network will reach. Whether it will connect to any public chain, Redbelly included, is not public[9].
2. What Overledger is
Overledger is Quant's platform for building applications that span more than one blockchain[11]. It has three foundations: a Gateway that authenticates clients and routes requests[12]; Connectors that hide the differences between each chain's interface behind one common interface[12]; and the Fusion Rollup, a shared layer that anchors to several chains at once and supports deposits, withdrawals and cross-chain messages between them[12].
In plain terms, the Gateway and Connectors are a switchboard: one login and one interface to talk to many chains. The Fusion Rollup is different. It is a separate chain run by Quant's system that holds tokens deposited from the chains connected to it. A chain can be reachable through the switchboard without being connected to the Fusion Rollup[12].
3. How chains connect to Overledger today
There are two routes. The self-serve route covers six chain families, including EVM, where an account can register a node and use the network without talking to Quant's account team[2]. The EVM family covers every EVM compatible chain[2]. The managed engagement route is for private or consortium networks, and for chain families Quant does not support yet[12].
A chain family qualifies for self-serve when its nodes offer an interface over HTTPS, need nothing beyond an API key, and it does not matter which node a client uses[2]. Networks where node identity matters, such as permissioned consortium chains and operator-gated public chains, are not self-serve today[2].
A chain that is not listed yet, but belongs to a supported family, is added with the same registration call that adds a node. The first registration creates the network, and it then becomes available to other Overledger users[2].
Each node is registered as public or private. A public node is shared with all users and must come from an approved provider, and a private node can be any address but only its owner can use it[2]. The approved providers are Alchemy, Infura, QuickNode, Chainstack, GetBlock, Blockdaemon and Ankr[2], and a public node URL must carry the provider's API key[2]. A private node can be any reachable HTTPS address[2]. Every node must pass a health check before it is used[2].
When a brand-new chain family is needed, the documented effort is about 2 days for a health and chain identity checker, plus about 1 day for each app that needs to use it[2].
4. The Redbelly facts that matter here
Redbelly is a layer 1 blockchain built for real world asset tokenisation[14]. It is compatible with the Ethereum Virtual Machine and runs smart contracts written for it[3]. Mainnet is chain ID 151 with a public RPC address[15], and Redbelly lists Ankr as a third-party public RPC provider for mainnet[15]. Testnet is chain ID 153[15].
On 15 October 2026 the official mainnet RPC and the Ankr RPC both answered with chain ID 151 (0x97)[4], and returned blocks[4]. The method net_version, which some older tools use to identify a network, returned "method does not exist"[4].
Writing to Redbelly is gated by identity. Every user must claim an access credential from an accredited issuer before their account can write to the network[8], and all participants must prove who they are before gaining access[16]. Accredited issuers are listed in an on-chain registry[17]. Businesses can be verified as incorporated entities[18], and even node operators need network access for their accounts[19].
Receptor is Redbelly's identity and verifiable credential protocol[20], built on the W3C verifiable credential data model[20]. It supports two methods[21]. Proof by Query uses a zero knowledge verifier smart contract[7] and publishes identity state to the chain[7]. Selective Disclosure reveals chosen details to a verifier and can only be used off-chain[22]. The identifiers of Redbelly's accredited credential issuer are specific to Redbelly[23], and apps can use eligibility checks to control who may call their contract functions[24].
Tokeniser runs on Redbelly[6] and enforces eligibility, identity and target market rules at the point of transfer, every time[6]. Before any trade proceeds, identity, eligibility and limits are checked[25]; transfers are recorded on the register in real time[26]; and pledged units stay locked until a loan is repaid[27]. Redbelly settles a transaction in a single round[6].
Redbelly already has token bridges. Its developer portal lists routes through Celer cBridge[28], LayerZero with Stargate[29] and Lucid Labs[30]. Celer uses a pegged bridge method[31]. Redbelly announced Wrapped RBNT on Ethereum with the contract 0xb45f...bf13[32], which the portal lists under Lucid Labs[30]. The portal lists a different Ethereum contract for the Celer route[28].
5. Can Redbelly connect now, and what is missing?
A connection can mean three different things. Each has a different answer.
Level 1: reaching Redbelly through the Overledger Gateway. Possibly yes, untested.
Redbelly is EVM compatible[3], and Overledger's EVM family covers every EVM compatible chain[2]. An unlisted network in a supported family can be added by the first node registration[2]. Redbelly appears to meet the three self-serve tests: its RPC works over HTTPS[4], reading needs no key[4], and Redbelly's access control applies to accounts, not to which node a client connects to[8]. Ankr, an approved provider[2], runs a Redbelly mainnet endpoint[15], and the official RPC could be added as a private node[2].
This level gives an institution one interface to read Redbelly data and send transactions it has signed itself. The Gateway forwards each request unchanged[2], so every Redbelly rule still applies. A transaction sent this way only succeeds if the sending account has Redbelly write access[8].
Four points are open. First, the docs do not say which call the EVM health check uses[2]; if it relies on net_version, which Overledger still offers to older tools[5], Redbelly's answer[4] could fail the check. Second, a public node URL must carry a provider API key[2], and we did not confirm that Ankr's keyed service covers Redbelly. Third, the live network list[36] needs an Overledger login[37], so we could not see whether Redbelly is already listed. Fourth, Quant could still decide to treat Redbelly as an engagement network[2].
Level 2: Overledger Flow Apps on Redbelly. Unknown.
Flow Apps run signing and other workflows[12]. The catalogue is not published[13] and every shipped app is built by Quant[13], so whether a given app accepts a self-serve EVM network such as Redbelly cannot be checked from public sources. If an app needs extra work for a new chain, the documented effort is about a day per app[2].
Level 3: joining the Fusion Rollup. Not possible yet.
The documented connected networks at testnet launch are Ethereum Sepolia, Polygon Amoy and Quant's permissioned Besu testnet[5]. Each connected chain carries the rollup's bridge and dispute contracts[5] and receives the rollup's state[5]. Token entries on the bridge are controlled by Quant's governance signers[38].
The documentation we read describes no self-serve way to add a chain to the Fusion Rollup. On Redbelly, every account that writes needs an access credential[8], so the accounts that deploy those contracts and post rollup state would each need Redbelly network access, and the organisation running them could be verified as a business[18]. This is the main missing piece for Level 3, and only Quant and Redbelly could resolve it.
6. The technical work a connection would need
Written for a non engineer. Steps marked Level 1 are small. Steps marked Level 3 need both Quant and Redbelly to take part, and no such work has been announced[1].
- Level 1, step 1: someone with an Overledger account registers a Redbelly node, either the official RPC as a private node or an approved provider's endpoint as a public node[2]. This is one form or one API call.
- Level 1, step 2: the node has to pass Overledger's health check[2]. If the check fails on Redbelly, Quant would need to adjust its EVM checker; the documented effort for a full new checker is about 2 days[2].
- Level 1, step 3: each institution that wants to send transactions needs a Redbelly access credential for every sending address[8], and business verification for the organisation[18]. They can sign with their own keys[13].
- Level 3, step 1: the rollup's standard bridge and dispute contracts are deployed on Redbelly[5], from accounts that hold Redbelly access[8].
- Level 3, step 2: the rollup's services start posting rollup state to Redbelly[5].
- Level 3, step 3: each token that should move is added to the bridge token list by Quant's governance[38].
- Level 3, step 4: issuers decide whether their asset contracts may hold or release tokens to the bridge contract, because Tokeniser checks eligibility on every transfer[6].
- Level 3, step 5: someone has to keep Overledger's own allowlists[38] in step with Receptor credentials, because the two systems do not read each other.
Registering a node is a technical action any Overledger account can take[2]. It would not by itself mean any agreement between Redbelly and Quant.
7. What a connection could offer institutions
- One interface. An institution that already reaches other chains through Overledger[11] could read Redbelly and send its own signed transactions through the same Gateway, under the same firewall rules[38], without running its own Redbelly integration.
- Rules stay on Redbelly. At Level 1 the Gateway only forwards requests[2], so Receptor access and Tokeniser eligibility checks still apply to every transaction[6, 8].
- Key control. Institutions can keep and use their own keys in Overledger's model[13], which matches how a regulated holder would expect to operate.
- Unified balances, only at Level 3. The Fusion Rollup can merge copies of the same token from several chains into one balance[5]. This is not available to Redbelly today[5].
- A possible route to tokenised deposit networks. The Clearing House network will use Quant for interoperability[9]. Whether that network will ever reach Redbelly, or any public chain, is unknown[9].
Limits to weigh. Redbelly already connects to other chains through Celer, LayerZero and Lucid Labs[28, 29, 30], and Tokeniser points to EVM compatibility as its link to other networks[6]. Overledger would add an institutional access layer rather than a first route out. Level 3 would add another operator to the trust chain, and withdrawals from the rollup wait for a dispute window[5], unlike Redbelly's single round settlement[6].
8. Receptor credentials and Tokeniser assets across chains
How Receptor credentials would behave
A Receptor credential is a W3C verifiable credential held by the user[20]. Its two uses travel differently. A Selective Disclosure proof is checked off-chain[22], so in principle any verifier could check it, including an externally hosted Overledger Flow App[12]; none exists today[13]. A Proof by Query check runs in a verifier contract against identity state published on Redbelly[7], so another chain cannot run the same check unless that setup is rebuilt there. The access credential that unlocks write access works only on Redbelly[8].
How Tokeniser assets would behave
A Tokeniser asset carries its rules in Redbelly contracts that check every transfer[6, 25]. A bridge moves an asset by locking it on one chain and issuing a copy on the other[33]. The copy obeys only the rules of the contract and policies on the other chain. Overledger's firewall decides access from its own list of users and their addresses[38], not from Receptor credentials.
Where compliance could break
- A copy on another chain without eligibility checks could be passed to someone who never proved eligibility on Redbelly[6].
- Two lists of who is allowed: Receptor credentials on Redbelly[8] and Overledger's allowlists[38]. If they drift apart, one system allows what the other refuses.
- A revoked credential on Redbelly[8] does not reach a copy held elsewhere unless someone updates the other list[38].
- Merged balances[5] could mix a restricted asset with an unrestricted copy of the same asset.
- The list of tokens that may cross the Fusion bridge is set by Quant's governance[38], not by the issuer.
- The register is kept on Redbelly in real time[26]. Units held on another chain, or locked in a bridge[27], need clear treatment in that register.
- Settlement timing changes: rollup withdrawals wait for a dispute window[5], while Redbelly is final in one round[6].
9. Not possible yet, and unknown
| Question | Answer today |
|---|---|
| Joining the Fusion Rollup | Not possible yet[5] |
| Receptor credentials recognised by Overledger's firewall | Not possible yet, no documented link[8, 38] |
| Tokeniser rules enforced on copies held on other chains | Not possible yet, only the destination's rules apply[6, 33] |
| Whether Redbelly passes Overledger's EVM health check | Unknown, needs a test with an account[2, 4] |
| Whether Redbelly is already in Overledger's live network list | Unknown, the list needs a login[37] |
| Whether Flow Apps work with Redbelly | Unknown, catalogue not public[13] |
| Which chains The Clearing House network will reach | Unknown[9] |
| Redbelly's position on bridging or on Overledger | Unknown, nothing published[1] |
| Any plan by Redbelly or Quant to connect | None announced[1] |
10. How this report was made and how to check it
Every source page was saved as a text snapshot on 15 October 2026, with its address, capture time and SHA-256 hash in evidence/manifest.json. Each factual claim cites a fact, and each fact quotes its source word for word. The script scripts/check.py confirms that every quote is in its snapshot, that every Confirmed paragraph cites a source, and that the text has no partnership wording, no investment language, no dashes and no emoji. We ran the RPC and API calls ourselves, and kept the full output in evidence/tests. We did not create an Overledger account, so nothing here was tested inside Overledger.
Community summary
Plain language, ready to share. The same text is in COMMUNITY-SUMMARY.md.
Could Redbelly connect to Quant's Overledger? We looked only at public documents. Redbelly and Quant have not announced any partnership or talks, and this research does not suggest any.
Overledger is Quant's platform for reaching many blockchains through one interface. It supports any EVM chain through a self-serve route, and Redbelly is EVM compatible. So a basic connection, reading Redbelly and sending transactions that the sender has signed, looks possible, but nobody has tested it yet. Every Redbelly rule would still apply, including the access credential that every sending account needs.
Overledger's Fusion Rollup, its shared layer for moving tokens between chains, does not include Redbelly, and there is no self-serve way to add a chain. That part is not possible today.
Receptor credentials and Tokeniser's eligibility rules are enforced on Redbelly. They do not travel with a token to another chain. Keeping regulated assets on Redbelly avoids that gap.
Open questions: whether Redbelly passes Overledger's network check, which chains The Clearing House network will reach, and Redbelly's own position on bridging. The full report and every source are linked below.
As an X thread
- 1/ The Clearing House picked Quant to power its tokenised deposit network, so people are asking: could Redbelly connect to Quant's Overledger? We read the public docs. No partnership or talks between Redbelly and Quant have been announced.
- 2/ Overledger reaches many chains through one interface. Any EVM chain can be added through a self-serve route, and Redbelly is EVM compatible. A basic connection for reading data and sending signed transactions looks possible, but it is untested.
- 3/ Redbelly's rules still apply on that route. Every account that sends a transaction needs a Redbelly access credential, and Tokeniser checks eligibility on every transfer.
- 4/ Overledger's Fusion Rollup, which moves tokens between connected chains, does not include Redbelly and has no self-serve way to add a chain. Not possible today.
- 5/ Receptor credentials and Tokeniser rules do not travel with a token to another chain. A copy elsewhere follows only that chain's rules. Keeping regulated assets on Redbelly avoids the gap.
- 6/ Still unknown: whether Redbelly passes Overledger's network check, which chains The Clearing House network will reach, and Redbelly's position on bridging. Full report with a source for every claim: https://overledger.test-hub.xyz
Source list
Every factual claim links to one of these sources. Under each source are the exact words the report relies on. Text snapshots of every page, with SHA-256 hashes, are in evidence/ in the project repository.
Redbelly DAO Task Board: TASK-29 brief: Quant Overledger and Redbelly Interoperability Research
https://taskboard.redbellydao.network/tasks/TASK-29- “This is feasibility research only. Redbelly and Quant have no announced partnership or talks”
- “Redbelly has not published an official position on bridging”
Quant, Overledger documentation: Chapter 5: Connectors
https://docs.overledger.dev/docs/connectors- “Six DLT families are available for self-serve onboarding today, you can register a node and call the network without an account-team conversation”
- “Covers every EVM-compatible chain”
- “A DLT family is considered eligible for self-serve if (a) its nodes expose RPC or REST over HTTPS, (b) the RPC requires no security factor beyond an API key, and (c) node identity does not matter to other tenants (so a pool of equivalent nodes can be load-balanced safely).”
- “New network within a supported DLT family, the network is not yet listed by Overledger, but its DLT family is one Overledger already supports for self-serve (EVM, Solana, Cosmos, SUI, Hedera, Aptos). The first POST /nodes call registers both the network and your node for it. This new network will then be available for Overledger users.”
- “If public is selected then the user can only add nodes from whitelisted providers. If private is selected then the user can add nodes from any domain.”
- “alchemy.com, infura.io, quiknode.pro, chainstack.com, getblock.io, blockdaemon.com, ankr.com”
- “Required, embedded in the URL path (the Gateway forwards the URL as-is), not a header.”
- “Any reachable HTTPS URL, self-hosted, custom-provider, on your own infrastructure, anywhere.”
- “The Gateway runs a health check using the DLT's standard validation from section 5.1 and, on success, adds the node to the network's load-balancing pool.”
- “For networks where node identity matters, typically permissioned DLTs used by regulated consortia and operator-gated public chains, Overledger does not self-serve currently.”
- “Implement a DLT checker (health validation + chain identifer lookup) ~2 days”
- “Add per-DLT handling in any apps that need to consume it ~1 day per app”
- “Forwards the payload, returns the native response unchanged.”
Vine, Redbelly Network developer portal: EVM compatibility and version details
https://vine.redbelly.network/consensus/evm-compatibility/- “Redbelly is compatible with the Ethereum Virtual Machine (EVM) and can execute smart contracts written for the EVM.”
Test run for this report: JSON-RPC calls to Redbelly mainnet and testnet endpoints, 15 October 2026
evidence/tests/rpc-check.txt in the project repository- “https://governors.mainnet.redbelly.network eth_chainId -> {"jsonrpc":"2.0","id":1,"result":"0x97"}”
- “https://rpc.ankr.com/redbelly_mainnet eth_chainId -> {"id":1,"jsonrpc":"2.0","result":"0x97"}”
- “https://governors.mainnet.redbelly.network net_version -> {"jsonrpc":"2.0","id":1,"error":{"code":-32601,"message":"the method net_version does not exist/is not available"}}”
- “eth_getBlockByNumber -> {"jsonrpc":"2.0","id":1,"result":{”
Quant, Overledger documentation: Chapter 8: Fusion Rollup
https://docs.overledger.dev/docs/fusion-rollup- “Connected DLT networks on testnet launch are: Ethereum Sepolia, Polygon Amoy, Quant's permissioned Besu testnet. The full live list comes from GET /networks/fusion.”
- “The bridge and dispute contracts deployed on each connected DLT network. Standard OP Stack contracts, one deployment per chain.”
- “Compute Fusion Rollup state roots and post them to all connected DLT networks for settlement”
- “Because Fusion is an optimistic rollup, a withdrawal is not immediately final, there is a dispute window during which a challenger can prove the Fusion Rollup state root invalid.”
- “Fusion can map several token contracts to a single rollup-side ERC-20, so deposits from any of those source chains land in one unified balance.”
- “Network ID. Exposed for wallets and tools that predate eth_chainId.”
Tokeniser: Technology
https://tokeniser.com/technology- “Eligibility, identity and your target market determination are enforced at the point of transfer, every time.”
- “Deterministic finality settles a transaction in a single round, final the moment it completes.”
- “full EVM compatibility connects you to more than 150 networks out of the box”
- “Underneath it runs Redbelly Network”
Redbelly Network technical documentation: Proof by Query
https://docs.redbelly.network/pages/methods/proof-by-query/- “a zero knowledge proof based verifier smart contract”
- “State verification and transition, with subsequent publication to the blockchain.”
Vine, Redbelly Network developer portal: User access
https://vine.redbelly.network/identity/user-access/- “Before being granted access to Redbelly Network, each user must claim their access credential from a network accredited issuer before they self enable their account with write access to the network through a specific network smart contract.”
The Clearing House: The Clearing House Partners with Quant to Advance the On-Chain Money Initiative (24 September 2026)
https://www.theclearinghouse.org/payment-systems/Articles/2026/09/The-Clearing-House-Partners-with-Quant-to-Advance-the--On-Chain-Money-Initiative- “The Clearing House announced the selection of Quant, a leading provider of programmable money infrastructure, to power its On-Chain Money Initiative, a new interoperable payments network that will enable financial institutions of all sizes to clear and settle tokenized deposit transactions.”
- “Quant's technology will enable the network's interoperability, orchestration, and transaction-management layer that coordinates the clearing and settlement of tokenized deposit transactions”
- “providing connectivity to existing fiat payment systems that financial institutions and their customers use every day, including the RTP® and CHIPS® networks”
- “The network is expected to become available to participating institutions in the first half of 2027, with additional details on participation and use cases to be announced as development progresses.”
Quant: Press release: The Clearing House Partners with Quant to Advance the On-Chain Money Initiative
https://quant.network/press-releases/the-clearing-house-partners-with-quant-to-advance-the-on-chain-money-initiative/- “The Clearing House will use Quant's technology to bring on-chain capabilities to its tokenised deposit clearing and settlement network for financial institutions.”
Quant, Overledger documentation: Start Here
https://docs.overledger.dev/docs/start-here- “Overledger is Quant's multi-DLT platform for building applications that span more than one blockchain”
Quant, Overledger documentation: Chapter 1: Overview
https://docs.overledger.dev/docs/overview- “A Gateway that authenticates clients, routes requests, and orchestrates higher-level workflows.”
- “A set of Connectors that abstract individual DLT RPC protocols behind a common interface.”
- “A Multi-ledger rollup (the Fusion Rollup) that anchors to multiple blockchains simultaneously, providing one EVM-compatible execution environment with deposits, withdrawals, and cross-chain messaging across every connected L1.”
- “Customers and partners can host their own Flow Apps externally, stand up an HTTPS service that implements the Flow App contract, register its URL with the Gateway, and your bespoke regulated workflow becomes a first-class app in Overledger.”
- “Managed engagement: you work with Quant's team to onboard a private / consortium network (e.g. Corda, Canton, Fabric) or to add a brand-new DLT family Quant doesn't yet support.”
Quant, Overledger documentation: Chapter 6: Flow Apps
https://docs.overledger.dev/docs/flow-apps- “today every shipped app is internal”
- “The Flow App catalogue is intentionally not enumerated in these docs”
- “Three phases between Client, Gateway, Flow App, and Signer Flow App. The Sign phase hands off via a sub-flow; the Client never sees private-key material.”
- “You hold the keys (BYO signing, see chapter 7.2).”
Redbelly Network technical documentation: Home
https://docs.redbelly.network- “The Redbelly Network is a layer 1 blockchain, built and optimised for real world asset tokenisation.”
Vine, Redbelly Network developer portal: Redbelly Network environments
https://vine.redbelly.network/environments/- “Network name: Redbelly Network Mainnet RPC URL: https://governors.mainnet.redbelly.network Chain ID: 151”
- “Ankr https://rpc.ankr.com/redbelly_mainnet”
- “RPC URL: https://governors.testnet.redbelly.network Chain ID: 153”
Vine, Redbelly Network developer portal: Identity and participation on the network
https://vine.redbelly.network/identity/- “all network participants MUST prove they are who they say they are before gaining access”
Vine, Redbelly Network developer portal: Accredited issuers
https://vine.redbelly.network/identity/accredited-issuers/- “All accredited issuers are listed in an on chain registry.”
Vine, Redbelly Network developer portal: Business verification
https://vine.redbelly.network/business-verification/- “To be verified, businesses need to prove they are an incorporated entity to a network accredited issuer.”
Vine, Redbelly Network developer portal: Becoming a node operator
https://vine.redbelly.network/nodes/become-operator/- “Node operators MUST have network access for 2 accounts and provide their public address when applying to run a node.”
Redbelly Network technical documentation: Receptor overview
https://docs.redbelly.network/pages/receptor/- “Receptor is Redbelly's native digital identity and verifiable credential protocol.”
- “Receptor is built on the W3C verifiable credential data model, providing a standardised and interoperable foundation for identity verification and eligibility criteria assurance.”
Vine, Redbelly Network developer portal: Eligibility
https://vine.redbelly.network/identity/eligibility/- “Redbelly supports two distinct credential types, or methods, that can be used to perform eligibility criteria checks:”
Redbelly Network technical documentation: Selective Disclosure
https://docs.redbelly.network/pages/methods/selective-disclosure/- “As selective disclosure involves disclosing information to the Verifier, it can only be used off-chain.”
Redbelly Network technical documentation: Eligibility SDK for Redbelly Network
https://docs.redbelly.network/pages/eligibility-sdk/eligibility-sdk/- “Redbelly Mainnet did:receptor:redbelly:mainnet:31AAH8sSaGd6fpnG1TcB6yQ4UZnNeyHzTk5aM2P7rjv”
Vine, Redbelly Network developer portal: Eligibility checks (smart contracts)
https://vine.redbelly.network/smart-contracts/eligibility-checks/- “Eligibility checks can be used to control access to your dApp or smart contract's functions or when specific smart contract functions are called to help meet your compliance requirements.”
Tokeniser: Automated compliance
https://tokeniser.com/product/superpowers/automated-compliance- “Before any trade proceeds, the investor's identity, eligibility (including wholesale or sophisticated status where required) and your limits are verified automatically.”
Tokeniser: Secondary transfer
https://tokeniser.com/product/superpowers/secondary-transfer- “every transfer is recorded on your register in real time”
Tokeniser: Collateral mobility
https://tokeniser.com/product/superpowers/collateral-mobility- “Investors pledge units as security, and the units remain locked until the loan is repaid.”
Vine, Redbelly Network developer portal: Bridged tokens: Celer cBridge
https://vine.redbelly.network/bridged-tokens/celer/- “RBNT bridges out from Redbelly to Ethereum and BNB Chain, not back.”
- “Ethereum 0x063a1D5BFEAb213c9c12f47b704fccf81D60983e wRBNT Wrapped RBNT 18”
Vine, Redbelly Network developer portal: Bridged tokens: LayerZero
https://vine.redbelly.network/bridged-tokens/layerzero/- “Tokens on Redbelly Network that can be bridged to other chains via LayerZero, using Stargate, and vice versa.”
Vine, Redbelly Network developer portal: Bridged tokens: Lucid Labs
https://vine.redbelly.network/bridged-tokens/lucidlabs/- “Tokens on Redbelly Network that can be bridged to other chains via Lucid Labs, and vice versa. Powered by Polymer and LayerZero.”
- “Ethereum 0xb45fFB51984d626Ee758b336C61Cf20990c6bF13 WRBNT Wrapped RBNT 18”
Celer Network blog: Celer Announces cBridge Support for Redbelly (1 August 2025)
https://blog.celer.network/2025/08/01/celer-announces-cbridge-support-for-redbelly/- “Celer is supporting asset and token bridging initially via a pegged bridge method”
Redbelly Network on X: Wrapped RBNT Token is now live on Ethereum Mainnet (14 February 2025)
https://x.com/RedbellyNetwork/status/1890340030197166112- “Wrapped RBNT Token is now live on Ethereum Mainnet.”
- “0xb45ffb51984d626ee758b336c61cf20990c6bf13”
Redbelly DAO Community Task Board: TASK-08 bridge integration guide (selected entry)
https://github.com/Redbelly-DAO-Community-Taskboard/TASK-08-bridge-integration-guide- “Redbridge is a lock-and-mint bridge”
- “Yes, on Mainnet dedicated "Redbelly Mainnet" deployment”
TASK-08 entry, public repository: Bridging Ethereum Sepolia to Redbelly Testnet: technical guide
https://github.com/tycayomide/redbelly-testnet-bridge/blob/main/TECHNICAL_GUIDE.md- “no major interoperability protocol has deployed core messaging infrastructure (endpoints, gateways, or guardian sets) to”
Redbelly DAO Community Task Board: TASK-16 Cross-Chain Recovery Playbook (selected entry, PDF)
https://github.com/Redbelly-DAO-Community-Taskboard/TASK-16-cross-chain-recovery-playbook/blob/main/deliverable/Redbelly-task-16-revised.pdf- “Because the official Redbelly bridges (Reddex and Lucid) currently only support bridging USDC and USDT from BNB Chain”
Quant, Overledger API reference: Overledger Server API reference
https://docs.overledger.dev/reference- “List Fusion Rollup connected networks”
Test run for this report: Calls to the public Overledger server API without an account, 15 October 2026
evidence/tests/overledger-api-check.txt in the project repository- “GET https://fusion-rollup.quant.dev/networks/fusion -> HTTP 401 {"status":401,"error":"Missing authorization header."”
Quant, Overledger documentation: Chapter 9: Overledger Firewall
https://docs.overledger.dev/docs/overledger-firewall- “Overledger maintains the binding between each user and their authorised on-chain address(es) off-chain, so policies expressed against a user translate into on-chain address allowlists at the contracts that enforce them.”
- “If permissioned, the user must appear in the network's allowlist.”
- “Token allowlist entries are governance-controlled (Quant Safe signers), not per-deployer, they apply to all users of the bridge.”