NAMG Community Network

KENN

The Community Token of Not Another Media Group

KENN is designed to coordinate memberships, creators, contributors, events, sponsors, community rewards, and collaboration across the NAMG network.

Maximum Supply
4,200,000,000 $KENN
Circulating Supply
99,214,660.9999 $KENN
Genesis Chain
WAX
Issuer
kenbrobro42o
Current Stage
Charter & Genesis Audit
Network Status
Pre-Implementation

Key token facts

The confirmed facts, in one place.

Everything below is explained in full further down this page. This is the quick reference.

Maximum Supply
4,200,000,000 $KENN
Circulating Supply
99,214,660.9999 $KENN
Genesis Chain
WAX
Issuer
kenbrobro42o
Current Stage
Charter & Genesis Audit
Network Status
Pre-Implementation

More than a creator token

A network token, not a personal one.

  • $KENN is the community token of Not Another Media Group (NAMG) as well as the Membership Token for the BRO Federation.
  • It is not a personal token of Kenn Bosak, and it does not entitle holders to any individual's earnings, intellectual property, likeness, or decisions.
  • The name traces back to the network's inspirational founder, but ownership, treasury control, and issuance are being formalized as network-level structures, not personal property.

What KENN is for

Coordination across the network, not a single product.

Every use below is proposed — none of it is live functionality yet. See the status matrix for exact stage.

Proposed

Membership coordination

Recognizing and rewarding active NAMG memberships across the network.

Proposed

Creator & contributor recognition

Directing a share of network supply toward the people producing media, tools, and events.

Proposed

Event & sponsor coordination

Connecting conferences, sponsors, and campaigns to a shared unit of account across communities.

Proposed

Cross-community collaboration

Giving independent communities inside the NAMG network a common token to coordinate joint activity through, alongside their own tokens.

Brofile community network

KENN reads from Brofile identity — it isn't Brofile.

  • Brofile is the identity and permissions layer that $KENN membership and rewards are designed to read from and interact with, it is not a $KENN-specific product.
  • Brofile already supports many independent communities, each with their own members, events, and reputation history, not only NAMG's.
  • BROAPs (Blockchain Resources Observatory Achievement Protocol) record participation, achievements, attendance, and reputation on Brofile and accross blockchains, this is the layer any future $KENN reward logic would reference, not $KENN itself.
  • A Brofile identity is the way a member's KENN membership status and community affiliations are recognized network-wide.

Network architecture

Four layers, and where KENN sits in them.

Identity and reputation sit beneath every community economy on the network, including KENN's.

  1. L1

    Brofile

    Identity
    • Identity
    • Wallets
    • Memberships
    • Permissions
  2. L2

    BROAP

    Reputation
    • Participation
    • Achievements
    • Attendance
    • Reputation
  3. L3

    Community tokens

    Independent economies
    • Independent community economies

    KENN — NAMG's community token

    $KENN sits beneath the community-token layer as NAMG's own community token for one economy among the network's communities, not a replacement for the others.

    Other communities' existing tokens can connect into network services above without being replaced or absorbed by KENN.

  4. L4

    Network services

    Coordination
    • Rewards
    • Vesting
    • Campaigns
    • Discovery
    • Sponsorships
    • Reporting

Existing community tokens are welcome

KENN doesn't ask a community to give up its own token.

  • Independent communities inside the NAMG network are not required to give up their own tokens to participate.
  • A community's existing token can keep its own supply, treasury, and governance $KENN is designed to sit alongside it, not replace it.
  • Where useful, a community token may connect to shared network services (discovery, sponsorship tooling, reporting) without merging economies.

KENN community bond

A proposed way for a community to link in without merging in.

  • A community bond is a proposed mechanism for a community to formally link its own token or treasury to the NAMG network without surrendering control of either.
  • The bond is intended to define what a community shares with the network (for example: cross-promotion, joint events, or reporting) and what stays independent.

Membership reward model

Proposed: half immediately, half vested over a year.

No membership reward program exists on-chain today. This section describes the proposed mechanics and example amounts only.

Membership purchased
50% immediately available
50% vested over 12 months

50% unlocked

Month 0Month 12

Illustration of the proposed schedule, not a live vesting position — no on-chain vesting exists yet.

A renewal creates a new grant. Previously earned rewards are not automatically forfeited because a membership expires.
Proposed example membership grants, showing immediate and vested KENN amounts by tier
MembershipImmediate (proposed)Vested (proposed)Total (proposed)
Community420 KENN420 KENN840 KENN
Supporter690 KENN690 KENN1,380 KENN
Network4,200 KENN4,200 KENN8,400 KENN

All amounts above are proposed examples for illustration only, not commitments.

Maximum supply

4,200,000,000 KENN

The 4.2-billion maximum applies to the aggregate $KENN supply across all supported Genesis chains ($WAX, $SOL & $BCH). A separate blockchain deployment does not create a second independent 4.2-billion allocation.

aggregate official issuance
  = $WAX issuance
  + $SOL issuance
  + $BCH issuance
  − provably burned $KENN

aggregate official issuance ≤ 4,200,000,000 $KENN
Maximum supply
The hard ceiling the network is designed never to exceed: 4,200,000,000 KENN, aggregated across every official chain.
Issued supply
$KENN actually created on-chain to date, on any official chain. Existing WAX issuance falls into this category and must be audited and classified before it is reported here.
Treasury-controlled supply
Issued $KENN held under NAMG network treasury control, not yet distributed to members, creators, or partners.
Locked supply
Issued $KENN that is contractually restricted from moving or being spent, including unvested membership and contributor grants.
Cross-chain custody supply
$KENN held in bridge or custody contracts while moving between official chains, counted once toward the aggregate cap regardless of which chain currently holds it.
Circulating supply
Issued $KENN that is not treasury-controlled, locked, or in cross-chain custody — the portion freely held and transferable by the network and its members.

WAX genesis

Issuance began on WAX.

  • $WAX is the $KENN OG Genesis chain, the chain where $KENN issuance began.
  • $KENN on $WAX was launched in 2021.
  • The $WAX issuer account is kenbrobro42o.
  • Existing $WAX issuance must be audited and classified within the complete supply allocation before it is reported as verified.
  • Nothing about OG Genesis on $WAX guarantees a particular outcome for supply audit findings.

Proposed supply allocation

How the 4.2 billion is proposed to divide up.

Proposed — subject to genesis supply audit and formal charter

  • Member and community rewards30%
  • Creator and contributor rewards20%
  • NAMG ecosystem treasury20%
  • Liquidity and market infrastructure10%
  • Partner-community programs8%
  • Sponsorship and campaign incentives5%
  • Team and long-term contributors5%
  • Security, grants, and contingency2%
Proposed KENN supply allocation by category, in percent and token count
CategoryShareKENN (proposed)
Member and community rewards30%1,260,000,000
Creator and contributor rewards20%840,000,000
NAMG ecosystem treasury20%840,000,000
Liquidity and market infrastructure10%420,000,000
Partner-community programs8%336,000,000
Sponsorship and campaign incentives5%210,000,000
Team and long-term contributors5%210,000,000
Security, grants, and contingency2%84,000,000
Total100%4,200,000,000

Emission and treasury principles

The rules the emission model is designed to follow.

Vesting before liquidity

Membership and contributor rewards are proposed to vest over time rather than distribute in full immediately.

Treasury transparency

Treasury-controlled KENN is intended to be reported separately from circulating supply, not blended into it.

Audit before expansion

New chain deployments and reward programs are intended to follow the genesis audit and charter, not precede them.

One cap, every chain

Emissions on any official chain are proposed to draw down the same 4.2-billion aggregate cap, never a separate one.

Multi-chain KENN

One genesis chain today. Expansion is proposed, not built.

Chain-by-chain status of KENN issuance and movement
ChainRoleStatus
WAXGenesis chain — existing issuanceLive
SolanaProposed expansion chainProposed
WAX ↔ Solana bridgeProposed cross-chain movementProposed
  • WAX is confirmed as the KENN genesis chain today.
  • Solana support is proposed and does not exist on-chain yet.
  • Any WAX-to-Solana movement would rely on a bridge or migration mechanism that is also proposed, not built.
  • No migration date, bridge provider, or Solana launch date is guaranteed by this page.

Transparency dashboard preview

What the public supply dashboard will show.

Every field but maximum supply is a placeholder until the genesis audit publishes verified numbers.

Reconciliation status: Pending genesis audit

Maximum network supply

4,200,000,000 KENN

Verified issued supply

Pending genesis audit

Estimated circulating supply

Pending genesis audit

Treasury-controlled supply

Pending genesis audit

Locked and vesting supply

Pending genesis audit

Cross-chain custody

Pending genesis audit

Burned supply

Pending genesis audit

Rolling 12-month emissions

Pending genesis audit

Last reconciliation

Pending genesis audit

Preview only — populated from a local placeholder, not a live endpoint. This layout is structured to consume a real KennSupplySnapshot JSON response once the genesis audit publishes verified figures.

Governance

Direction of travel, not a ratified structure yet.

Treasury and emission decisions are intended to sit with NAMG network governance, not a single individual — the specific governance structure is still being formalized as part of the charter.

Community bond and partner-program terms are expected to be reviewable by the communities entering them, not imposed unilaterally.

Until the formal charter is published, governance described here is a direction of travel, not a ratified structure.

Live vs proposed status matrix

What's actually shipped, right now.

Live, in development, and proposed status of KENN network features
ItemStatusDetail
WAX KENNLiveIssued on WAX under kenbrobro42o.
4.2-billion aggregate maximumLiveCeiling applies across all official chains combined.
Public KENN webpageLiveThis page, live once deployed to notanother.media.
Genesis supply auditIn Development
Formal KENN CharterIn Development
Brofile community registryIn Development
Membership KENN rewardsProposed
On-chain vestingProposed
Solana KENNProposed
WAX/Solana migrationProposed
Community bondsProposed
Public supply dashboardProposed

Development roadmap

Seven phases from audit to partner communities.

  1. Phase 01

    KENN Genesis Audit

    In Development

    Independently verify everything already issued on WAX before anything new is proposed on top of it.

    Deliverables

    • Full accounting of existing WAX issuance under kenbrobro42o
    • Classification of issued supply into treasury, locked, and circulating
    • Published audit findings

    Exit condition

    Audit findings are published and existing WAX issuance is fully classified within the supply allocation.

  2. Phase 02

    Community Registry

    In Development

    Give Brofile a registry of NAMG-affiliated communities and their membership status.

    Deliverables

    • Brofile community registry schema
    • Membership status readable from Brofile identity
    • Formal KENN Charter draft

    Exit condition

    A community and its members can be identified through Brofile without manual lookup.

  3. Phase 03

    Supply Transparency

    Proposed

    Replace this page's pending fields with a live, verified public supply dashboard.

    Deliverables

    • Public JSON API matching the KennSupplySnapshot shape
    • Dashboard reading from verified on-chain data
    • Reconciliation cadence published

    Exit condition

    The transparency dashboard displays verified, non-mock figures reconciled on a published schedule.

  4. Phase 04

    Membership Rewards

    Proposed

    Turn the proposed membership reward model into an operating, on-chain vesting system.

    Deliverables

    • On-chain vesting contract(s)
    • Membership tier reward parameters ratified under the charter
    • Renewal-grant logic implemented

    Exit condition

    A membership purchase produces a real, on-chain immediate-plus-vested KENN grant.

  5. Phase 05

    Solana Integration

    Proposed

    Stand up KENN on Solana as a second official chain under the same aggregate cap.

    Deliverables

    • Solana KENN token deployment
    • Aggregate supply accounting extended across WAX and Solana
    • Security review of the new deployment

    Exit condition

    Solana KENN exists on-chain and is reflected in the aggregate supply dashboard, not a separate cap.

  6. Phase 06

    WAX/Solana Migration

    Proposed

    Allow KENN to move between WAX and Solana without creating duplicate supply.

    Deliverables

    • Bridge or migration mechanism
    • Burn-and-mint or lock-and-mint accounting, publicly verifiable
    • Cross-chain custody reporting in the dashboard

    Exit condition

    KENN can move between official chains with cross-chain custody publicly tracked and no increase to aggregate issuance.

  7. Phase 07

    Partner Communities

    Proposed

    Open community bonds to communities beyond NAMG's own, without absorbing their tokens.

    Deliverables

    • Community bond terms template
    • First partner community bond executed
    • Partner-community program allocation actively distributed

    Exit condition

    At least one independent community operates a signed community bond with the network while retaining its own token.

Beyond KENN

KENN is one community asset in a larger proposed structure.

The BRO Federation is a proposed treasury and governance layer that could let KENN, and other community tokens like it, hold a formally recognized position across the network — without giving up KENN's own supply, treasury, or governance. Nothing about this changes what's described above; it's a separate, still-proposed layer above it.

Read the BRO Federation design →

Core principle

KENN coordinates the network. It does not own it, and it does not promise a return on it.

Important notice

  • KENN is not equity, debt, profit sharing, or a guaranteed investment return.
  • Holding or earning KENN does not confer ownership of NAMG, Brofile, or any affiliated community.
  • No price floor, guaranteed appreciation, or risk-free reward is offered or implied anywhere on this page.
  • Proposed features (marked Proposed above) are not audited, not guaranteed to ship on any timeline, and not decentralized unless and until a control structure supporting that claim is published.
  • Membership reward figures shown are proposed examples for illustration, not commitments.

Join the community

This charter is being built in the open.

The genesis audit, formal charter, and community registry are in progress. Community input during this stage shapes what gets ratified.