Whitepaper chapter notes (archive)10 / 10
Community Relations
These notes follow the whitepaper chapter by chapter; they are archived and no longer updated as the chain changes. The protocol in brief, and where the chain differs from the whitepaper, is in the HELIX quick reference; the official docs have the current rules.
In 30 seconds
- The contract only records who referred whom; level is not a rank
- Most relations were migrated from Polygon; Anubis invites aren't open yet
- No referral rates in the whitepaper; this site can't change relations
The relations contract
Referral relations live in the community relations contract on Anubis:
Community0xc9f9a8a2dBf8188AD6610e0239105CAbE67c4993
- Deployed: contract code exists from block 1,841,628 (2026-04-28).
- Contract type: as of 2026-09-24, the block explorer shows it as an EIP-1967 upgradeable proxy, and the source code of its logic contract is not verified there.
The contract stores two values per member:
| Value | Meaning |
|---|---|
| level | The member's depth in the relation tree. The root member is 1; every member is one more than their referrer |
| referrer | The referrer's address |
What the contract can answer:
members(address): the address's level and referrer. For an address that is not a member, level is 0.referrerOf(address): the referrer.referrals(address, start, count): a page of the address's direct referrals, plus how many there are in total.
The contract only records who referred whom. Deeper figures such as total team size or a team's total Genesis subscriptions require walking the whole tree, which is what this site's indexer does.
The root of the tree
The root member is the address returned by commRoot(), 0x159ec1f43d18ff1f275156a4a8b0e53503503c1b, at level 1. Its referrer is the contract's placeholder address ORIGIN(), 0x0000000000000000000000000000000000000001. Every member can be traced up through their referrers to this root.
Two events: Joined and Imported
| Event | Fields | Emitted when |
|---|---|---|
| Joined | member, referrer, level | A member joins the tree |
| Imported | member, referrer, operator | Relations are imported in bulk by an operator address |
On-chain records show that almost every member of the tree was migrated from Polygon in bulk through Imported events: the migration began at block 1,856,081 and ran in batches, with 318,155 members imported by block 1,888,000 alone (318,156 with the root). For the current total, the number imported and those who joined directly on Anubis, see "Members", "Imported" and "Joined on chain" on the community data page, which also shows daily joins.
Invitations are not open on Anubis yet
The official dApp shows that invitations are not yet enabled on the Anubis chain and asks users to invite on Polygon.Official dApp page So almost every relation on Anubis today came from the migration, and new invitation relations will only appear on Anubis once the official dApp opens them.
How deep the tree is
As of the data on 2026-09-24, Genesis Plan subscribers sit between level 6 and level 97 of the tree, with a median of level 45. Because the tree is this deep, the site pre-aggregates team data in its indexer instead of walking the chain level by level on every page view.
Community Power in the whitepaper
The whitepaper splits each day's Community Emission 50/50 between Personal Power and Community Power. The personal half is shared by weight of each person's effective Power; the community half goes into a separate community Power competition. Both halves share the same emission budget after the three gates, and the 50/50 split is only an internal allocation that creates no extra emission.Whitepaper p. 73–74
Daily Community Emission = 50% Personal Power + 50% Community Power
The whitepaper does not say how Community Power is calculated, and it does not connect it to this relations contract.
This site's team tools
From this contract and the Genesis subscription contract, the site assembles the following for any address:
- Address page (from the "Look up address" box in the header): its "Relations" view shows whether the address is a member, its level, referrer, upline chain and direct referrals; its "Genesis" view shows its own Genesis subscription records.
- Team data: the address page openly shows the total downline at any depth and the team's total Genesis subscriptions; any address's team report (each day's new performance, new members and lines) is public too; the breakdown by depth and the full list of team members are in the "Members" view of Team, free once you register and sign in. These figures come from the site's indexer; while it catches up, pages show "Indexer syncing" with its progress.
- Notes, groups and tracked addresses (free once signed in): you can add notes and groups to addresses, and keep the addresses you check often as tracked addresses. A tracked address can carry a note too; it is the same note that address shows elsewhere. They are kept in your account on this site's server, and you can export and import them as a backup. Never put a private key, seed phrase or any password in a note.