Issue 002 — the submission is in
The entry went in before the deadline, what is already live still stands, and the bench gained a world that does not open yet.
- newsletter
- edition-002
- hackathon
- solana
The hackathon submission was due October 12 and it was sent. This issue is the receipt: what went in, what did not change because of it, and what is on the bench now — public summary of the submission.
What fell off the truck
The entry for the Crypto World's Fair, Colosseum's online hackathon, was submitted before the deadline. What went in was the Private Vault — which runs on Solana mainnet, with real money and a small amount — and the house around it: the lab tools, the public archive and the documentation that says where each piece breaks.
What this is not: a prize, a customer, or validation. A hackathon prize proves the idea convinced judges within a week; it does not prove revenue, longevity, or that anyone will use it. Nothing on the site changed because of the submission. What changes is the schedule.
From the lab
What was already live still stands, and it is worth repeating what each piece does, because a piece without a declared limit turns into a promise:
- The Hash Notary computes SHA-256 inside your machine. The text is not sent anywhere — and a hash proves the content existed, not who wrote it or when.
- The Private Vault hides the link between deposit and withdrawal on mainnet. It does not hide the fee: 0.005 SOL plus 0.3%, and above 10% of the amount the vault warns you and asks for confirmation. The note created at deposit is the money — without a backup, it is gone.
- PRX on devnet is still arithmetic computed in the browser: supply, decimals and mint authority. It is not a token that was created, and it will not be called one before an explicit decision per operation.
The measured part of the week came out as an article: the container is not slow, the shared folder is — 2000 small files take 10.27s on one side and 0.15s on the other.
The bench
A 3D world that opens in the browser, with no sign-up and nothing to install. It is in development and it is not on the public site. Which means: no date, no countdown and no "coming soon" — an invented number does not pass around here when the subject is money, and it will not pass when the subject is a deadline either. When it opens, it opens with something you can check on screen.
Internet thing
OpenTimestamps stamps a file on Bitcoin and returns an .ots receipt that travels with the file. The calendar servers are free, with no sign-up and no API key, and the receipt is verified from the command line — pip3 install opentimestamps-client and ots verify. It is the older sibling of what is studied here: proof of existence with the receipt in the owner's hands, instead of a service promising to keep it for you. Where the piece fits is in proving the text is the same.
Next time
What the bench became once it leaves the local browser, plus an experiment that may still fail — and if it fails, the issue says it failed. Subscribe to get the next one. If you do not subscribe, nothing happens: the issue stays in the public archive anyway.