GRIOT — what this is, and what it is not.

Overview

GRIOT is building an archive of human knowledge: a place where what one person knows is written down, attributed to the person it came from, and made available to whoever needs it next. The scope is deliberately broad — a recipe, a repair method, a farming technique, an oral history and a smart contract are all knowledge that can be lost when the person holding it stops passing it on.

The project takes its name from the West African griot, the hereditary keepers of oral history, genealogy and counsel. GRIOT does not claim to represent or inherit that institution. It carries one principle forward: knowledge survives when someone is responsible for carrying it, when they are named, and when it is handed on before it is lost.

$GRIOT is the economic layer beneath that work, not the product itself. Reading the archive will never require holding the token.

Token

Every value below is verifiable on-chain. Check the contract address against this page before interacting with anything claiming to be $GRIOT.

Name

GRIOT

Symbol

$GRIOT

Chain

BNB Chain (BSC)

Total supply

1,000,000,000

Launch venue

four.meme

Launch type

Fair launch, public bonding curve

Bonding curve

Completed — now trades on BNB Chain DEXes

Distribution

Of the 1,000,000,000 supply, 80% was sold on a public bonding curve on four.meme. The remaining 20% was paired with the BNB the curve raised to create PancakeSwap liquidity when the curve completed, and those LP tokens were burned. Everyone bought on the same curve, at the same prices — including the people who started the project.

• —No presale
• —No private round
• —No team allocation
• —No insider allocation
• —No vesting schedule for anyone
• —No allowlist or early access of any kind

Because there was no presale, there is nothing anyone could have sold you before launch. Any offer of $GRIOT made privately, before or since, did not come from this project.

Supply and liquidity

There is no locked or unlocking allocation held by the team or by anyone else, because none was ever created. 80% of the supply was sold on the public bonding curve and the other 20% became PancakeSwap liquidity, so there is no tranche that can be released into the market at a later date.

Liquidity is burned rather than time-locked. When the bonding curve completed, four.meme migrated the accumulated liquidity to PancakeSwap and the resulting LP tokens were burned. No party — including this project — can withdraw that liquidity. A burn does not expire the way a timed lock does.

Both facts are verifiable on-chain from the contract address. Nothing here needs to be taken on trust.

Team allocation

None — nothing to lock or unlock

Vesting

None for any party

Liquidity

Migrated to PancakeSwap on curve completion

LP tokens

Burned — permanently unrecoverable

Migration handled by

four.meme contracts, not by this project

Transaction tax

Buying carries a 1% tax and selling carries a 2% tax. These are separate rates, not a combined 3%. Of every tax collected — whether from a buy or a sell — 10% is burned and 10% goes to eligible holders.

Buy tax

1%

Sell tax

2%

Burn

10% of tax collected

Holders

10% of tax collected

The knowledge network

In development — not yet live

The archive is designed around a Knowledge Record: a single preserved piece of knowledge that takes whatever shape its subject needs. A recipe is not stored as a research paper; an oral history is not flattened into a blog post.

Each record separates the people involved, because inherited knowledge does not belong to whoever typed it up. A record names the knowledge holder, whoever documented it, whoever contributed it, whoever translated it and whoever reviewed it — separately.

Records carry their lineage where it is known, and say plainly when it is not. Where accounts differ — as they do for most traditional knowledge — variants are held side by side rather than one being crowned as definitive.

None of this is built. There are no records, no contributors and no archive to browse. No usage, adoption or community figures are claimed anywhere on this site.

Proof of Knowledge

Specified — no anchoring contract is deployed and nothing has been anchored

Anyone can host an archive. The hard part is proving that what it holds today is what it held a year ago, and that nobody — including the people running it — quietly changed it in between. Proof of Knowledge is how GRIOT answers that.

Once a record has been checked by people with standing in its subject, it is sealed: its content, media references, attribution, consent status and the reviewers’ decisions are combined into a single cryptographic fingerprint. That fingerprint is written to BNB Chain with a timestamp.

The record itself stays off-chain. A two-hour recording of an elder cannot live on a blockchain at any sensible cost, and claiming otherwise would be dishonest. What goes on-chain is the proof. Anyone can re-compute the fingerprint from the published record and compare it to the anchored one — if they differ by a single character, the record was altered after sealing.

Corrections never overwrite. A revision is sealed as a new version linked to the previous fingerprint, so the history of how a record changed is itself provable.

• —Proves — this exact record existed on this date
• —Proves — it has not been altered since it was sealed
• —Proves — these named people reviewed and accepted it
• —Proves — this is who the knowledge was attributed to at the time
• —Proves — the version history, in order
• —Does not prove — that the knowledge is correct
• —Does not prove — that the knowledge holder is who they say they are
• —Does not prove — that consent was genuinely given, only that it was recorded
• —Does not prove — that a community agrees with how its knowledge was described

Proof of Knowledge is a provenance and integrity scheme. It is not a consensus mechanism — GRIOT does not run a chain or validate blocks, and the name should not be read as implying either. A proof of integrity is not a proof of truth, and no part of this system claims to establish that a preserved piece of knowledge is correct.

Consent and attribution

Commitment — enforced when the archive is built

Some knowledge is not the contributor’s to give away. A family’s method, a community’s practice, a ceremony that was never meant to be public — preserving something is not the same as being entitled to it.

• —Consent is recorded as part of a record, not assumed from the act of publishing
• —Communities can be attributed, not only individuals
• —A community can dispute or request withdrawal of a record about them
• —Knowledge can be documented but restricted — preserved without being published, where that is what respect requires

Contribution and rewards

Designed, not built. Not funded. No date.

The intended model separates three things that are often confused. Reputation is a long-term record of what someone has contributed; it cannot be bought, sold or transferred. GRIOT Credit is a planned off-chain unit earned through qualifying contribution; it is not $GRIOT and cannot be transferred between people. $GRIOT is the token.

Credit would be created by contribution being accepted after review — never by votes, likes or engagement. A community signal decides what gets seen and reviewed; it earns nothing on its own. This distinction is deliberate: a design where votes create value is a design that gets farmed.

No reward pool exists. No conversion rate between Credit and $GRIOT has been set, and none is promised. Eligible Credit may qualify a contributor for rewards during a configured reward period, subject to review — it is not a balance owed to anyone. Nothing in this section is built, funded or scheduled.

Access

Core knowledge will not be token-gated. Reading the archive will never require holding $GRIOT, connecting a wallet, or having any Credit. The token is intended to reward contribution; it does not own access to human knowledge.

Roadmap

Direction, not committed dates

Each phase should earn trust before the next one claims to preserve it. The reward layers come last deliberately — an incentive shipped before the review systems that police it gets farmed immediately, and an archive that fills with low-quality material early does not recover.

• —Phase 1 — The archive: knowledge records, search, sources, contributors, and sealing accepted records on-chain
• —Phase 2 — Community knowledge: helpful signals, comments, corrections, variants, lineage, translations
• —Phase 3 — Contribution identity: contributor profiles, reputation, review roles
• —Phase 4 — GRIOT Credit: credit engine, anti-abuse controls, credit history
• —Phase 5 — Knowledge rewards: reward periods, distributions, sponsored preservation
• —Phase 6 — Intelligence: search, translation assistance, discovery
• —Phase 7 — Wider ledger work: public verification tooling, batch anchoring, external attestations

The archive is being built. No opening date is set: it opens when its first records are sealed and verifiable. Everything beyond Phase 1 is direction without a date.

Ownership and governance

GRIOT is community-owned and deliberately not tied to any one person. There is no founder allocation, no team wallet holding a reserved share, and no personal branding attached to the project.

Governance mechanisms for the network — how contributions are reviewed, who reviews them, and how disputes are settled — are part of the design and are not yet built. They will be documented here as they exist, not before.

Verification and safety

This site is the only official source for the contract address. Check it character by character against the block explorer before interacting with anything.

• —Nobody from this project will ever send you a contract address in a direct message
• —There is no presale, early allocation or private round to be offered
• —Nobody from this project will ever ask for your seed phrase or private key
• —This site connects no wallet and handles no transaction — every trading link is an outbound link to a third-party venue

Official links

These are the only official channels. Anything not listed here is not affiliated with this project, whatever it claims.