Steem Testnet Relaunched
A little over a year ago, I launched a Steem testnet. Back then, the goal was to gather experience and provide a test environment for new projects.
The testnet served its purpose, but it was doomed. At the beginning of this year, there was a security incident at the hoster that left the server beyond saving… including the backup stored on it!
Since there was no obvious need for a reinstallation afterwards, I didn't pursue it further at first. Now, however, @faisalamin has reached out and could use a test environment.
Setup
I no longer had a backup, but I did have an Obsidian vault full of notes. So the setup shouldn't be as new and challenging as the first time.
Shouldn't! Things turned out a bit differently.
I no longer wanted to run my own custom testnet, but rather the "official" testnet that is built into the regular steemd code. This meant I could use my current version 0.23.2, which still had to be built as a testnet.
However, this code is based on the recent Ubuntu 24.04. That means the small tools used for the testnet are also built on this system. The other tool, Tinman, complained about this, as it was still based on old Python 3.6 code. So I first had to adapt Tinman to Python 3.12.
After that, I still had to pull a snapshot from the main chain so that all accounts would also exist on the testnet.
Then it was a matter of setting up witnesses, distributing assets, and creating the corresponding blocks with the debug_node plugin. On the side, I also submitted an update to the steemd code.
Testnet
The testnet is up and running, and the 21 configured witnesses are producing blocks. Every account that existed on the main chain until the beginning of November is also available on the testnet. You can perform actions there using your main chain keys.
I think I need a testnet block explorer or something else to see the activities on the testnet.
However, this is my first transaction:
The configuration can be retrieved directly from the chain. Have fun testing!
If you have any questions, feel free to leave a comment.
The address is:
https://testapi.moecki.online
Steem Search on https://moecki.online/ |
|---|
19.11.2026
Hört sich wieder nach Arbeit an!
Dachte spontan, ich lasse ein auf die Testapi angepasstes Standard Frontend in einem GitHub Codespace laufen. Nur so aus Neugier um ein paar Tx abzusenden. Denke, da müsste man etwas mehr verbiegen als nur die Einstellung der API. Hmm, ich glaub ich lass das lieber, bevor ich dein Testnet kaputt mache!
0.00 SBD,
3.87 STEEM,
3.87 SP
Danke.
Wenn das Frontend vornehmlich die Abfragen aus der
condenser_apiverwendet, dürfte das sogar machbar sein. Das Steemit-Frontend braucht aber diebridge_apimit den Abfragen, die an Hivemind gehen. Hivemind habe ich für die Test-Chain nicht aufgesetzt und daher wird das nicht funktionieren.Für Hive (und früher auch für Steem) gibt es aber ein Skript (TinToy), das mehrere andere Dienste für ein Testnet startet. Da ich nun einige Schritte schon mehrfach machen musste, hatte ich mir auch überlegt, ein Skript zur Automatisierung zu bauen. Oder vielleicht gleich das TinToy wieder für den Steem anpassen. Mal sehen...
oder du fängst schon mal an ;-))