REN
E41479
REN is a blockchain-based project and protocol focused on enabling cross-chain liquidity and interoperability between different cryptocurrency networks.
All labels observed (4)
| Label | Occurrences |
|---|---|
| REN canonical | 5 |
| Ren | 1 |
| Ren network | 1 |
| renFIL | 1 |
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
blockchain project
ⓘ
cryptocurrency ⓘ interoperability protocol ⓘ network nodes ⓘ virtual machine ⓘ |
| aimsTo |
eliminate centralized custodians for cross-chain transfers
ⓘ
improve liquidity across blockchains ⓘ |
| builtOn |
Ethereum blockchain
ⓘ
surface form:
Ethereum
|
| category |
cross-chain bridge infrastructure
ⓘ
infrastructure protocol ⓘ |
| consensusMechanism | Byzantine fault tolerant protocol ⓘ |
| enables |
cross-chain asset transfers
ⓘ
interoperable DeFi applications ⓘ |
| focusesOn |
blockchain interoperability
ⓘ
cross-chain liquidity ⓘ |
| formerlyKnownAs | Republic Protocol ⓘ |
| governedBy | REN token holders ⓘ |
| hasComponent |
Darknodes
ⓘ
RenVM ⓘ |
| hasFullName | Ren ⓘ |
| hasTickerSymbol | REN self-link ⓘ |
| hasWebsite | https://renproject.io/ ⓘ |
| integratesWith | Ethereum DeFi protocols ⓘ |
| laterPivotedTo | cross-chain interoperability and liquidity ⓘ |
| launchedAs | Republic Protocol privacy-preserving dark pool ⓘ |
| networkType | permissionless ⓘ |
| primaryUseCase | bringing non-Ethereum assets to Ethereum DeFi ⓘ |
| requireStake | REN token ⓘ |
| role |
decentralized custodian for cross-chain assets
ⓘ
power RenVM ⓘ |
| sector |
cross-chain bridges
ⓘ
decentralized finance ⓘ |
| securityModel | decentralized custody via MPC ⓘ |
| supportsAsset |
Bitcoin
ⓘ
Bitcoin Cash ⓘ Ethereum blockchain ⓘ
surface form:
Ethereum
Zcash ⓘ various ERC-20 tokens ⓘ |
| supportsUseCase |
wrapping Bitcoin as renBTC
ⓘ
wrapping other chains’ assets as ERC-20 tokens ⓘ |
| tokenStandard | ERC-20 ⓘ |
| tokenType |
governance token
ⓘ
utility token ⓘ |
| usedFor |
bonding by Darknodes
ⓘ
paying fees in the Ren ecosystem ⓘ |
| usesTechnology |
secure multi-party computation
ⓘ
threshold cryptography ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: REN Description of subject: REN is a blockchain-based project and protocol focused on enabling cross-chain liquidity and interoperability between different cryptocurrency networks.
Referenced by (8)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
Ren