Team: Wave
Wave is a team of 3 engineers structured around a DevOps and a BackEnd Engineer and a tech lead. We are CISCO certificated, with a long experience in infra management, SIEM implementation and Service Oriented Architecture.
Security
We are sticking to the best practice with Sentries → relay nodes → validator → HSM.
For signing, a dedicated SGX enclave uses the tendermint key management system maintained by Iqlusion.
Reliability
Our main infra is deployed in OVH, our backup infra is using Equinix.
We are using Ansible as configuration management tool and PAgerduty for on-call rotation.
Elasticsearch and kibana are used for logs analysis. Prometheus analytics, Prometheus node exporter, grafana and others script for DDOS mitigation and reporting tools.
We are 24/7 available.
We are working with dedicated servers across the globe for better support and backup, we believe that the infrastructure for all the projects we are supporting should be very secure, easy to maintain and have almost perfect uptime.
We monitor with special dedicated tools all the health features of our validator nodes, consensus participation and timely updates.
Communication
Mail: contact AT 0xwave DOT com
Team contact: aorfevrebr DOT gmail.com, Prev CTO for daomaker DOT com
Security contact: wave0x AT proton DOT me
Discord: @Waves#9228
Telegram: @WaveWays
Entity name and location: Wave is based in Paris, France.
What kind of hardware do you run?
Infrastructure location: France and US.
Dedicated bare metal hosted in the EU tiers 4 data centers.
Technical make-up of team:
Years of experience: Over 10 years in DevOps, over 3 in blockchain infra.
What other networks are you running validators for?
Solana - H1kyn75BFTXr8QRmToRRvuEEmYan5n6M5APyfhMLau3b
Quicksilver - quickvaloper1xv3c6673a6plcaaz8xshqmnumnffd4xmd5gfyp
Agoric - agoricvaloper1m47vds3c4qj47hz57mumwc90ep7jcaxg9ck8xv
Tgrade - tgrade1efp3hmnslju2pn8g2qukp5k5xs028rhppznk67
Lum - lumvaloper1gz3qwx785rgcdzrzf6uhjl9nwjvuh83krvcqp5
Avalanche - NodeID-JyCGTjJaPELmLZdtn5J1HwKHZzki6Ae9W
Based on your participation in any previous testnets, mainnets, are there any best practices to be aware of? What are some things that made previous testnets, mainnet launches successful and/or things to avoid that have gone poorly?
- Had one of the fastest growing node @ fantom network mainnet launch because of our community based growth strategies. The node gathered rapidly over 150M $FTM in delegation.
- Having to few or too many validators in the set, few may make your network faster but leaves out a lot of room for downfall due to the fact that some issues which occur may stress to much the set and the chain will be halted, too many and proposals and upgrades will not go as smooth as you would want especially if you need a quick fix ASAP
- We developed various open source snapshot strategies.We took part in the AVAX testnet and we consider that its success is also linked to our efforts. Our scripts has been used by 500+ node during testnet
Do you have a validator voting framework and process?
Yes
Are you planning to play any additional roles in the dYdX ecosystem (e.g. market maker, trader, indexer, front-end, other)?
In addition to the infra support, we are active traders and are working on on-chain trading bots as telegram reporting/alerting bots.
Are there other products or services you want to highlight that could be relevant for dYdX?
We are working on on-chain scalping and arbitrage bots.
Any notable contributions in other ecosystems that you would like to highlight for the community?
We do participate in the testnet and mainnet of every chain we are validating. We provide RPC endpoints and relayers services (i.e.
Our [Osmosis <> Agoric] Mintscan relayer has already successfully
relayed more than [10 000 txs] Mintscan
Osmosis Relayer Operator address for channel-320 : osmo1w6hxjh6ymq3fnx03y664qmzrlud29jyzyzwsk5