feat: add BisonFi override templates - #8
Open
bakasura980 wants to merge 37 commits into
Open
Conversation
…y slot Addresses two review comments. A persisted override was re-queued with fetch_before_use intact, so every following slot pulled the whole account from mainnet again: one RPC per slot per override, and any field the override does not write was reset to mainnet's value, discarding what local transactions had written to it. fetch_before_use is now cleared on the re-queue, but only after the write succeeds, so a failed apply still retries next slot with the fetch. The re-queue replaces a copy of itself already queued for that slot instead of bailing out, which keeps one entry per id. persist also gains the ts-bindings attribute its sibling fetch_before_use already had, and the regenerated OverrideInstance.ts exposes it - the field was previously absent from the TS SDK entirely.
…ge numbers support
…eChain/surfpool into feat/bisonfi-support
…y slot Addresses two review comments. A persisted override was re-queued with fetch_before_use intact, so every following slot pulled the whole account from mainnet again: one RPC per slot per override, and any field the override does not write was reset to mainnet's value, discarding what local transactions had written to it. fetch_before_use is now cleared on the re-queue, but only after the write succeeds, so a failed apply still retries next slot with the fetch. The re-queue replaces a copy of itself already queued for that slot instead of bailing out, which keeps one entry per id. persist also gains the ts-bindings attribute its sibling fetch_before_use already had, and the regenerated OverrideInstance.ts exposes it - the field was previously absent from the TS SDK entirely.
…ge numbers support
bakasura980
force-pushed
the
feat/kamino-protocol-support
branch
from
August 24, 2026 12:20
686cf07 to
f71abb8
Compare
…y slot Addresses two review comments. A persisted override was re-queued with fetch_before_use intact, so every following slot pulled the whole account from mainnet again: one RPC per slot per override, and any field the override does not write was reset to mainnet's value, discarding what local transactions had written to it. fetch_before_use is now cleared on the re-queue, but only after the write succeeds, so a failed apply still retries next slot with the fetch. The re-queue replaces a copy of itself already queued for that slot instead of bailing out, which keeps one entry per id. persist also gains the ts-bindings attribute its sibling fetch_before_use already had, and the regenerated OverrideInstance.ts exposes it - the field was previously absent from the TS SDK entirely.
…ge numbers support
bakasura980
force-pushed
the
feat/kamino-protocol-support
branch
from
August 25, 2026 11:23
c40c4ea to
794b8e8
Compare
Content was already applied in 26c7b5c, which lost its second parent to a reset and so left the branch looking unmerged - every later pull replayed the same conflicts. This records the parent; the tree is unchanged.
bakasura980
changed the base branch from
feat/kamino-protocol-support
to
feat/scenarios/protocols/kamino
August 26, 2026 09:45
bakasura980
changed the base branch from
feat/scenarios/protocols/kamino
to
feat/kamino-protocol-support
August 26, 2026 09:45
|
…LimeChain/surfpool into feat/kamino-protocol-support
bakasura980
changed the base branch from
feat/kamino-protocol-support
to
feat/scenarios/protocols/kamino
August 26, 2026 09:52
The Kamino PR was squash-merged into the base as 272e238, which has no ancestry link to the feat/kamino-protocol-support history already in this branch - so every merge re-derived the same six conflicts from two unrelated lineages. 272e238's tree is byte-identical to the kamino tip merged in d243443, so this records the parent and leaves the tree alone.
Tests couldn’t run because Rustup attempted to write outside the permitted workspace. No other actionable issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BisonFi publishes no IDL and is not an Anchor program, so this adds a raw byte-layout write path guarded by account size and magic, plus four templates on it: price, depth, spread and freshness.
Also introduces optional IDLs on templates, so a program without one no longer needs a reconstructed IDL in the repo.
Greptile Summary
The PR adds IDL-free, guarded raw-byte account overrides and four BisonFi scenario templates.
Confidence Score: 5/5
The PR appears safe to merge because no blocking failure remains within the eligible follow-up scope.
No blocking failure remains.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart LR S[Scenario override] --> T[Resolve template and account] T --> G{Raw layout present?} G -->|Yes| V[Validate account size and magic/version] V --> E[Encode supplied values] E --> W[Write bytes at declared offsets] G -->|No| I[Resolve owner IDL] I --> D[Decode and update fields] D --> WReviews (9): Last reviewed commit: "Include the workflow" | Re-trigger Greptile
Context used (3)