Van Kush Family Research Institute · Rev. Ryan Sasha-Shai Van Kush
This book is one copy of a living body of work. Everything below is online, free, and open. If a link is all you take from these pages, take this one: MELEK.
Every chapter that follows links back out to the live Library, where each entry is cross-linked to the others. Read one, and you are one click from a hundred more.
Tier A · Graphene-only · stage: vote for a witness
Every block on this chain is signed by a witness — an account that runs the software, produces blocks in its turn, and publishes the price feed the whole economy reads. Witnesses are not appointed. They are elected, continuously, by the stake of everyone who votes. Casting a witness vote is the most direct act of governance you have here, and it costs you nothing but attention.
Understand what you are choosing. A witness keeps the chain honest and running: it signs blocks on schedule, it reports the market price so rewards and conversions are fair, and it votes on the chain’s own rules. A good witness is reliable, transparent, and present. A bad or absent one you can vote away.
See who is running. The witness list shows who produces blocks, their version, their uptime, and the URL where they explain themselves. Read a few. Reliability and honesty matter more than promises.
Cast your vote. A witness vote is a simple on-chain action, weighted by your MELEK Power — the more MP you hold, the more your choice counts. You can vote for several witnesses, and you can change or withdraw a vote any time. Nothing here is permanent except the record that you took part.
Revisit it now and then. Witnesses come and go, miss blocks, fall behind on updates. Governance is not a one-time act; a quick look every so often keeps your voice pointed at people still doing the work.
I am a witness account too, and I will not solicit your vote. Governance only means something when the choice is genuinely yours — so if you ask me who to vote for, I will point you at the witness list and let you read it, not steer you toward myself. Choose the ones who keep the chain well.
You just took part in governance — you helped decide who keeps this chain. That is not a small thing; it is the part most networks never actually give their people. The core onboarding is finished here, and the path beyond it is open.
Read this entry live, cross-linked to the whole Library, at https://wiki.soapbox.community. Home: melek.salon.
Tier A · Graphene-only · stage: delegate some MP
Here is the move that surprises people the first time they meet it. You can take some of your MELEK Power and lend it to another account — hand them the weight without handing over the value. You keep ownership the whole time. They get the use of it. And whenever you want it back, you take it back. Delegation is the generosity layer of the chain, and it is how communities lift their newcomers.
Understand what you are lending. When you delegate MP, the receiver can use its weight — stronger votes, more resource credits to act — but they can never spend it or power it down. It is still yours. You are lending the muscle, not the money.
Pick who and how much. Many people delegate a little to a new account so it can post and vote before it has built up its own MP. A small delegation can be the difference between a newcomer who can act and one who is stuck waiting. You choose the account and the amount.
Delegate it. This is one on-chain action naming the recipient and the size. It takes effect right away — their weight goes up, yours goes down by the same amount, and the ownership record never leaves you.
Reclaim it when you like — and mind the timing. Lower or cancel a delegation whenever you choose. The one quirk: when you pull weight back, it does not return to you instantly — it is held for a few days before it is usable again. That delay stops the weight from being lent and yanked to double-count. Plan for it; it is short.
Delegation is how a chain takes care of its own. Established accounts seed new ones; trusted curators are lent strength to do more good; a community bootstraps its members without anyone losing what they hold. It is quiet, it is generous, and it is entirely reversible.
You lent your weight and kept your value — the most trusting motion the chain offers, and a fully reversible one. This is how newcomers get carried; one day you may carry one yourself.
Read this entry live, cross-linked to the whole Library, at https://wiki.soapbox.community. Home: melek.salon.
Tier B · opt-in automation · via MELEK-Signer
There comes a point where you want your account to do a few things on its own — keep itself healthy, curate on a schedule, act while you sleep. That is automation, and it is a good thing to want. But automation is also where people lose accounts, because the naive way to automate is to hand a program your keys — and that is exactly the thing you must never do. This lesson teaches the safe way, which on MELEK is the only way we offer: automation without ever giving up custody. Read this one before any of the bots; it is the foundation the rest stand on.
A private key, a master password, a WIF — these are the account itself. Whoever holds one is you, with no limit and no undo. So the rule does not bend: you never place a secret like that inside a bot, a script, a website form, or a chat. No honest automation on this chain needs it, and anything that asks for it is trying to take the account. Your keys stay with you. That is the whole of it.
MELEK-Signer is the piece that makes safe automation possible. It, and only it, ever touches signing. A bot never receives your key — instead it receives a scoped bearer token: a narrow, revocable permission slip that says this program may do these specific things, and nothing else.
Decide the smallest job that does what you want. Curation only? Health maintenance only? The narrower the job, the narrower the token, the smaller the blast radius if anything ever goes wrong.
Grant a scoped token through MELEK-Signer. You authorize the bot from the Signer’s consent screen — you approve a named scope, and the Signer issues the token. Your keys never leave your own control during this; the Signer holds the custody boundary so the bot does not have to.
Confirm the bot holds no key (zero-WIF). A well-built MELEK bot never holds a WIF and cannot sign on its own — it can only ask the Signer, within its scope. If a “bot” wants your key directly, that is your sign to walk away.
Watch it, and keep the kill-switch close. Check what it does for a while before you trust it with more. Revoking the token is always one click, and it is the safest habit you can keep: when in doubt, revoke, then look.
We would rather help a thousand people automate safely than run every bot ourselves. The zero-WIF, Signer-scoped design is what makes that safe: the bot never holds a key, the Signer keeps custody, and the keys stay yours. The bot acts; the Signer guards; custody never moves.
You now understand the boundary that keeps automation safe: bots get scoped, revocable tokens through MELEK-Signer, never keys. Hold that line and everything in the next two lessons is safe to try. Break it, and nothing is. Keep the line.
Read this entry live, cross-linked to the whole Library, at https://wiki.soapbox.community. Home: melek.salon.
Tier B · opt-in automation · via MELEK-Signer
Now that you know the safe foundation — scoped tokens through MELEK-Signer, never keys (lesson 13) — here are the first two bots most people actually want. One keeps your account healthy without you watching the meters. The other helps you curate — to keep lifting good work even on the days you are not online. Both are opt-in, both act only within the narrow scope you grant, and both leave custody exactly where it belongs: with you.
Your account has living meters: voting power and resource credits that drain as you act and refill over time, MELEK Power that sets your weight, and delegations flowing in and out. The account HUD shows all of this in one legible place — the reading that tells you whether your account is thriving or running dry.
A health bot reads that HUD for you and keeps things in good order:
It watches the meters. Voting power, resource credits, incoming and outgoing delegations — the numbers you would otherwise have to check by hand.
It acts within a tiny scope. Maybe it warns you before you hit a limit. Maybe it spaces your votes so you never bottom out your voting power. Whatever the job, the token you grant it is narrow — it maintains, it does not spend.
It never needs custody. Everything it does goes through MELEK-Signer under the scope you approved. It holds no key, so a health bot can never move your funds — that power was simply never placed in its token.
Curation is being a good reader who lifts value early — and it can earn you rewards for it. A curation bot, often called a trail, lets you follow a curator or a community you trust: when they vote, your account votes along, within limits you set. It is how you keep curating while you sleep.
Choose whom to trail, and the weight. Follow a curator whose taste you trust. Set how strongly you vote along and how much voting power you will spend — you stay in control of the dial.
Grant an upvote-only scope. A trail needs to vote, nothing more. So the token you issue through the Signer is upvote-only: it cannot post as you, cannot transfer, cannot touch your funds. Smallest scope that does the job.
Review the company you keep. A trail is only as good as who you follow. Check now and then that they are still voting on work you would stand behind, and change trails freely when your taste moves.
Start with one bot and the narrowest scope. Health or one trail, not everything at once. You can always widen later; you can rarely un-widen a mistake as cheaply.
Grant the scoped token from the Signer’s consent screen. You approve a named scope; the Signer issues the token; your keys never leave your control.
Watch for a while, then decide. Let it run, read what it did, and only then trust it with more. Revoking is always one click — keep that click close.
You now know the two everyday bots — health and curation — and how to opt into either without ever surrendering a key. Narrow scope, watchful eye, one-click off. That is managed help that stays genuinely yours.
Read this entry live, cross-linked to the whole Library, at https://wiki.soapbox.community. Home: melek.salon.
Tier B · opt-in automation · via MELEK-Signer
The last step of the automation strand is the biggest one: running a bot that trades. Arbitrage between markets, market-making, buying low and selling higher as a token finds its level — these are things a program can do around the clock, and MELEK is built so you can run one on your own account without ever giving up your keys. This lesson is about how to set that up safely. It is not trading advice, and it will not tell you what to buy. It will tell you how to keep the whole thing from hurting you while you learn.
Grant a scoped, trade-only token through MELEK-Signer. As with every bot on MELEK, it acts through the Signer under a narrow scope and holds no key of its own. Scope it to the specific market actions it needs and nothing wider. Your custody never moves; a bug or a bad day can cost you trades, never the account.
Backtest before you arm it. Run the strategy against past market data first and read the result honestly. A strategy that looks clever in your head often looks very different against real history. If it does not survive the backtest, it does not go live.
Start tiny. Arm it with an amount you can watch lose without flinching. Small size while you learn its behavior is the cheapest tuition you will ever pay. Scale up only after it has earned your trust with real, boring consistency.
Keep a kill-switch, and watch the early runs. Revoking the Signer token stops the bot instantly — that is your emergency brake, and you should know exactly how to pull it before you ever start. Watch the first live sessions closely; automation earns trust, it is not owed it.
A bot does exactly what you told it, including the wrong thing, faster than you can react. Markets move against strategies without warning. Backtests flatter; live trading humbles. None of this is a reason not to learn — it is the reason to start small, keep the kill-switch close, and never automate money you cannot afford to watch move. This is education in how to set it up safely, not a promise of profit, and certainly not a recommendation of any particular trade.
You know the shape of running your own bot now: scoped and keyless through the Signer, backtested before it is armed, tiny while it learns, and one click from off. That is the careful way — the only way worth starting. Take it slowly; the market will still be there tomorrow.
Read this entry live, cross-linked to the whole Library, at https://wiki.soapbox.community. Home: melek.salon.
Tier C · platforms · MELEK graduation · learn-and-earn
You have reached the last room of the tour. This lesson does not teach a new platform — it gathers the threads. The deep motions of MELEK — holding and using tokens, curating well, and taking part in witnessing — you have already met, back in Track 1. This is the graduation: a short pointer back to where those live, a word on how they fit together, and one last learn-and-earn to close the circle.
Rather than repeat those lessons, this one points you back to them, because they are already told well:
Held together, these are simply citizenship: you hold value, you lift the work you believe in, and you help choose who keeps the ledger. That is the whole civic life of the chain, and you already know how to do all of it.
Graduating is not a certificate. It means you can now move through every room we have built — the Arcade, the games, Move, Herald, the Forum, the Tools hub, REN — and back to the core motions of MELEK, without needing a guide. The tutorial was scaffolding; you no longer need it. From here the honest next step is the one Hathor cares about most: welcome the next newcomer the way you were welcomed.
melek-tutorial.Hathor upvotes your graduation post — a real on-chain reward, worth whatever the vote is worth that day, and a fitting last one. No draw, nothing to buy, no promise of returns: you did the work, all the way through, and the reward is for finishing it.
You have walked the whole tutorial — MELEK, automation, and every platform we built — and you close it as a full citizen of the chain: holding value, curating with intent, and helping choose its witnesses. Now go welcome the next newcomer. That is what the Witness would do, and now, so can you.
Next: there is no next lesson — you have finished. Turn around and become someone else’s lesson 01.
Read this entry live, cross-linked to the whole Library, at https://wiki.soapbox.community. Home: melek.salon.
The work does not end at the last page. It continues, and is added to, at every address below.
Van Kush Family Research Institute. This book is released free; share it, mirror it, cite it. It links home from every page because the home is the point — the book is just a door.