A hundred participants learn the exact date of the Assetrix deployment at least seven days before everyone else, and the contract address at the minute it goes live.
Everyone has equal rights to use the contract. But the cost of entry keeps rising, so learning the exact deployment date first is not only interesting but also worthwhile.
7 daysat least: notice of the exact deployment date
10,500 USDCThe fund only grows. The organizers of the programme can raise the prize fund at any time and never lower it, the way a ratchet turns one way only.in prizes over three months
On 8 February 2027 at 12:00 UTC, after the closing week, the list of the hundred participants with the most points is fixed. Each of them receives:
the exact date and hour of the deployment, at least seven days ahead and before everyone else, with a reminder one day before;
the contract address at the minute of deployment, directly from the project, before aggregators show it;
a name in the public list of early participants on this site: the name the participant chose for the tables. A participant without a chosen name is not named in the list.
Each of them receives all of this directly in the bot, even with the sound turned down. The hundred has no separate closed group.
No queue to the protocol. The programme gives priority in information, not in access: the contract does not tell people apart. Everyone has equal rights to use it.
Who learns the date first: 100 to 120 people
Who
How many
Why
The hundred with the most points
100
For work on explaining and spreading the protocol. They do the tasks and can win money prizes.
Administrators on the team on the day the list is fixed
up to 20
For helping to run the programme. They review the work of others instead of doing tasks, so they take no money prizes: a reviewer must gain nothing from a decision.
An administrator blocked after the list is fixed does not receive the date or the address. One removed from the role does.
If a seat frees up
A member of the hundred who drops out after the list is fixed (banned, blocked or who deleted their record) receives nothing more, and the seat passes to the next participant by points. The new member of the hundred gets a message about it, the date if it was already announced, and the address at the minute of deployment. Once the address has gone out, seats no longer pass on.
A seat that passed on is never taken back. If the one who dropped out is restored on appeal, they return to the list without pushing anyone out.
Only a participant with points holds a seat: a participant without points is not on the list and does not take a freed seat. A participant banned or blocked before the list is fixed and restored on appeal after it gets a seat above the hundred, if their points on the day of fixing were enough for the hundred and the address has not gone out yet.
With equal points, the one who subscribed to the bot earlier ranks higher.
The line
Until the list is fixed, the cabinet shows the line of the hundred rather than the overall leader: how many points participant #100 has, and how many you still need. A newcomer aims at the line, not at first place. The monthly race runs separately and starts from zero every month (see Prizes).
Until the list is fixed, the cabinet shows the line: the points of participant #100.
All times 12:00 UTC. The deployment date is a target, not a commitment.
Event
Date
Warm-up
From 15 October 2026. The rules are published, and the bot records participants and their invitations. Points start when the programme opens.
Programme opens
1 November 2026, 12:00 UTC
Monthly races with prizes
November and December 2026, January 2027: 3,500 USDC and twenty places each month, 10,500 USDC over three months The fund only grows. The organizers of the programme can raise the prize fund at any time and never lower it, the way a ratchet turns one way only.
Results of the month
Once the month is over, all its work is reviewed and every disagreement about it is answered: no later than the 8th of the next month. January results come with the fixing of the list.
Submissions and invitations close
1 February 2027, 12:00 UTC
Closing week
1–8 February 2027: submitted work is reviewed, and invitations complete their seven days
The list is fixed
8 February 2027, 12:00 UTC: after the closing week, once the queue is empty, every disagreement is answered, and work returned for changes has had its seven days
Deployment of the contract
Planned by 1 March 2027. This is a target, not a commitment. The hundred and the administrators learn the exact date at least seven days ahead.
The public countdown runs to the opening of the programme and then to the fixing of the list, not to the deployment: these are the dates the project fully controls.
Limits keep a seat from being taken by repeating one action. The limit on invitations keeps the list mixed: twenty invited people is the most that invitations can bring, and beyond that a seat takes a contribution. The share from invitees is bounded by your own work too.
The bot awards some points by itself: for invitations, the share from invitees, the first-work bonus and the Google bonus for a site. An administrator awards all others after reviewing the work.
The project channel
Subscribing to the channel @assetrixdao brings no points: Telegram rules forbid paying for subscribers. The subscription is a condition for an invitation to count, and a way to tell a person from a bot. Starting the bot brings no points either.
Every participant gets a personal link and a card with a QR code (Your cabinet). An invitee counts when all three hold:
they came to the bot through this link and had not been in it before;
they stayed in the bot for seven days and are subscribed to the channel @assetrixdao;
they came back to the bot at least once after the first visit: opened the cabinet, asked a question or checked an address.
+3 points for each invitee who countsup to 20 people
+¼ of their points for work, each monthno more than your own points for work
Your flock: the people who came through your link.
Each counted invitee brings 3 points, up to 60 for the whole programme, that is 20 people. One person brings invitation points once: deleting their record or following another link does not change that. An invitee counted above the limit brings no points, but the share from their work still comes.
The share from invitees
The inviter gets a quarter of the points the invitee earned in the month by their own work: the same points that count towards the threshold (Prizes). The quarter is taken from the month’s total and rounded down. It comes on top: the invitee loses nothing.
In a month, the share is no more than the inviter earned by their own work in that month. The rest waits for the inviter’s work, and what has not come by the end of the month is lost. An invitee who dropped out, or who was removed as manipulation, brings no share.
What does not count
Self-invitations, invitations from a second account of the same person, and invitees with no activity at all do not count. An administrator may refuse a series of invitations that looks like manipulation: fresh accounts without history, the same creation time, no activity. The decision goes into the public journal with the reason.
Invitations made before the programme opens count from its first hour. An invitation goes into the prize race of the month in which it counted; those counted in the closing week go into January. Invitations after 1 February 2027, 12:00 UTC do not count.
A participant sees their invitees under the same names as in the tables: whether each one counts, what is missing, and how many points each brought. When an invitee counts, the bot tells the inviter.
Keep your link out of other people’s groups. Do not post it in other people’s Telegram groups and do not send it to strangers. This leads to a penalty, up to a ban (Penalties).
The limits by type in this table apply to the tasks under Points. A new task type (Changes to the rules) is accepted on every platform in the table except the participant’s own site or blog.
Why half on our own platforms. The Assetrix discussion group and the Assetrix thread on Bitcointalk already hold our audience: nobody there needs winning over. A reply to a critic there is useful, but half as valuable as the same reply on X or in someone else’s forum thread. The top of the range is halved, so a reply to a critic on our own platforms is worth 5 points. This is not a penalty, only a difference in use to the project.
Not accepted: closed channels and chats, platforms that require signing in to read, and posts in your own channel without an outside audience.
An administrator checks what a Telegram group is about: a group that is not about crypto is a reason to decline. In someone else’s group, the participant answers the objection and leaves no invitation link (Invitations).
Your own site is a platform only for the site task. It is a site on your own domain, on a free site builder, or a blog on a blogging platform. A page on a social network, in Telegram, on YouTube, on GitHub or on a forum is not a site. The site’s address must not contain the words assetrix or astrx: such addresses are easy to fake.
Each task has a range of points. The administrator sets the score within it by the criteria below. The button See an example on a task screen in the cabinet leads to a sample of top-scoring work of that type once one is published. The sample for the test run is a full report on the route, worth 30: a 50 is given only for a mismatch found with the documents.
A thread, a post or a video that explains how the protocol works.
20
Explains in your own words and takes on a non-trivial point: why redemption is neutral, why the corridor holds, why a vote is cast by burning tokens. No factual errors, and a link to the primary source.
15
Correct and clear, but the topic is simple: what a position is, how it differs from a stablecoin.
10
Correct in substance, but close to a retelling of our text, or very short.
The participant makes a site or blog about Assetrix, even a single page, in any language, with a link to assetrix.org. One site per participant for the whole programme. Whichever page of the site is sent, the site counts as one work.
The site is accepted if it:
says it is a participant’s site, not the official site of the project, and names where the official one is;
links to assetrix.org with rel="sponsored" or rel="nofollow": Google treats a link placed for a reward as paid, and the attribute protects both sites;
carries the tag #AssetrixEarlyBirds;
has at least 300 words;
has no wallet addresses and no requests to connect a wallet.
30
Explains the protocol correctly and in your own words, covers more than one mechanism, keeps the market price apart from the mint price, and claims nothing beyond the documents.
25
Correct and clear, but on one topic, or close to our texts.
20
Correct in substance, but short.
Your own banner: +10. A picture about Assetrix made by the site’s author, with a link to assetrix.org. An administrator counts it.
A place in Google: +10. Right after submission, and for a month afterwards, the bot searches Google for site:your-site Assetrix OR ASTRX. If Google shows the site by the review, the bonus comes with the work. If later, the bot adds it by itself, into the race of the month in which it happened, until the list is fixed. You can submit the site without waiting for Google.
Part
Any other language
English, Spanish, Chinese
Content
20–30
10–15
Your own banner
+10
+5
A place in Google
+10
+5
At most
50
25
In English, Spanish and Chinese everything is halved: the official site already speaks these languages. In any other language, the full amounts apply. The bot detects the language from the text of the page.
Not accepted
one article instead of a site, or a site about something else;
Your own thought, at least twenty words. Forwarding someone else’s post without words of your own is not accepted. The same text under different posts counts once.
A mismatch of figures between documents, an error in a formula, a wrong statement about the mechanics, a broken link in a published document, a defect in the code. The report names the exact place, what it says, what it should say, and the proof.
50
The error changes the meaning: a wrong formula, a figure a reader bases a decision on, a vulnerability.
25
The error does not change the meaning: a broken link, a wrong section number.
A vulnerability is never published openly. Send it in the bot with the command /vuln: only the owner reads such a message. It is checked and scored in the same range, as points without a submission (Review), and published after the fix.
Not accepted
typos and punctuation;
“this seems unclear to me” without pointing to an error;
The most important task of the programme. The participant goes through the main functions of the Assetrix holder account on the test network and tells publicly what they did, what they got, what was convenient and what was not. The route is required:
1Create a wallet in MetaMask.
2Add the Arbitrum Sepolia network to the wallet.
3Enter the Assetrix holder account on assetrix.org with this wallet.
4Take test gas from an external Arbitrum Sepolia faucet, and test stablecoins in the holder account itself.
5Open a position.
6Do any three of five: redeem part of the position, close the position, buy or sell ASTRX on Uniswap, vote, send to another address.
The proof is a screenshot of your holder account on assetrix.org that shows the address of the test wallet. The screenshot is published with the report. The report gives the steps, links to the transactions, what the documents led you to expect and what happened. The short film of the holder account and the test network page show the way.
50
A mismatch between behaviour and the documents is found: a figure does not match, a screen says something else, a refusal without a reason the documents name.
30
A full report on the route that anyone can repeat; everything matched the documents.
Submit work in your cabinet, on the Tasks tab: a link, the text of the work, and one line saying what it is. For a site you do not paste text: the bot reads the page itself. The work must be:
published publicly and open without signing in;
published after the programme opens and submitted before 1 February 2027, 12:00 UTC;
available for at least seven days after submission. If it is removed earlier, the owner or the lead administrator take its points away while those seven days run; the reason goes into the public journal, and the same link cannot be submitted again;
tagged as part of the Early Birds programme: #AssetrixEarlyBirds.
Work counts in the prize race of the month in which it was submitted, even if it is reviewed later. Work returned for changes and submitted again counts in the month of the new submission.
One page is one work. Links to the same page (x.com and twitter.com, share tails, short YouTube and Reddit addresses) count as one work; comments in one thread count as different works. A site is one work as a whole, whichever page is sent. The exception is a second try of the same page after a decline (Reasons for declining).
The bot refuses work above the monthly limit of its type right at submission. Work still waiting for a decision or returned for changes counts towards the limit; a decline frees the place.
The tag is required, and here is why. The programme pays money prizes, so participants are interested parties. Since February 2026 the rules of X require paid promotion to be disclosed, and an untagged post can cost a participant their account and the project its reputation. The tag removes this risk. It also confirms authorship at review.
What the bot checks by itself
Five checks run at the moment of submission, before an administrator sees the work. Four of them stop the submission. Work submitted again after a return goes through the same checks on the corrected text.
More than half the text matches work already accepted, your own or another participant’s
the submission is refused
More than a third of the text matches our own texts
accepted with the mark “retelling”; an administrator decides
For a site, the bot also checks the address, the marked link to assetrix.org, wallet addresses and requests to connect a wallet (without these the submission is refused), and looks for the site in Google.
What the check does not do. It does not decide whether a person or a machine wrote the text: there is no reliable way to do that, and we will not promise one. It catches other things: someone else’s platform, a missing tag, work that is too short, a copy of work already accepted, your own included, and a retelling of our own texts. One publication is one work.
You always paste the text of the work when submitting, except for a site: X and some other platforms do not give the text to the bot without signing in, and the checks run on the text. The bot downloads the page itself where the platform allows it; an administrator compares the text with the link now and then.
A person reviews the work: an administrator. There is no automatic scoring and there will be none: the bot only shows the administrator the results of its checks.
Review takes up to 48 hours. The cabinet shows how long your work has been waiting.
The administrator scores the work within its range by the criteria in Tasks and scoring, returns it for changes with a note, or declines it with a reason from the closed list (Reasons for declining).
Work returned for changes is corrected and submitted again within seven days, and counts in the month of the new submission. Only the participant sees the note; the journal records only the return. Work not submitted again in seven days does not count and no longer takes a place under the monthly limit. The same link cannot be submitted again; a new publication can.
Every award, removal of points, return and decline goes into the public journal: to whom, for what, how many points, and a link to the work.
A disputed case is decided in the participant’s favour.
Disagreeing with a decision
Under accepted or declined work there is the button Disagree: one per work, up to 500 characters. A return for changes is not yet a decision: the work is corrected, and the right to disagree stays for the decision on it.
A disagreement goes to the owner and the lead administrator, not to the one who decided. The one who decided does not learn who disagreed, and the disagreement does not go into the journal. The answer comes in the bot. A disagreement with a decision of the lead administrator is handled by the owner; only the owner changes the owner’s decisions.
If a disagreement is upheld, the decision changes in the participant’s favour: the score of accepted work goes up, and declined work is accepted. The points go to the month of submission. If the results of that month are already announced, they are not revised, and the points go to the overall total.
The results of a month wait for answers to every disagreement about its work, and the fixing of the list waits for all of them. After the list is fixed, disagreements are not accepted: decisions no longer change.
Points without a submission
From the opening of the programme, an administrator can award 1 to 50 points for a contribution without a public link: for example, for a vulnerability sent with /vuln (An error found). An explanation is required and goes into the journal. Administrators award no points to themselves or to one another.
An administrator does not score an error in the code: they pass it to the owner, and the owner scores it. Administrators score all other work.
In the closing week, 1–8 February, the queue is cleared completely: while any work waits in it, the list is not fixed. Work returned for changes also holds the fixing while the participant’s seven days for corrections run.
The list is closed. An administrator chooses from it and does not write a reason in their own words.
Promises of returns or a price forecast final
A factual error about the mechanics
A retelling of our text without a contribution of your own
Not a site or blog about Assetrix: one article, or a site about something else
The site poses as the official one
No tag of participation in the programme
Published before the programme opened
The link is unavailable or requires signing in
The Telegram group is not about crypto
Removed before seven days had passed
Manipulation: fresh accounts, repeats, bot activity final
Insults, attacks on other projects
A duplicate of work already accepted
The monthly limit for this type is exceeded
Not an error: a typo, style, or something already known (An error found)
Test run: the route is not complete, or there is no proof (A test run)
Forwarded without words of your own (A short post)
Two declines are final: promises of returns and manipulation. After any other decline, the same link can be submitted once more: correct the work on the same page or, after a decline for the monthly limit, submit it in the next month. The second try counts in the month in which it is submitted; there is no third.
Work published before the opening, removed before seven days, or published in a Telegram group not about crypto cannot be fixed on the same page: a new publication replaces it.
every month3,500 USDCThe fund only grows. The organizers of the programme can raise the prize fund at any time and never lower it, the way a ratchet turns one way only.20 places
1st1,000
2nd500
3rd300
4th–20th100 each
November, December and January: 10,500 USDC in all.
Place
Prize
Condition
First
1,000 USDC
the most race points of the month among those past the threshold
Second
500 USDC
—
Third
300 USDC
—
4th to 20th
100 USDC each
seventeen places
The programme budget is 3,500 USDC a month for three months: 10,500 USDC The fund only grows. The organizers of the programme can raise the prize fund at any time and never lower it, the way a ratchet turns one way only.. Extra places set by the owner add their sum to the budget of their month and to the total.
Threshold. A monthly prize goes only to a participant with at least 10 points that month for their own accepted work. The first-work bonus and points awarded by an administrator without a submission count towards the threshold; invitation points and the share from invitees do not. Beyond the threshold, race points are needed too: if penalties took them all, there is no prize.
Race points. The race of the month counts points for work submitted that month, the first-work bonus, points awarded without a submission, invitations counted that month, and the share from invitees for that month. Invitations counted in the closing week go into January. Every month starts from zero: a newcomer starts level with everyone.
How many prizes. As many as there are participants past the threshold, but no more than there are places. Places go from the top down by race points.
Carry-over. The money of places nobody took, and prizes the winner never claimed, passes to the next month. There it opens extra places of 100 USDC, if more than twenty people passed the threshold. The carry-over does not increase the size of prizes.
January. In the last month, the carry-over opens no places. The whole regular January fund, together with the carry-over of past months, is divided among the occupied regular places in proportion to their size. So January amounts depend on how many people passed the threshold, and are final only when the results are summed up.
Extra places. The owner may create extra prize places for any sum in the current month. They enter the table at once by sum; with an equal sum, a regular place ranks higher. They are marked Extra bonus, last until the end of the month and do not carry over; they cannot be cancelled or reduced. This is separate money: it does not touch the carry-over of the regular fund. The sum of added places counts in the budget of its month and in the programme total, and the bot, the cabinet and the card name the budget with these places. Every participant receives the announcement, and it goes to the channel and the journal. In January, an extra place must not cut anyone’s prize: a place that would cut one stays empty. That is why the sum in a January announcement reads “up to”.
Results. They are announced once the month is over, all its work is reviewed and every disagreement about it is answered: no later than the 8th of the next month. January results come with the fixing of the list, on 8 February. Months close in order: November, December, January.
Payment
Prizes are paid in USDC on Arbitrum One, by hand: the bot holds no money. After the results, the bot asks the winner for a wallet address. The winner has 30 days for this, with reminders 7 days and one day before the end. Payment comes within 10 days of receiving the address. An address the winner already gave carries over to their next prize.
If there is no address in 30 days, a regular prize returns to the fund and an extra-place prize expires. A January prize has nowhere to return: without an address in 30 days, it is not paid. The owner marks each payment with the transaction hash.
Winners are published in the journal and the channel. One participant can win in different months.
With equal points, the one who reached them earlier ranks higher: the one whose last award of the month came earlier. For work, the time of submission counts, not the time of review, so the speed of review does not affect the place.
Taxes on a prize are the recipient’s responsibility.
A quarter of the race points of the month the participant has at that minute is taken off. A skull appears by the name.
−50%
Half of the race points of the month at that minute is taken off: after −25%, half of what is left. A second skull.
Ban
Out of the prizes and out of the hundred until the end of the programme.
A deduction is made once, rounded in the participant’s favour: 12 points become 9 after −25%, and 5 after −50%. Points earned after a penalty come in full. The threshold of the month counts the work actually done. A penalty does not touch the points for the hundred.
All penalties except a ban last until the end of the month. On the first day of the next month the skulls go and the steps start again; what was taken stays taken in its month’s race. January penalties last until the January results.
A penalty before the programme opens takes no points and lapses at the opening. A penalty in the closing week takes points from the January race, whose results come with the fixing of the list. After the list is fixed, points are not taken. After the fixing, only the owner and the lead administrator can ban, and the seat of the banned participant in the hundred passes to the next (If a seat frees up).
A reason is required, up to 200 characters; a comment is optional, up to 300. The reason, the comment and the points taken go into the public journal, and the participant gets a message.
Ban. The participant is out of the prizes and the hundred until the end of the programme. Grounds: manipulation of invitations or activity; promising returns in the project’s name; posing as the administration; selling or handing over a seat. A ban does not take away a prize of a month already closed.
Block. The bot stops serving the participant, and they are removed from the discussion group. A blocked administrator loses the role. An unpaid prize of a blocked participant is not paid, even if they already gave a wallet address: when its time runs out, the prize returns to the fund, and a January prize is not paid. If the block is lifted on appeal before the time runs out, the prize is paid as usual.
Who imposes them. An administrator only in steps: −25%, then −50%, then a ban; after the list is fixed, administrators impose no penalties. The owner and the lead administrator choose any penalty in any order, ban and block at once, and always see who is penalized now, by whom, and each participant’s history of penalties. Administrators are not penalized: they are removed from the role and never return to the standings. Only the owner can block the lead administrator.
Lifting. On a well-founded appeal, the owner or the lead administrator lift all current penalties at once, never one of two. The points return, the skulls go, and until the end of the month the name carries the mark Rehabilitated. A deduction of the past month can also be lifted while the results of that month are not announced; announced results do not change. Only the owner lifts a penalty the owner imposed. What is lifted is what the one lifting saw on the screen: if something changed meanwhile, nothing is lifted. The lifting is published in the journal, and the participant gets a message.
An appeal is made in the bot chat; a blocked participant writes to the project by email.
The rules may be refined. A change is announced in the channel and the bot at least seven days ahead and applies from the next round. Awards and declines are never revised retroactively.
Rates and limits of existing tasks do not change in the current round. A change to them applies from the first day of the nearest month that begins at least seven days later: a change made on 28 November applies from 1 January. A change that takes effect in less than seven days can no longer be changed or cancelled. From 25 December rates and limits no longer change. Before the programme opens, a change applies at once.
Work is scored by the rates of the month in which it was submitted, even if it is reviewed later.
New task types
New task types are the exception. The owner and the administrators may create a new type at any time, and it applies at once: it adds opportunities and takes nothing away from what was announced.
A new type is worth 1 to 50 points.
It has a description of what exactly to do, and an optional deadline in UTC. At that minute the type leaves the cabinet by itself; work submitted before the deadline is still reviewed after it.
It is accepted on all platforms from Where to publish except the participant’s own site or blog; in the Assetrix thread on Bitcointalk and in the discussion group, for half the range.
A type that is no longer relevant can be switched off: it disappears from the cabinet, and the points awarded for it remain.
A new type appears in the cabinet, and a record of it in the public journal.
Appoints and removes administrators and the lead administrator. Switches news mailings on and off for the lead administrator and administrators. Only the owner creates extra prize places, keeps the official list of addresses and links, fixes the list of the hundred, announces the deployment date, sends out the contract address, marks prize payments and exports the participant base. Together with the lead administrator: imposes any penalty, bans and blocks at once, lifts penalties (only the owner lifts the owner’s own), removes points for work deleted before seven days, handles disagreements and applications to the team. Approves changes to the rules. Scores errors in the code and receives vulnerability reports.
Lead administrator
One for the programme, appointed by the owner. Appoints and removes administrators. Sends news while the owner has not switched mailings off for them, and while they have it, switches it on and off for administrators. Imposes any penalty, bans and blocks at once, lifts penalties except the owner’s, and sees who is penalized now, by whom, and the history of penalties. Removes points for work deleted before seven days, except work the owner decided on. Sees administrators’ statistics, handles disagreements and applications to the team. Does everything an administrator does. Cannot create prize places, appoint or remove the lead administrator, close a disagreement with their own decision, or change the owner’s decisions. Money, official addresses, dates, the fixing and the export belong to the owner alone.
Administrator
Reviews work: accepts it with a score, returns it for changes, or declines it with a reason. Passes errors in the code to the owner. Awards points without a submission, 1 to 50, with an explanation, and never to themselves. Penalizes only in steps: −25%, −50%, ban, until the list is fixed. Removes uncounted invitations as manipulation. Creates, edits and switches off task types. Sums up the results of months. Sends news if the owner or the lead administrator switched it on. Answers participants, and never writes to anyone first.
Participant
Invites, submits work, and sees their place in the monthly race and against the line of the hundred, the breakdown of their points, their invitees and the public journal. Once in ten days can write to an administrator, up to 300 characters; the owner and the lead administrator see a copy. Can disagree once with each decision on accepted or declined work. After the first accepted work, can apply to become an administrator.
red
amber
green
blue
violet
teal
Administrators are known by colour. Their names stay private.
Administrators are anonymous. Each administrator has a colour instead of a name: administrator red, amber, green and so on. The public journal and messages to participants show the colour, not a name, a handle or an identifier. Only the owner and the lead administrator know which colour is which person; an ordinary administrator does not see it even in the journal. The colour stays on past decisions after the person leaves the role.
There are no more than twenty administrators, the lead administrator included. They do no tasks, take no prizes and are not in the tables, neither while on the team nor after. They learn the deployment date together with the hundred, for helping to run the programme. After the launch, administrators are the first to be considered as candidates for the Assetrix team.
How to become an administrator
The button Apply to join the team is on the Administrators tab of the cabinet. You can apply once in the programme, when all of this holds:
at least one of your works is accepted;
you have no penalty this month (lifted penalties, and those that lapsed with the past month, do not count);
the team has fewer than twenty people;
submissions are still open: until 1 February 2027, 12:00 UTC.
The application is written in English, 20 to 500 characters: why you, and how much time you have. The owner and the lead administrator decide, and the answer comes in the bot. An approved application makes the participant an administrator and takes them out of the standings for good.
The owner and the lead administrator can appoint anyone as an administrator without an application, except a blocked participant; that person’s application then closes by itself.
The participant’s cabinet is the page earlybirds.assetrix.org. The bot leads to it with one button: Telegram confirms the sign-in, and there is no password. From another device, you sign in with a code confirmed in the bot. The programme has no Telegram mini app: Telegram rules allow only the TON blockchain in them.
Name. Tables, the feed, the journal and the results show only the name the participant chose. Without a chosen name, the participant appears as Participant with a number. The Telegram name is not published anywhere.
A name has up to 24 characters. It cannot contain invisible or control characters, letters that imitate Latin ones but belong to another alphabet, or anything that resembles Assetrix or the team: admin, support, official and the like.
Your bird. Instead of a photo, each participant has a bird drawn from their number; the button Another bird gives a different one. Pictures cannot be uploaded.
Flag. A country flag by the name is decoration. The participant chooses or removes it; without a choice, the flag is guessed from the Telegram language and marked as a guess.
Your card. Each participant has a card of their own: the bird, the place, the flock of invitees, the invitation link with a QR code and the programme’s prize budget. Share it on X and Telegram: the open page of the card gives it a preview and a button to the bot. Participants who dropped out and the administration have no cards. The card carries no Telegram name or number; a participant without a chosen name is signed on it as in the tables, Participant with a number. After 1 February 2027, the card no longer promises points for invitations.
Verify. The Verify tab checks an address or a link against the project’s official list: is it ours.
/quiet turns the sound down. Decisions on your work, the results of months and everything about the hundred always arrive.
/vuln reports a vulnerability: only the owner receives the message.
/forget deletes your record: points, work, invitations and the seat in the hundred go with it. The journal keeps decisions without the name. An unpaid prize of a closed month stays in the results with its address until it is paid. The first-work bonus is not given twice. A returning person is not new: they do not become an invitee, by the old link or by anyone else’s. A record with a ban, a block or an administrator role is not deleted, and one with a penalty this month not until that month’s race ends.
In one sentence. Early Birds gives a hundred participants information before everyone else: the exact deployment date at least seven days ahead, and the contract address at the minute of deployment. Everyone has equal rights to use the contract, but the cost of entry keeps rising, so learning the date first is not only interesting but also worthwhile.
Rules version 1.5 of 27 September 2026. A change is announced in the channel and the bot at least seven days ahead.