20th Nov 2026
5 min read

ARK Development Report - November 20, 2026

Welcome to this week’s Weekly Development Report, highlighting continued progress across the ecosystem, with a focus on security, reliability, and keeping our infrastructure and applications up to date. This week, Mainsail received further improvements to API security, IP handling, and transaction submission rate limiting, alongside fixes to webhook validation. ARK Scan also saw updates to supply display, PHP compatibility, and dependencies, while infrastructure maintenance continued with PHP upgrades, server kernel updates, and hardware improvements.

Development Activity Summary (November 13 – November 20, 2026)

Below is a breakdown of the total number of merged commits and contributing authors by project, highlighting development activity from November 13, 2026, to November 20, 2026.

Project Commits Authors
ARK Connect 0 0
ARK Scan 22 2
ARK SDKs & Docs 0 0
ARK Vault 0 0
Mainsail 183 4

In total, 205 commits were merged across all projects this week. As always, commit counts fluctuate with sprint focus and task complexity.

ARK Scan Weekly Report

This week’s ARK Scan work focused on correcting supply display, addressing PHP deprecation warnings, and updating dependencies across the Mainsail branch.

The total supply highlight was adjusted to round values down to the nearest whole number. This change was prompted by fractional supply values appearing on the devnet and was applied to both the main and Mainsail development branches.

A dependency constraint on react/promise was also removed to allow the package to move to version 3. This resolves a deprecation warning caused by outdated PHP syntax, which appeared when running certain explorer commands on newer PHP versions. The change was applied to both branches.

Further dependency updates were made to the Mainsail branch to improve compatibility with PHP 8.5 and bring the application in line with the latest available packages. Some major updates remain blocked by existing dependency requirements and will be handled separately, with the Foundation and Crypto packages being addressed as prerequisites for further upgrades.

Next week, we’ll continue updating the Mainsail branch dependencies, focusing on the remaining Foundation and Crypto upgrades and resolving any compatibility issues they introduce. We’ll also continue internal testing and address any issues identified across the explorer branches.

Mainsail Weekly Report

This week’s Mainsail work focused on strengthening API security and request handling, introducing transaction submission rate limits, and fixing webhook condition validation.

The api-common package received several improvements to client IP handling. The handling of X-Forwarded-For headers was updated to use the latest forwarded address and verify that it is a valid IP. Client IP addresses and forwarded addresses are now canonicalized when proxy trust is enabled. Rate limiting for IPv6 clients was also adjusted to group addresses by their /64 network prefix, preventing clients from bypassing limits by using different addresses within the same network range.

A new costRateLimit plugin was introduced for the transaction-pool API to control transaction submission based on the number of transactions rather than just the number of requests. The POST /transactions endpoint now uses a separate budget of 600 transaction points per 60 seconds per IP by default, with each submitted transaction consuming one point. Batches that exceed the remaining budget are rejected with a 429 response and a Retry-After header, without partially consuming the remaining allowance. Rate-limit information is included in dedicated X-TransactionRateLimit-* headers, while the existing X-RateLimit-* headers continue to report request-based limits. Transaction submissions still count towards the existing request limit, and read endpoints remain unaffected. Additionally, a peer returning a 429 response is no longer treated as a failed gossip post. The new limits can be configured or disabled through dedicated environment variables.

Webhook condition validation was also corrected. Previously, the schema allowed arbitrary condition names instead of restricting them to supported values, which could cause invalid conditions to be stored. The notBetween condition was also registered under a different name than the one used during lookup, preventing matching webhooks from firing. In addition, condition names inherited from Object.prototype, such as constructor, could incorrectly match every event. These issues have been addressed by tightening validation and correcting condition matching.

Finally, CI workflows were fixed to check out pull requests using their head commit SHA. This allows workflows to run correctly for pull requests originating from forked repositories.

Next week, we’ll continue the P2P server migration by replacing Hapi with a custom server. The work will focus on completing the core server implementation, integrating the existing networking functionality, and addressing connection handling, request processing, and compatibility issues uncovered during testing. We’ll also continue refining the P2P components to ensure the transition does not affect network stability or communication between peers.

Infrastructure & Security Updates

Following last week’s update, we’ve continued our work on keeping our infrastructure secure and up to date. Software maintenance is never a one-time effort, and the steady stream of new patch releases makes it important to stay on top of things.

Over the past week we applied the latest PHP patch releases across our projects. These smaller updates often contain important security fixes and bug fixes, and applying them promptly keeps the gap between a fix becoming available and it running in production as small as possible. We also made further adjustments to bring all of our projects up to PHP 8.5. With PHP 8.6 newly released, having every project on the same, current version gives us a consistent baseline and makes the upcoming move to PHP 8.6 smaller and more predictable.

On the server side, we installed the latest kernel patches and rebooted our servers so the updates are fully in effect. Kernel updates only take effect after a restart, so we scheduled these reboots carefully to keep any impact on our users to a minimum. We also upgraded the servers behind ARK Scan, including the servers used for search queries, to move them onto more recent hardware.

As before, security and performance remain ongoing priorities. We’ll keep monitoring new releases and vulnerabilities, and continue to regularly update both our projects and our servers.

Feedback & Feature Requests

If you are using our open-source products and would like to provide feedback or request a feature, please feel free to contact us via the contact pages for the specific product you are using or open an issue on GitHub.

Quick access links to GitHub issues pages:

Follow Us on X

Follow us on X and keep an eye on the blog to stay up to date with everything we ship. We publish a development report every week so you can follow along as the ecosystem grows.

Share:

Get in Touch!

Whether you want to learn more about ARK Ecosystem, want to apply for developer bounty, become our partner or just want to say Hello, get in touch and we will get back to you.



An Ecosystem of Developers

Join us on our journey to create the future of Web3.