Issues

[High] Author a repo-specific `CODE_OF_CONDUCT.md` addressing this project's financial-stakes-specific dynamics

stellar-vortex-protocol/vortex-contracts#584 · opened

on Oct 17, 2026

[High] `governor`, `timelock`, and `treasury_streams` each write persistent storage without ever calling `extend_ttl` — a third, fourth, and fifth instance of the same gap already filed for `reputation_badge` (#119)

stellar-vortex-protocol/vortex-contracts#583 · opened

on Oct 17, 2026

[High] `governor`'s vote-tally and deadline arithmetic uses raw, unchecked operators instead of this codebase's established `checked_`/`saturating_` convention

stellar-vortex-protocol/vortex-contracts#582 · opened

on Oct 17, 2026

[High] `treasury_streams::initialize` has the identical missing-authorization bug as `governor` (#120)

stellar-vortex-protocol/vortex-contracts#581 · opened

on Oct 17, 2026

[High] `governor::initialize` has no authorization check at all — anyone can claim and configure a freshly-deployed governor

stellar-vortex-protocol/vortex-contracts#580 · opened

on Oct 17, 2026

[High] `reputation_badge` never bumps TTL on any storage entry — badges risk archival eviction

stellar-vortex-protocol/vortex-contracts#579 · opened

on Oct 17, 2026

[High] `backstop_vault.deposit()` violates checks-effects-interactions — the token transfer happens before the share/asset storage writes

stellar-vortex-protocol/vortex-contracts#578 · opened

on Oct 17, 2026

[High] Every CI job — including for crates that actually compile — fails at the exact same step, for the exact same single root cause: issue #1's broken workspace `Cargo.toml`

stellar-vortex-protocol/vortex-contracts#577 · opened

on Oct 17, 2026

[High] CI on `main` has been red for approximately 11 weeks (~118 run attempts, only the earliest 10 ever passed), tracing back to a trivial formatting failure that was never fixed

stellar-vortex-protocol/vortex-contracts#576 · opened

on Oct 17, 2026

[High] `vortex-common`'s `require_admin` uses `IntoVal<Env>` with the wrong number of generic arguments — the crate does not compile, independent of being unused (#44)

stellar-vortex-protocol/vortex-contracts#575 · opened

on Oct 17, 2026

[High] `intent_periphery` is missing a `use soroban_sdk::IntoVal;` import — four proxy methods fail to compile

stellar-vortex-protocol/vortex-contracts#574 · opened

on Oct 17, 2026

[High] `treasury_streams`'s `Cargo.toml` never declares `soroban-sdk` as a dependency — the crate cannot compile under any configuration

stellar-vortex-protocol/vortex-contracts#573 · opened

on Oct 17, 2026

[High] `timelock` does not compile — `hash_operation` is defined twice, and the real implementation underneath has further, independent type errors

stellar-vortex-protocol/vortex-contracts#572 · opened

on Oct 17, 2026

[High] `governor` does not compile — `proposal` and `voting_power` are each defined twice in the same `impl` block

stellar-vortex-protocol/vortex-contracts#571 · opened

on Oct 17, 2026

[High] `solver_registry` does not compile at all — its entire trailing block of TTL helper functions is duplicated outside the `impl` block, causing a syntax error

stellar-vortex-protocol/vortex-contracts#570 · opened

on Oct 17, 2026

[High] `Error::BatchSizeExceeded` (#239) was never added — batch entrypoints still reuse `Error::ZeroAmount` with a "no dedicated error" comment

stellar-vortex-protocol/vortex-contracts#569 · opened

on Oct 17, 2026

[High] `proof_registry`'s contract-upgrade mechanism (#240) was never implemented

stellar-vortex-protocol/vortex-contracts#568 · opened

on Oct 17, 2026

[High] 31 `Error` variant names, 17 `DataKey` variant names, and at least 3 struct fields are each declared twice in `intent_settlement/src/lib.rs` — plus ~38 discriminant values independently reused by unrelated variants — a third, independent instance of the same unmerged-duplication pattern as #98

stellar-vortex-protocol/vortex-contracts#567 · opened

on Oct 17, 2026

[High] `soroban-sdk` was never actually upgraded from 21.0.0 — issue #377's closing commit added a migration-notes doc, not a dependency bump

stellar-vortex-protocol/vortex-contracts#566 · opened

on Oct 17, 2026

[High] Client-computable, timestamp-free intent ids (#354) were designed in a doc but never implemented — `compute_intent_id` still requires a timestamp

stellar-vortex-protocol/vortex-contracts#565 · opened

on Oct 17, 2026

[High] Operator session keys, delegated staking, sealed-bid auctions, and best-effort batch variants (#363–#366) are inert type scaffolding with zero functional implementation

stellar-vortex-protocol/vortex-contracts#564 · opened

on Oct 17, 2026

[High] Add a fuzzing harness for `proof_registry`'s manual byte-level parsers — closed issue #207 was closed by an unrelated commit; no harness exists

stellar-vortex-protocol/vortex-contracts#563 · opened

on Oct 17, 2026

[High] Issue #342 was closed by a commit whose own message admits the fix was deferred, not completed — a direct, documented instance of fake issue closure

stellar-vortex-protocol/vortex-contracts#562 · opened

on Oct 17, 2026

[High] Implement on-chain rate-of-change guardrails for protocol parameters — closed issue #404 delivered a one-line README bullet, not code

stellar-vortex-protocol/vortex-contracts#561 · opened

on Oct 17, 2026

[High] Implement the interface-version handshake between cooperating contracts — closed issue #400 delivered a one-line README bullet, not code

stellar-vortex-protocol/vortex-contracts#560 · opened

on Oct 17, 2026

Navigation Menu

Repository navigation

Issues

[High] Author a repo-specific `CODE_OF_CONDUCT.md` addressing this project's financial-stakes-specific dynamics

[High] `governor`, `timelock`, and `treasury_streams` each write persistent storage without ever calling `extend_ttl` — a third, fourth, and fifth instance of the same gap already filed for `reputation_badge` (#119)

[High] `governor`'s vote-tally and deadline arithmetic uses raw, unchecked operators instead of this codebase's established `checked_`/`saturating_` convention

[High] `treasury_streams::initialize` has the identical missing-authorization bug as `governor` (#120)

[High] `governor::initialize` has no authorization check at all — anyone can claim and configure a freshly-deployed governor

[High] `reputation_badge` never bumps TTL on any storage entry — badges risk archival eviction

[High] `backstop_vault.deposit()` violates checks-effects-interactions — the token transfer happens before the share/asset storage writes

[High] Every CI job — including for crates that actually compile — fails at the exact same step, for the exact same single root cause: issue #1's broken workspace `Cargo.toml`

[High] CI on `main` has been red for approximately 11 weeks (~118 run attempts, only the earliest 10 ever passed), tracing back to a trivial formatting failure that was never fixed

[High] `vortex-common`'s `require_admin` uses `IntoVal<Env>` with the wrong number of generic arguments — the crate does not compile, independent of being unused (#44)

[High] `intent_periphery` is missing a `use soroban_sdk::IntoVal;` import — four proxy methods fail to compile

[High] `treasury_streams`'s `Cargo.toml` never declares `soroban-sdk` as a dependency — the crate cannot compile under any configuration

[High] `timelock` does not compile — `hash_operation` is defined twice, and the real implementation underneath has further, independent type errors

[High] `governor` does not compile — `proposal` and `voting_power` are each defined twice in the same `impl` block

[High] `solver_registry` does not compile at all — its entire trailing block of TTL helper functions is duplicated outside the `impl` block, causing a syntax error

[High] `Error::BatchSizeExceeded` (#239) was never added — batch entrypoints still reuse `Error::ZeroAmount` with a "no dedicated error" comment

[High] `proof_registry`'s contract-upgrade mechanism (#240) was never implemented

[High] `soroban-sdk` was never actually upgraded from 21.0.0 — issue #377's closing commit added a migration-notes doc, not a dependency bump

[High] Client-computable, timestamp-free intent ids (#354) were designed in a doc but never implemented — `compute_intent_id` still requires a timestamp

[High] Operator session keys, delegated staking, sealed-bid auctions, and best-effort batch variants (#363–#366) are inert type scaffolding with zero functional implementation

[High] Add a fuzzing harness for `proof_registry`'s manual byte-level parsers — closed issue #207 was closed by an unrelated commit; no harness exists

[High] Issue #342 was closed by a commit whose own message admits the fix was deferred, not completed — a direct, documented instance of fake issue closure

[High] Implement on-chain rate-of-change guardrails for protocol parameters — closed issue #404 delivered a one-line README bullet, not code

[High] Implement the interface-version handshake between cooperating contracts — closed issue #400 delivered a one-line README bullet, not code