Skip to content

Source Verification RFP Submission#9

Closed
chadoh wants to merge 5 commits into
mainfrom
feat/rfps-source-verification
Closed

Source Verification RFP Submission#9
chadoh wants to merge 5 commits into
mainfrom
feat/rfps-source-verification

Conversation

@chadoh

@chadoh chadoh commented Jun 4, 2026

Copy link
Copy Markdown
Member

@chadoh chadoh force-pushed the feat/rfps-source-verification branch from 694512b to 881292f Compare June 4, 2026 16:16
@chadoh chadoh force-pushed the feat/rfps-source-verification branch from 881292f to 05b7dac Compare June 4, 2026 16:22

@elizabethengelman elizabethengelman left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just adding a few thoughts as I'm reviewing for the first time!

Comment thread rfps/source-verification.md Outdated
> - https://github.com/FrankSzendzielarz/SorobanRPCSDK
> => Good one - https://drive.google.com/file/d/167c6KVuyvRo7haInUahDfeMRxkO8gya3/view"

## Verifier added to Registry's allowlist

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the balance of these diagrams which are more focused on finer grain details vs the ones in #11 which give a good overview of the system as a whole. I think that both are important & helpful to the reviewer.

I'll continue noodling on it, and see if I can come up with any other questions that another finer-grain diagram could help answer.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I like the idea of the finer-grain diagrams to explain seams in the system. One idea that comes to mind: a diagram that shows how verification run triggers work, specifically for back-verification.

`rfps/source-verification` is now a directory with:

- README.md: the copy-pasted source of the RFP document itself
- full-application.md: our work-in-progress responses for the full form
  submission
- technical-architecture-highlevel.md: copy-pasted from #11

Co-authored-by: Ethan Frey <ethanfrey@noreply.github.com>
@chadoh chadoh force-pushed the feat/rfps-source-verification branch from d29854e to d2f2639 Compare June 11, 2026 20:18
@ethanfrey ethanfrey mentioned this pull request Jun 12, 2026
@chadoh

chadoh commented Jun 12, 2026

Copy link
Copy Markdown
Member Author

Thanks @elizabethengelman! Glad you commented on those original diagrams so we can find them as we finalize the design in Milestone 1. I think for the RFP application it's fine (preferred, even) to have it be a little more high-level.

Closing this in favor of the equivalent PR in the new RFP repo (stellar-registry/rfps#1) — we have a stellar-registry org now, why not use it!

@chadoh chadoh closed this Jun 12, 2026
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.

3 participants