cryptosnif
Radiant Capital (RDNT)
Documentary contract0x3082cc23568ea640225c2467653db90e9250aaa0
Unrated · 0% Evidence coverage
Operational strength remains unproven; unrated with 0% scoring coverage.
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.
Inspect the evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
Promise
This dossier examines the documented purpose and mechanisms of Radiant Capital (RDNT) on the eip155:42161 network. The goal is to establish what the available records state about this asset, while clearly separating those documentary claims from independent operational verification.
Established facts
The pinned Trust Wallet Arbitrum integration record identifies Radiant with the symbol RDNT and a documentary address of 0x3082cc23568ea640225c2467653db90e9250aaa0. This record specifies 18 decimal places, which concern amount representation and do not measure supply or value. The entry is labeled ARBITRUM and active within the community-maintained registry. The registry description states that RDNT is an OFT-20 token, where OFT-20 refers to an Omnichain Fungible Token standard enabling cross-chain transfers. It describes Radiant Capital as an omnichain money market built atop Layer Zero, allowing users to deposit and borrow assets across chains. The text further attributes governance decisions to the Radiant DAO through decentralized discussions and voting. These statements are attributed registry claims, not independently established issuer statements or operational observations. The general ERC-20 specification defines a standard interface for fungible tokens, including functions for totalSupply, balanceOf, transfers, and allowances. An allowance permits a named spender to use a specified amount, with repeated approvals overwriting previous amounts. A wallet ERC20 label establishes no independently checked compliance or actual deployed implementation. The Trust Wallet Assets README confirms this is a community-maintained registry where anyone can submit assets, and inclusion does not imply a direct partnership with listed projects. It explicitly excludes brand-new tokens, meaning this source cannot provide an exhaustive inventory of recent launches.
Unknowns
Present independent control, beneficial ownership, usage patterns, client adoption, supply distribution, concentration, liquidity, and complete incident history remain unverified. No live network observation was performed to validate the described mechanisms. The dossier may explain stated aims with attribution, but no deployed implementation, rights, safety, or investment outcome was checked.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The active status is a metadata label with no live-network validation. Without independent verification, promotional statements, network performance, consensus behavior, current deployment, and control remain unverified. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. Missing essential data on identity, supply, and control prevents any assessment of risk or utility beyond the provided registry descriptions.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move from an unrated status. Calibration and editorial review following such verification would establish whether the documentary claims align with actual operational reality.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Observable usage, token necessity and dependencies.
Inspect the evidence
Sources behind this analysis
Trust Wallet: captured Arbitrum record for Radiant
The pinned Trust Wallet Arbitrum integration record names Radiant with symbol RDNT, documentary address 0x3082cc23568ea640225c2467653db90e9250aaa0 and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry ARBITRUM and active. Its community-maintained description states: "$RDNT, an OFT-20, is Radiant's native utility token. Radiant Capital is an omnichain money market built atop Layer Zero. Deposit and borrow assets cross-chain, seamlessly. Through decentralized discussions, voting, and governance, the Radiant DAO determines the decisions, and, ultimately, the vision of the Radiant ecosystem." Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. The dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown. The general ERC-20 specification is separate from this token implementation.
Inspect the primary source ↗Trust Wallet: pinned Arbitrum directory context
The pinned Trust Wallet arbitrum network-context record identifies the community registry directory for Arbitrum. This supplies documentary network context for entries in the same pinned directory. Promotional statements, network performance, consensus behavior, current deployment and control are not verified or admitted from this context.
Inspect the primary source ↗Trust Wallet Assets: README.md (bbe582d25a22)
The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The README states that its scripts and documentation use the MIT license. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.
Inspect the primary source ↗Ethereum ERC-20: pinned token interface specification
The pinned ERC-20 specification describes a standard interface for fungible tokens in smart contracts. It defines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval and remaining allowance. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification says callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. These interface requirements describe what a conforming implementation should do. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. No token transaction was performed in this review. Copyright and related rights are waived under CC0.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.