Stacks Integration – Project Status Report 09/09/2025
Current Status
- Stacks contracts are complete.
- Current state is similar to Near: SDK and solver implementation are still pending.
- Work has been in the pipeline for a long time, but delays are due to complexity and prioritization of other deployments, updates, and audit fixes.
Challenges
- Stacks and Near use different tech stacks, making each component unique and more complex to implement.
- Both tech stacks require separate audits for every part of the build.
- This uniqueness and complexity cause slower progress compared to EVM-based stacks.
- EVM implementations are easier due to existing audits and stronger external interest.
Timeline
| Item |
Status |
Target Completion |
| Contracts |
Completed |
N/A |
| SDK implementation |
Pending |
Late October (expected) |
| Solver implementation |
Pending |
TBD |
| Audit phase (post-build) |
Required |
Post-SDK & solver completion |
Risks
- Complexity of non-EVM tech stacks increases development and audit times.
- Priority shifts to other key deployments may further delay timelines.
- Solver implementation is still undefined in terms of exact scheduling.
Next Steps
- Begin SDK implementation in late October.
- Follow with solver implementation work once resources are available.
- Prepare for external audits after SDK and solver are completed.