Mandragora | Validator Introduction

Validators Introductions
1

Overview

Validator Name: Mandragora
Operator ID(s):

  • storyvaloper1c22aqt476xymds86utw0lew02sxtz2ky4ttvwa [locked]

Website: https://mandragora.io
Twitter: https://x.com/mandragora_spem

Infrastructure

Type: Hybrid (Bare metal)
Regions: North America (Canada), Europe (France)
Security Certs: ISO 27001

Experience

Operating Since: 2018
Networks Validated: +40 since 2018, including both testnets and mainnets, and winners/top performers in incentivized testnets like Story (within top 5), Namada (top 1), Evmos (top 10), UX Chain (top 3, formerly Umee) and Sentinel (tier 2 winners).
Story Mainnet Uptime: 99.99%
Story Testnet (Iliad/Odyssey): Yes, uptime 99.99% on both testnets (within the top 5 performers at Odyssey).

Story Ecosystem Contributions

  • How has your team contributed to the ecosystem beyond validation?

  1. Provided critical infrastructure since early testnets. RPC and WSS endpoints (CometBFT and EVM), REST API endpoint, peer and seed nodes, Geth node, Addrbook, pruned and archive snapshots, and more.

  2. Leading the Spanish-speaking community on Discord, X, and Telegram by posting regular updates and relevant documentation, as well as doing X Spaces with Story ecosystem projects like Metapool to let Spanish-speaking people further know and engage not only about and with Story itself, but also with interesting use-cases in the Story’s ecosystem.

  3. We have provided technical support non-stop to other validators since the early testnets, this way making us and other folks like Coha05 the main baseline to take into account to evaluate other validators once Odyssey testnet ended and we made the final transition to mainnet.

  4. We have been within the top 5 performers at Odyssey testnet as well as on early testnets.

  5. We have provided relevant feedback to the team and tools on early stages like Lost my validator to be able to retrieve the validator private key just by using the validator account private key - it’s now hardcoded in the Story’s client binary.

  6. We have participated and engaged with proposals made by other validators, providing feedback and making a formed decision to move forward, such as the 1024 IP staking minimum reduction proposal in the Story’s forum.

  • Other meaningful contributions

We have reported various issues and proposed improvements during testnets and mainnet:

  1. This GitHub issue led to the unjail command addition in the v0.11.0 release:
    • https://github.com/piplabs/story/issues/80

  2. This GitHub issue was closed as finally proposed improvements for some items weren’t planned:
    • https://github.com/piplabs/story/issues/90

  3. This GitHub issue is still open nowadays:
    • https://github.com/piplabs/story/issues/91

  4. This GitHub issue has been finally addressed with the v1.2.0 release:
    • https://github.com/piplabs/story/issues/533

Why Delegate to Us?

Our main goal in supporting Story is to join forces with other organizations on a journey toward a world where intellectual property is better suited to our times. We plan to continue providing support in this regard, whether by providing necessary infrastructure services, collaborating with ecosystem projects for various purposes, or promoting events to spread the word about the project.

Links

  • https://staking.story.foundation/validators/storyvaloper1c22aqt476xymds86utw0lew02sxtz2ky4ttvwa
  • https://story.explorers.guru/validator/storyvaloper1c22aqt476xymds86utw0lew02sxtz2ky4ttvwa
2 Likes