Grinffindor.org Services

Grin Infrastructure & Development Update (Last Weeks)

Over the past two weeks I have been working on building infrastructure and tooling to support the Grin ecosystem and improve accessibility for users and developers.


Grinffindor Services

These endpoints provide public access to nodes and services.

Hardware & Infrastructure

  • Purchased a miner for the Grin testnet

  • Installed a 42U server rack

  • Acquried two Dell servers:

    • one dedicated to development

    • one dedicated to the Grin ecosystem services


Virtualization & Services

The infrastructure runs on Proxmox with multiple VMs:

  • Reverse proxy VM

  • Testnet node VM (including Stratum server)

  • Mainnet node VM

  • Testnet Telegram bot VM

  • Mainnet Telegram bot VM

Node capabilities

  • Operating as DNS seeders

  • Foreign APIs are publicly accessible → wallet connectivity enabled


Telegram Bots

Mainnet Faucet Bot

Testnet Faucet + Tipping Bot

Testnet Tipping Feature (New)

Last week I extended the testnet bot with tipping functionality.

Commands

  • /deposit

  • /withdraw

  • /tip

Technical details

  • Wallet runs in a separate account/path

  • Tips are executed off-chain between Telegram users

  • Deposits and withdrawals use Slatepacks

  • Currently in testing phase

Test group:

Community testing and feedback are very welcome.


Role of the Infrastructure

This setup aims to:

  • improve wallet connectivity

  • strengthen network resilience via seeder nodes

  • provide easy access to testnet coins

  • encourage community interaction through faucet & tipping tools


Plans for the Coming Weeks

Bots & Services

Umbrel Integration

Core & API Work

  • extend Grin++ and grin-rust-node APIs

  • submit a pull request

Grinffindor

  • Implement Website + feature

After completing these tasks, I’m open to new ideas and areas where I can contribute.

Feedback, testing, and suggestions are welcome :slightly_smiling_face:

15 Likes

omg this is brilliant

1 Like

Grinffindor … and Slythegrin

3 Likes

And Copyright :zany_face:

Nice idea :face_with_monocle:

2 Likes

Just to say what a great and useful initiative this is, and fun too. Coincidentally grinnode.live was down today (maybe still is), so the timing is indeed auspicious. Kudos, sir.

3 Likes

Grinffindor hahaha love it, great work Weische

2 Likes

I have deployed a runtime monitor with a dedicated VM on my server for the Grin testnet.

Currently, the setup consists of:

4x Grin Rust nodes
1x Grin++ node

In addition, one Grin Rust node and one Grin++ node continuously perform cyclic full syncs from scratch.

The runtime currently uses the latest main and staging branches together with the changes from
https://github.com/mimblewimble/grin/pull/3835

The runtime monitor also provides:

a runtime overview of all running nodes

continuous benchmark tracking

Current average full sync duration
~70–100 minutes per sync.

4 Likes

In case you need to have faster sync of chain_data, you may use the archived networks that i’m providing Grin-Node-Toolkit/extensions/grinmasternodes.json at main Ā· noobvie/Grin-Node-Toolkit Ā· GitHub

Usually if in US, 5-10 mins for full pruned sync, and around 20 mins for full archived sync via the on-the-fly extraction.

2 Likes