Skip to content

Conversation

@ehanoc
Copy link

@ehanoc ehanoc commented Sep 4, 2025

Description

Submitting proposal for Algorand's x402 support.

The proposal takes advantages of Algorand's Native Atomic Transaction Groups, Instant finality and the ability to fee pooling to comply with the requirements of x402 protocol.

Future

Upon review and if accepted, we are committed to submit the actual implementation

  • Algorand Foundation

@cb-heimdall
Copy link

cb-heimdall commented Sep 4, 2025

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

@vercel
Copy link

vercel bot commented Sep 4, 2025

@ehanoc is attempting to deploy a commit to the Coinbase Team on Vercel.

A member of the Team first needs to authorize it.

@emg110 emg110 mentioned this pull request Nov 5, 2025
3 tasks
@CarsonRoscoe
Copy link
Contributor

Hey all,

With #705 nearly complete, we encourage you to rebase off of the development-v2 branch. Adding new protocol families such as Algorand will be much easier in the new version, and that branch will become the new main shortly

@ehanoc
Copy link
Author

ehanoc commented Dec 5, 2025

Hey all,

With #705 nearly complete, we encourage you to rebase off of the development-v2 branch. Adding new protocol families such as Algorand will be much easier in the new version, and that branch will become the new main shortly

Hey @CarsonRoscoe , thanks for getting back to us.

I had a look at that branch and it seems to be touching mostly implementations, we are only submitting the specification here as suggested by the CONTRIBUTING.md guide. We recommend first proposing a scheme by opening a PR with a proposed spec into specs/, discussing the architecture and purpose in that PR, then once the PR is merged, moving on to implementation. . It's a single file atm.

We are ready to submit an implementation if we can get a review on this and approval first. Would that be possible?

@phdargen phdargen mentioned this pull request Jan 2, 2026
3 tasks
Copy link

@edcalderon edcalderon left a comment

Choose a reason for hiding this comment

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

LGTM

@ehanoc
Copy link
Author

ehanoc commented Jan 8, 2026

Hey @CarsonRoscoe , any chance we could have someone have a look at this?

Copy link
Contributor

@CarsonRoscoe CarsonRoscoe left a comment

Choose a reason for hiding this comment

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

Approach seems logical. Most feedback is about upgrading this to target version 2

Copy link
Contributor

@CarsonRoscoe CarsonRoscoe left a comment

Choose a reason for hiding this comment

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

After reviewing, virtually all my requested changes are just about targetting v2 over v1.

The meat of the proposal is logical and I am content with, once the v2 updates are in we'll be good to merge

@github-actions github-actions bot added the specs Spec changes or additions label Jan 13, 2026
Signed-off-by: ehanoc <bruno.martins@algorand.foundation>

Co-authored-by: cusma <cosimo.bassi@algorand.foundation>
Co-authored-by: tasosbit <tasos.bitsios@algorand.foundation>
Co-authored-by: nullun <steve.ferrigno@algorand.foundation>
Co-authored-by: tasosbit <tasos.bitsios@algorand.foundation>
Co-authored-by: emg110 <emg110@gmail.com>
@ehanoc
Copy link
Author

ehanoc commented Jan 13, 2026

After reviewing, virtually all my requested changes are just about targetting v2 over v1.

The meat of the proposal is logical and I am content with, once the v2 updates are in we'll be good to merge

Thanks so much for reviewing @CarsonRoscoe . I've just made the updates, rebased and pushed.

Let me know if there's anything else!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

specs Spec changes or additions

Development

Successfully merging this pull request may close these issues.

4 participants