✳THE FOUNDATION FOR WHAT COMES NEXT
Explore native markets, evaluate an exchange integration, or build payment and asset workflows. Graphene brings these paths together with on-chain records, visible fees, and an Ethereum-compatible API.
A WINDOW INTO THE NETWORK
Network figures come from the same indexer API as the Graphene explorer.
Counts reflect indexed blocks and synced state; they may lag the chain.
YOUR ROLE. YOUR STARTING POINT.
Find the information and tools that fit your role, from a first market check to a platform integration or partnership.
Explore funded buy and sell offers and liquidity pools. Check token identities, trust status, and the fees for the action you want to take.
Liquidity and trading activity vary by market.
Start a technical review of GRPH and native tokens, then test the account, transaction, and RPC flows your platform needs.
The brief is a starting point for your own listing and integration review.
Explore a payment, asset, attestation, market, or infrastructure use case with the Graphene team. Start with the problem you want to solve.
Share your organization, use case, and proposed next step.
BUILT INTO THE FOUNDATION
Graphene includes native modules for assets, exchange, payments, staking, attestations, and governance.
NATIVE ASSETS
Create and transfer tokens, with issuance rules enforced by the protocol.
TRADING & LIQUIDITY
Use funded buy and sell orders, or exchange assets through liquidity pools.
PAYMENT INVOICES
Create an invoice and track partial contributions until it is fully paid.
VALIDATORS & DELEGATION
Delegate stake to validators through the network’s staking module.
ATTESTATIONS
Register data schemas and issue attestations: structured statements recorded on chain.
PROPOSALS & VOTING
Propose and vote on supported protocol changes through on-chain governance.
COMMUNITY-GOVERNED ASSETS
Trusted tokens carry Graphene’s community-governed trust flag. The protocol checks that flag when tokens enter native trading and borrowing flows.
THE NATIVE TOKEN
GRPH pays network fees, supports validators, and gives holders a way to take part in protocol decisions.
Native supply is shown only when the API’s supply snapshot matches its synced state. Trusted-token supplies come from their own token records.
Explore GRPH holdersPay the base transaction fee and native operation charges in GRPH.
Stake or delegate GRPH through the native staking module.
Use GRPH for proposal deposits and temporarily locked votes.
Use GRPH as collateral in supported trusted-token borrowing markets; oracle and risk rules apply.
Token trading, liquidity, and swaps require the trust flag. Native GRPH is accepted separately.
Governance can change the flag. Existing orders and pools are checked again when used; cancellations and liquidity withdrawals remain available.
A trust flag does not prove backing, redemption rights, a price peg, or liquidity. Borrowing also needs valid oracle coverage: an available on-chain price source.
Graphene EUR
0x32401c759f38042c58aada91cd079132188b9899View token in explorerGraphene GOLD
0xb4a0a62047532651229a2da440fcf3661ba58bf3View token in explorerGraphene Silver
0x0c4314c9a819779e3b5ac6bf7baf6bf5b840441cView token in explorerGraphene USD
0xc8fbec2bb3f061de66cb98e039f605aae49f635bView token in explorerNames such as USD, EUR, GOLD, or Silver identify tokens; they do not establish backing or a redemption promise. This list describes the selected network only.
KNOW THE COST BEFORE YOU ACT
Graphene charges a governance-set base transaction fee. Some actions also have a module charge or a refundable deposit.
Plus the base transaction fee
Plus the base transaction fee
Plus the base transaction fee
0.2% of the invoice’s gross payment, taken in the requested asset. Invoice creation also locks a refundable deposit: 10 GRPH. The deposit returns to the creator when the invoice is fully paid.
100 GRPH. Locked when proposing. Returned if quorum is reached; collected as a protocol fee if quorum is missed. The base transaction fee is separate.
Saved settings snapshot · live check pending · Checked:
A transaction that passes validation but fails during execution still pays the base fee. Swap and other module charges depend on the action. The final receipt records what was charged.
HOLDERS HELP SHAPE THE RULES
Graphene uses on-chain proposals and votes to change supported settings, token trust, token issuance, and fee-account actions.
Submit a proposal and lock its GRPH deposit. A proposal freezes its rules and takes voting eligibility from the parent committed block.
Lock a positive amount within your snapshot balance. Voting power is the integer square root of that amount, subject to a per-wallet cap. Each wallet votes once per proposal.
The vote must reach quorum: the required share of eligible voting power. It must also reach the required share of yes voting power. Vote locks are released when voting ends.
A passed proposal waits for a timelock: a delay counted in blocks. The chain then rechecks and applies the change. A change that fails execution checks is rejected.
New proposals use the current settings below. Existing proposals keep the rules captured when they were created.
View governance in the explorerSaved settings snapshot · live check pending
Durations are block counts, not seconds or calendar dates. Same-block transfers cannot increase a proposal’s snapshot power. Quadratic voting and a wallet cap do not by themselves prevent one person from controlling multiple wallets.
FROM CURIOUS TO CONNECTED
Start by reading network activity, then connect your tools and explore the code.
Open the explorer to inspect blocks, transactions, and addresses.
Point an Ethereum-compatible client at your Graphene RPC endpoint.
Read the native module APIs and try an asset, invoice, or attestation on your own development network.
IDEAS, WITH BUILDING BLOCKS
Native modules provide starting points for applications that move value and record activity.
01 / COMMERCE
Build a payment flow that tracks contributions and shows a clear invoice status.
Explore the module02 / DIGITAL ASSETS
Explore token creation, transfers, and governance-controlled issuance rules.
Explore the module03 / VERIFIABLE RECORDS
Use schemas and attestations to publish structured statements on chain.
Explore the moduleWHY BUILD ON GRAPHENE?
Graphene combines native financial modules, a community trust policy, and governance-set transaction prices behind an Ethereum-compatible RPC API.
Start from native assets, orders, pools, invoices, attestations, and borrowing workflows. The application can focus on how people use them.
The protocol rechecks token trust in supported markets. Governance controls supported fee settings and changes through proposals.
Use supported Ethereum JSON-RPC methods and the explorer while working with the network’s native modules.
| Design choice | Graphene | Ethereum L1 | Cosmos SDK applications |
|---|---|---|---|
| Asset building blocks | Native token issuance and financial modules | ERC-20 token APIs implemented in smart contracts | Native modules such as bank; application-specific modules can be added |
| Transaction pricing | Governance-set fixed base fee, plus applicable module charges | Gas used × (base fee + priority fee) | Fee and gas rules depend on the application |
| Protocol governance | Balance-snapshot voting with a square-root weight, wallet cap, thresholds, and delay | EIP process, community discussion, and coordinated network upgrades | On-chain governance is available through the gov module; the application selects its rules |
Graphene’s value proposition is this integrated combination. Native modules and on-chain governance are also available in other stacks. This comparison does not establish a speed, security, adoption, or cost ranking.
FAMILIAR TOOLS. A NEW FOUNDATION.
Graphene exposes an Ethereum-compatible JSON-RPC endpoint alongside native state APIs. Start with a read-only request, then explore the modules behind it.
curl "$GRAPHENE_RPC_URL" \
-H "Content-Type: application/json" \
--data '{
"jsonrpc": "2.0",
"method": "eth_blockNumber",
"params": [],
"id": 1
}'Set GRAPHENE_RPC_URL to your node’s endpoint. This request reads the latest block number; it does not send a transaction.
FOR EXCHANGE TEAMS AND PARTNERS
Use this overview to begin a technical or commercial conversation. It describes the available building blocks and the questions to resolve for your chosen deployment.
Confirm the chain ID and node endpoints. GRPH is the native asset; other tokens are identified by their chain and address, with explicit decimals.
Check the supported Ethereum JSON-RPC methods, blocks, receipts, nonces, and fee settings. Test deposit crediting and withdrawal handling against the selected network.
Evaluate funded orders, liquidity pools, payment invoices, or attestations against your use case. A token trust flag controls eligibility in supported native markets.
Agree on the integration scope, required documentation, operational responsibilities, and acceptance tests with the team.
Graphene integration overview Audiences: exchanges, wallet teams, traders, partners, and network operators. Available building blocks: native GRPH and token issuance; funded buy/sell orders and liquidity pools; payment invoices; attestations; staking and supported on-chain governance actions. Integration surface: supported Ethereum-compatible JSON-RPC methods, native state APIs, and the block explorer. Confirm target network, chain ID, method coverage, and endpoint access with the team. Review: asset addresses and decimals; deposit monitoring; transaction and receipt handling; withdrawals; fees; custody and reconciliation; and deployment-specific acceptance tests. Trust flags, fee settings, and governance rules can change. Contact: anastal2001@yahoo.com Include your organization, use case, target network, questions, and proposed next step.
EXPLORE THE CODEBASE
The workspace brings together the chain service, a node runtime, an explorer, and a peer-to-peer network library.
Java + Quarkus · ABCI + RPC
Node.js · agents + orchestration
React · inspect network activity
Peer-to-peer transport libraries
These facts describe the local codebase, rather than a claim about any public deployment.
A FEW THINGS WORTH KNOWING
Understand the network, its tools, and the scope of these facts.
Trusted tokens carry a governance-controlled flag that makes them eligible for native trading and trusted-token lending markets. Check the token’s chain and address, not just its symbol. Governance can revoke trust, and borrowing also depends on valid oracle coverage. The flag does not guarantee backing, a price peg, redemption, or liquidity.
Graphene is a blockchain project that combines Tendermint consensus with a Java and Quarkus chain service. Its codebase includes native modules for assets, trading, payments, staking, attestations, and governance. An Ethereum-compatible RPC API and a React explorer provide ways to read and interact with the network.
The inspected workspace uses Tendermint consensus and includes validators and stake delegation. That does not establish the witness-based DPoS design associated with other projects named Graphene. This page describes this workspace only. Confirm the consensus configuration of the network you intend to use before relying on it.
Graphene exposes an Ethereum-compatible JSON-RPC endpoint, and its explorer uses Viem to interact with the network. Begin with read-only calls such as eth_blockNumber. Compatibility depends on the method and feature you need, so check the implementation and test your integration against your selected node before sending transactions.
The codebase provides modules for tokens, funded orders, liquidity pools, payment invoices, staking, attestations, and governance. These can support asset and payment workflows without assembling every part yourself. Treat them as development building blocks: review the module rules, fees, and deployment configuration before designing an application around them.
This page does not publish a throughput benchmark or a fixed block time. Actual timing depends on the network and its configuration. Protocol fee logic exists in the codebase, with prices controlled through governance. Read current network settings and inspect representative transactions to assess timing and costs for your application.
The figures use the same state statistics endpoint as the explorer. Blocks and transactions reflect the indexer, while addresses reflect synced state. They may lag the chain and do not represent individual people. If the endpoint cannot be reached, the page shows an unavailable state instead of made-up numbers.
FIND YOUR PLACE ON THE NETWORK
Explore the markets, evaluate an integration, or start a partnership conversation.
Find your path on Graphene