# Graphene blockchain

> 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.

## Scope and freshness
This file describes the Graphene workspace and selected network, not other projects named Graphene. Figures below are indexer snapshots, not an investment recommendation or a guarantee of deployment readiness. Token trust, supply, fees, and governance settings can change after the stated verification time. Confirm current settings on the selected node before transacting or integrating.

## Key facts
- Consensus: Tendermint
- Core languages: Java, TypeScript & JavaScript
- Governance: On-chain proposals & voting
- Block time: Network-dependent; verify live
- License: Needs verification before launch
- Selected chain ID: 9876.
- Interface: supported Ethereum-compatible JSON-RPC methods and native state APIs. Full Ethereum method parity is not established.

## Who Graphene is for
- 01 / TRADERS: Explore funded buy and sell offers and liquidity pools. Check token identities, trust status, and the fees for the action you want to take.
- 02 / EXCHANGES & WALLETS: Start a technical review of GRPH and native tokens, then test the account, transaction, and RPC flows your platform needs.
- 03 / PARTNERS & OPERATORS: Explore a payment, asset, attestation, market, or infrastructure use case with the Graphene team. Start with the problem you want to solve.

## Native GRPH
GRPH pays network fees, supports validators, and gives holders a way to take part in protocol decisions.
- GRPH is the native network asset, separate from tokens carrying a governance-controlled trust flag.
- Native decimals: 18; one GRPH equals 10^18 native base units.
- Native total supply: no validated value has been captured for this homepage snapshot. Native supply is shown only when the API’s supply snapshot matches its synced state. Trusted-token supplies come from their own token records.
- Pay network fees: Pay the base transaction fee and native operation charges in GRPH.
- Support validators: Stake or delegate GRPH through the native staking module.
- Take part in governance: Use GRPH for proposal deposits and temporarily locked votes.
- Back a borrowing position: Use GRPH as collateral in supported trusted-token borrowing markets; oracle and risk rules apply.
- [Explore GRPH holders](https://explorer.dev.zlinkchain.io/tokens?tab=holders&token=0x0000000000000000000000000000000000000000)

## Trusted tokens and total supplies
Registry checked: 2026-11-11T18:41:34.400424Z. Chain ID: 9876. Supply figures are reported total supplies, not circulating-supply or reserve-backing estimates.

| Symbol | Name | Reported total supply | Decimals | Token address |
| --- | --- | --- | --- | --- |
| gEUR | Graphene EUR | 12,000,000 gEUR | 5 | 0x32401c759f38042c58aada91cd079132188b9899 |
| gGOLD | Graphene GOLD | 10,000 gGOLD | 2 | 0xb4a0a62047532651229a2da440fcf3661ba58bf3 |
| gSLV | Graphene Silver | 10,000 gSLV | 2 | 0x0c4314c9a819779e3b5ac6bf7baf6bf5b840441c |
| gUSD | Graphene USD | 12,000,000 gUSD | 5 | 0xc8fbec2bb3f061de66cb98e039f605aae49f635b |

Trusted tokens carry Graphene’s community-governed trust flag. The protocol checks that flag when tokens enter native trading and borrowing flows.
- Check eligibility: Token trading, liquidity, and swaps require the trust flag. Native GRPH is accepted separately.
- Watch for changes: Governance can change the flag. Existing orders and pools are checked again when used; cancellations and liquidity withdrawals remain available.
- Check the asset itself: 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.
Names 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.

## Use cases
- From invoice to paid. Build a payment flow that tracks contributions and shows a clear invoice status.
- Give your idea an asset. Explore token creation, transfers, and governance-controlled issuance rules.
- A record others can inspect. Use schemas and attestations to publish structured statements on chain.
- Native markets: funded buy/sell offers and liquidity pools; inspect market conditions and available liquidity before trading.
- Exchange and wallet integration: evaluate supported account, block, transaction, receipt, asset, and RPC flows on the intended deployment.
- Partners and operators: explore payment, asset, attestation, market, or infrastructure workflows with the team.

## Current fees (last verified settings)
Settings checked: 2026-11-11T18:41:14.909584Z. Chain ID: 9876. These are the last verified settings captured in this file; the static file does not poll for updates.

- Base transaction fee: 0.001 GRPH. The fixed protocol base fee is independent of signed wallet gas fields.

| Operation | Additional operation charge | Base plus operation charge on successful execution |
| --- | --- | --- |
| Token creation | 100 GRPH | 100.001 GRPH |
| Attestation schema registration | 10 GRPH | 10.001 GRPH |
| Attestation creation | 10 GRPH | 10.001 GRPH |

- Invoice payment fee: 0.2% of the gross invoice payment, collected in the invoice asset. Each transaction also has the applicable base transaction fee.
- Invoice creation deposit: 10 GRPH, locked separately from fees and returned to its creator when the invoice is fully paid.
- Proposal deposit: 100 GRPH, locked separately from the base transaction fee. It is returned if quorum is reached, even if a proposal is rejected; otherwise it is collected as a protocol fee.
- Swap fees and other module-specific charges depend on the action or pool. The list above is not a complete transaction quote for every module.
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.

## Governance
Graphene uses on-chain proposals and votes to change supported settings, token trust, token issuance, and fee-account actions.
01. Propose a supported change: Submit a proposal and lock its GRPH deposit. A proposal freezes its rules and takes voting eligibility from the parent committed block.
02. Vote with eligible GRPH: 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.
03. Meet both thresholds: 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.
04. Wait, then apply: 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.

Current rules for new proposals, verified 2026-11-11T18:41:14.909584Z:
- Proposal deposit: 100 GRPH.
- Voting period: 604,800 blocks.
- Execution delay: 172,800 blocks.
- Quorum: 20% of eligible voting power.
- Approval: 60% of cast voting power.
- Vote weight: integer square root of the locked native base-unit amount, capped at 100,000,000,000 voting-power units per wallet.
New proposals use the current settings below. Existing proposals keep the rules captured when they were created.
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.

## Exchange integration details
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.
- Assets and network: Confirm the chain ID and node endpoints. GRPH is the native asset; other tokens are identified by their chain and address, with explicit decimals.
- Transactions and operations: Check the supported Ethereum JSON-RPC methods, blocks, receipts, nonces, and fee settings. Test deposit crediting and withdrawal handling against the selected network.
- Markets and business flows: Evaluate funded orders, liquidity pools, payment invoices, or attestations against your use case. A token trust flag controls eligibility in supported native markets.
- A shared evaluation: Agree on the integration scope, required documentation, operational responsibilities, and acceptance tests with the team.
- Test native GRPH and token deposits, withdrawal signing/broadcasting, failed receipts, nonces, fee charges, balance reconciliation, and deployment-specific confirmation policies before enabling a production flow.
- Verify RPC method coverage, node access, historical data availability, and operational responsibilities with the team. An Ethereum-compatible API does not establish a completed custody integration, exchange listing, audit, or service-level commitment.
- [Read the integration overview](https://dev.zlinkchain.io/#integration-guide)

## Exchange and partner enquiries
- Public contact: [anastal2001@yahoo.com](mailto:anastal2001@yahoo.com).
- Include your organization, use case, target network, assets to evaluate, requirements, questions, and proposed next step.
- Website enquiry links open email drafts; they do not send a message automatically.

## Why Graphene
Graphene combines native financial modules, a community trust policy, and governance-set transaction prices behind an Ethereum-compatible RPC API.
- Useful modules already in the protocol: Start from native assets, orders, pools, invoices, attestations, and borrowing workflows. The application can focus on how people use them.
- Shared trust and pricing rules: The protocol rechecks token trust in supported markets. Governance controls supported fee settings and changes through proposals.
- Familiar tools at the edge: Use supported Ethereum JSON-RPC methods and the explorer while working with the network’s native modules.
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.

## Resources
- [Native and trusted assets](https://dev.zlinkchain.io/#trusted-tokens)
- [Current fee settings](https://dev.zlinkchain.io/#fees)
- [Governance overview](https://dev.zlinkchain.io/#governance)
- [Developer overview](https://dev.zlinkchain.io/#developers)
- [Explorer, configured endpoint](https://explorer.dev.zlinkchain.io)
- [Trading](https://explorer.dev.zlinkchain.io/trade)
- [Governance explorer](https://explorer.dev.zlinkchain.io/governance)

## Claims requiring separate verification
No throughput benchmark, fixed block time, reserve backing, price peg, redemption guarantee, partner endorsement, exchange listing, mainnet status, reward forecast, or project-wide license is established by this file. Native supply remains unpublished until a validated figure is captured. No private project repository links are included.