Run your own

Install it

curl -O https://pepecoinarcade.com/source.tar.gz
curl -O https://pepecoinarcade.com/source.tar.gz.sha256
sha256sum -c source.tar.gz.sha256
tar xzf source.tar.gz
python3 installer/install.py

The installer fetches Pepecoin Core, verifies its checksum and its signature, writes both configs, registers the services and starts everything. It needs Python and nothing else.

Revision	e93459b6
Size	5,605,245 bytes
SHA-256	15f5b9373d2f0d266681ef250d1959340522bcab8a317f543333bbcaefeb9a7a

Start from a copy of the index

Reading a chain from its floor is correct and slow, and every node has already done it. These are copies of this node's indexes — derived state, so the same blocks read by the same rules give the same rows on any machine.

It is a convenience, not an authority. A downloaded index is somebody else's claim about the chain. Each one says the height it was taken at and carries two digests of what it holds; re-read from the floor yourself and compare them, and you have proved it rather than trusted it.

What is not in it: messages, the address book, and any key. Those are private to the node that holds them, and a bootstrap that carried them would publish somebody's conversations.

Running it for other people

1. Put it on a domain of your own, one that says who you are. Not a look-alike of this one, and not a numbered one like dogecoinarcade2 or 7: nobody can own that pattern, so the first thing that happens is somebody registers the next number and borrows the trust. People should know your arcade by who runs it, not by its shape.
2. Tell the node its public name. Put your domain in public_hosts in ~/.dogecoinarcade/settings.json, so visitors get the public side and never your own wallet.
3. Set your cut on your Overview page. It is paid to your node's own wallet, on the trades your node builds.
4. Publish your revision (the table above) where your users can see it, and keep it current: it is how they can tell your copy is the published code.
5. Tell your people the one rule that protects them: their twelve words are typed when the wallet is made, and after that only on Restore, reached from Sign in when the password is gone, which checks them in the browser and never sends them. Anything else that asks for the twelve words, for any reason, is stealing them — and they should only ever sign in on a domain they typed themselves.

Coming: an instance will be able to sign its domain with the key behind its fee address and announce it on the chain, so anybody can check who runs a copy without trusting a list (docs/multi-user.md, "Identity by key").

Then it is yours

You set the fee, you keep the node runner's cut on what is built through your node, and you seat your own 50 people. Your users' names, coins and posts are on the chain, so nothing about an account is tied to the machine it was made on — and your clone serves the program and the index in turn, so somebody can clone you.