Ironforge

We are now up and running.Please sign in at ironforge.sanctum.so x.com/IronforgeCloud…

Ironforge is moving from ironforge.cloud to ironforge.sanctum.so. The transition will begin at 4:30 pm SGT, and our website will be down for a few minutes as the process completes. Our underlying service will NOT be impacted. Only the frontend website/dashboard will be affected. All users will be signed out of the website and will need to log back in once the website is live again.

At @triton_one, we're open-source advocates who enjoy contributing to other teams' work in addition to our own. Together with @ABKLABS, we've been pushing hard on the @metaplex Digital Asset Standard API project. We've got the DAS API in a great place, and I'd like to share a status update. For background, over three years ago, I was contacted by the Metaplex team and my friend @_austbot about supporting their ambitious API project. We naively said "Yes," not realizing what we had just committed to. 😉 In the early days, our role was limited to operational support -- Austin would prepare a new release, and we would deploy it to give feedback. There was a lot of glass chewing in those days. Many times, the feedback was, "This doesn't work," but Austin persisted until the project was ready for the next steps. After the DAS API was deployed into production, it became apparent that it required additional developer love, so our team stepped up to contribute code and pull requests to the Metaplex repository. @linuskendall, @espiKnwldgBmbs, @_fanatid, and others all made significant contributions. After three years, we have DAS API supporting a notable amount of our Triton production RPC traffic. The DAS API isn't just for NFTs; it also supports fungible tokens in a format compatible with the @solana JSON RPC API token methods. The performance is fantastic -- we've got heavy queries, such as getTokenLargestAccounts (gTLA), running in under 100 milliseconds! DAS API is an integral part of our RPC 2.0 stack. Did I mention it is open-source? Notably, we've removed the dependency of running a dedicated RPC node to feed the index. By using our widely supported Yellowstone gRPC interface, any team can run their own DAS API instance by connecting to any of the RPC vendors that offer gRPC. Running an index in the cloud is also feasible for many apps. It's worth repeating -- "any team can run their own DAS API instance!" I mention that because Solana applications are becoming increasingly feature-rich, to the point where they've outgrown the standard JSON RPC API. Sophisticated apps often require custom indexes, and the Metaplex DAS API can serve as a great starting point. Developers can customize the code with the confidence that it will perform well in production. Triton has contributed a significant amount of time and money to DAS API without receiving grants or other financial compensation. In return, I hope the ecosystem will benefit from our contribution by building better apps. Finally, we're always happy to work with other teams on our Yellowstone open-source projects. For example, we have almost thirty contributors to our Dragon's Mouth gRPC Geyser plugin. Thanks to everyone who helped! Here are links to the mentioned repositories: Metaplex DAS API: github.com/metaplex-found… Triton Fork of DAS API (we contribute all changes upstream): github.com/rpcpool/digita… Yellowstone gRPC Contributors: github.com/rpcpool/yellow…

Introducing Alerts 🚀 Monitor your RPC endpoints, load balancer, and transactions in real-time. Receive instant notifications via Slack, PagerDuty, and more when something needs attention to respond to incidents faster 📈. Now in public beta ✨

I'm hiring 2 Developers, - Rust (needed) - Hardworking and a great teammate (needed) - Solana (nice to have) - Experience: Mid to Senior

🆕 Slot Drift support in the Load Balancer

🆕 Changelog is not out yet, but a very important feature has just been added to the @IronforgeCloud RPC Load Balancer. Now, if an endpoint falls behind X slot from the tip of the network, you can instruct the Load Balancer to deprioritize that endpoint or to ignore it.

Behind the scenes at $GNME: Our devs are working with @heliuslabs & @AlchemyPlatform for robust infrastructure, while @IronforgeCloud ensures smooth RPCs. Building reliable mining experiences on Solana, block by block 🛠️

Shoutout to @IronforgeCloud and staked RPC connections from @triton_one & @heliuslabs! Landing transactions on Solana and making new Solana integrators happy can be so easy.

🔜 @IronforgeCloud will allow you to route traffic away from RPC endpoints that are failing behind the tip of the network.

@solana just started

job’s not finished btw

🆕 Changelog: January 13, 2025 Introducing comprehensive audit logs, header forwarding, and enhanced WAF rules. Track all organization actions, forward HTTP headers using the X-Ironforge-Proxy-* prefix, and benefit from improved security with robust property-based firewall rules.

If you're using Ironforge and need to forward some HTTP headers to your RPC requests, you can do it now by prefixing the header with `Ironforge-Proxy-<header-name>`. Documentation 👇

🎆 Happy New Year CT! Tired of abandoning your New Year's resolutions by February? 👀 Introducing reSOLution: Stake $SOL on your goals, get verified by friends, and earn rewards for achieving them. Personal growth meets DeFi on @Solana. stakeresolution.com

🆕 Today, we’re releasing a new load balancer algorithm option (weighted) for better traffic control, a new logs experience, and improved p99 latency. We’re also working on self-hosted load balancers and full-text log searches. Changelog link below 👇

At Vectis, we aim to deliver a stable and exceptional user experience by partnering with leading infrastructures on @Solana. Our service providers include: - @Heliuslabs: the leading RPC provider on Solana - @IronforgeCloud: experts in failover and load-balancing services By building with these strong partners, we ensure seamless operations and provide a trustworthy product for our users.

@Truffle_HQ @italoacasas 🩷

@italoacasas 🫶Thank you for your transparency and for Ironforge's speed in resolving this issue!

Please read.