feat: persist caller-managed chain slot in accountsdb - #170
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: magicblock-labs/magicblock-engine/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough
Priority: ⬇️ Low Change: Feature Merge Risk: ⚪ Minimal · up to The caller-managed chain slot is independent of execution progress and checksums and persists through existing flush and snapshot operations. No actionable merge-blocking risk was identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What changed
Callers can now retain an external chain slot in AccountsDB through
accounts().chain_slot()andaccounts().set_chain_slot(slot), independently of local execution progress.Closes #169
Impact
The slot starts at zero and accepts rewinds. Updates don't flush on their own; existing sync and snapshot operations persist the metadata. The slot is excluded from execution checksums.