RBNT bridge controller (LockRelease)0xe356197f2728∴⟡∴da18488c610d
Discovery + lifecycle view: deployment, upgrades and ownership changes are derived locally from receipts and event logs.
Registry
Manually curated metadata from contract_registry. Reviewed by root · 13 days ago
- Name
- RBNT bridge controller (LockRelease)
- Standard (registry)
- custom
- Category
- infrastructure · bridge-controller
- Verification source
- routescan
- Notes
- LockReleaseAssetController — WRBNT liquidity + TransferCreated/Relayed path to Polymer adapter (whitelist on wrapper TransferSent).
Cross-chain bridge stack
This contract is the bridge controller (lockrelease) in the RBNT → external chains bridge. Aggregate flow stats live on the wrapper contract page.
- Role here
- Bridge controller (LockRelease)
- Cross-chain wrapper
- 0x00c1∴⟡∴566e
- Bridge controller
- 0xe356∴⟡∴610d
- Bridged token
- 0x6ed1∴⟡∴6076
- Wrapper fee treasury
- 0x5d69∴⟡∴76f1
- Adapter fee treasury
- 0xa745∴⟡∴d3a2
Recent interactions
Transactions that call this contract (to_address = this address), newest first. For outgoing calls from this contract too, open full activity on the address page.
No incoming calls in this slice
Either nothing indexed yet, or the cursor is past the oldest transaction.
Lifecycle
No lifecycle events for this address. The contract is either pre-genesis, factory-deployed (top-level CREATE not visible), or simply immutable with no proxy / ownership events.
Standard detection
Detected as Custom contract · 30% · 207 logs · 0 transfers · last detected 5 hrs ago
Matched event signatures
No standard event signatures observed.
Matched method selectors
No standard selectors observed.
Method selectors
Top selectors observed in calldata. Known signatures are matched against a deterministic local catalog (no external ABI yet).