Skip to content

Research: identify the best-evidenced get_safety consumer - #264

Open
GOE001 wants to merge 7 commits into
use-assay:mainfrom
GOE001:docs/issue-153-consumer-research
Open

GOE001 wants to merge 7 commits into
use-assay:mainfrom
GOE001:docs/issue-153-consumer-research

Conversation

@GOE001

@GOE001 GOE001 commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

closed #153

@drips-wave

drips-wave Bot commented Sep 30, 2026

Copy link
Copy Markdown

@GOE001 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@mergekeeper

mergekeeper Bot commented Sep 30, 2026

Copy link
Copy Markdown

MergeKeeper review

Scope: in scope for linked issue #153.
Verdict: clean

The PR successfully adds a comprehensive research deliverable in docs/consumer-integration-research.md comparing three candidate consumers (Soroswap allowlist, DeFindex vault, and Blend lending pool) using real deployed protocol references, evaluating their needs against Assay's interface, and providing a reasoned recommendation.

Reviewed commit: f9d865a205e0d1f88a1fc2ec3cc088c43dcedcd1.
CI and merge eligibility are checked separately.

@Fury03
Fury03 self-requested a review October 6, 2026 04:54
@mergekeeper

mergekeeper Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

MergeKeeper merge status

Status: blocked
PR state: open
Mergeability: mergeable
Checked commit: f9d865a205e0d1f88a1fc2ec3cc088c43dcedcd1.

Reason: One or more required CI checks failed.

Failing checks:

Next steps:

  1. Open the failing check details above and fix the reported error.
  2. Run the same checks locally where possible.
  3. Commit and push the fix.
  4. MergeKeeper will automatically re-review the updated PR.

AKAEMM668 and others added 3 commits October 22, 2026 10:28
A run of merge commits on main resolved conflicts by keeping both sides
instead of the intended union. That duplicated type and function
declarations (mechanics, api, scan, cmd/assay), dropped shared helpers
(write_attestation was still called but gone from horizon and
stellarexpert and sep1), reverted a few type changes (CanonicalTime,
Answer[T], Options), and left several test files with two copies of the
same helper. `go build`, `go vet`, `go test`, `cargo fmt`,
`cargo clippy` and `cargo test` all failed as a result, so every open
PR inherited a red build.

Reconstruct the intended unions, restore the dropped definitions, align
the tests with the behaviors the newer branches added (blocked-lookup
skip is undetermined, evidence timestamps are canonical and carry a
requested URL, reputation is cached), and regenerate the Soroban test
snapshots for the pinned toolchain and soroban-sdk 28.

This is deliberately a scoped main-only repair: the feature PRs keep
their own diffs, and land green once this is on main.
@mergekeeper

mergekeeper Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Needs review

Linked to #153, but the diff does not match the issue scope.

This PR introduces research on get_safety consumer integration as requested by issue #153, but it also includes unrelated workflow edits and domain check logic changes in internal/mechanics/check_domain.go that belong to separate tasks.

Reviewed commit: 114eeac57286efa87276b8f5a31370161baca370.

GOE001 and others added 3 commits October 22, 2026 11:50
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Research: which consumer integration is best evidenced first

1 participant