Academy course x402 fundamentals #3303
Conversation
…tegrated in the future implementation demo
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…amentals Signed-off-by: federiconardelli7 <148543277+federiconardelli7@users.noreply.github.com>
content/academy/x402-payment-infrastructure/02-introduction/01-what-is-x402.mdx
Outdated
Show resolved
Hide resolved
content/academy/x402-payment-infrastructure/02-introduction/03-use-cases.mdx
Outdated
Show resolved
Hide resolved
content/academy/x402-payment-infrastructure/02-introduction/02-payment-problem.mdx
Show resolved
Hide resolved
…t important topics
…yment, x-payment-response. Improve readability in general
| - [Introduction to x402](/academy/x402-payment-infrastructure/02-introduction/01-what-is-x402) | ||
| - [Technical Architecture](/academy/x402-payment-infrastructure/03-technical-architecture/01-payment-flow) | ||
| - [x402 on Avalanche](/academy/x402-payment-infrastructure/04-x402-on-avalanche/01-why-avalanche) | ||
| - [Implementation Guide](/academy/x402-payment-infrastructure/05-implementation/01-setup) |
There was a problem hiding this comment.
make sure to name the new folder in the next PR like this :)
There was a problem hiding this comment.
Perfect, I'll add the implementation folder when we have the SDK for starting the implementation guide.
| ### 1. Create Account | ||
| - Sign up for a service account with personal information | ||
| - Verify email addresses and set up passwords | ||
| - 5-15 minutes per service with high abandonment rates | ||
|
|
||
| ### 2. Add Payment Method | ||
| - Enter credit card details and complete bank verification | ||
| - Navigate complex payment forms | ||
| - 3-10 minutes with security and privacy concerns | ||
|
|
||
| ### 3. Complete KYC (Know Your Customer) | ||
| - Submit government-issued ID and proof of address | ||
| - Complete verification and wait for approval | ||
| - Hours to days with privacy concerns | ||
|
|
||
| ### 4. Buy Credits or Subscribe | ||
| - Purchase credits or subscribe to monthly plans before trying | ||
| - Commit to minimum purchases without knowing value | ||
| - Forces prepayment for uncertain utility | ||
|
|
||
| ### 5. Manage API Keys | ||
| - Generate, store, and rotate API keys securely | ||
| - Monitor for key compromise | ||
| - Ongoing maintenance and security risk |
There was a problem hiding this comment.
I would summarize just to 5 bullet points like:
1 - Creating acount: requires signing up, verifying email address and setting up password (eta 5-15 minutes)
2 - Add Payment methods: creditad card details, bank verificavtion (eta 3-10 minutes)
....
| ### Cannot Create Accounts | ||
| Most signup flows require human verification through CAPTCHA, email confirmation, or phone verification. AI agents cannot complete these human-centric verification processes, preventing them from even accessing services. | ||
|
|
||
| ### Cannot Complete KYC | ||
| Identity verification (Know Your Customer) is designed specifically for humans—requiring government-issued IDs, proof of address, and sometimes video verification. AI agents have no legal identity and cannot complete these requirements. | ||
|
|
||
| ### Cannot Handle Micropayments | ||
| Transaction fees make small payments economically impossible. When an AI agent needs to pay \$0.001 for a single API call, traditional payment fees of $0.30+ make the transaction infeasible. | ||
|
|
||
| ### Credential Management Risks | ||
| Storing API keys and payment credentials creates security vulnerabilities. AI agents would need to securely manage numerous credentials across services, creating attack vectors and compliance challenges. | ||
|
|
||
| ### Limited Autonomy | ||
| Pre-approved payment methods and spending limits require human authorization, defeating the purpose of autonomous agents. Agents cannot dynamically adjust their resource usage or respond to changing market conditions. |
There was a problem hiding this comment.
I would create 5 bullet points just a bit more compressed:
- Can't Create Accounts: signup glows requires human verification through CAPTCHA, email or phone which AI agents can't do
- Can't Complete KYC (would delete or add to create accounts it very similar)
- Can't Handle Micropayments: .....
But great work on the file, i think its much more clear and straight to the point now!!
| ## The Micropayment Impossibility | ||
|
|
||
| Traditional payment systems make micropayments economically impossible: | ||
|
|
||
| ``` | ||
| Transaction Value: $0.01 (1 cent API request) | ||
| Processing Fee: 2.9% + $0.30 | ||
| Total Fee: $0.30029 | ||
| Net to Merchant: -$0.29029 (loss of 2,903%) | ||
|
|
||
| Result: Merchant loses money on every transaction | ||
| ``` | ||
|
|
||
| This economic reality forces developers into subscription models even when pay-per-use would better serve users. |
There was a problem hiding this comment.
Rework maybe into the cost structure problems? the cost are already outlined in High Percentage Fees so it is easy to just include the idea below of how this make it impossible for micropayments
Also very personal but im not a big fan of how the json notation looks on the markdown
There was a problem hiding this comment.
Agree, done
| ## Summary | ||
|
|
||
| Traditional payment systems create insurmountable barriers for modern digital commerce through account requirements, high fees, settlement delays, and automation limitations. These systems make micropayments impossible and force developers into suboptimal business models. The x402 protocol addresses all of these limitations by providing instant, permissionless, HTTP-native payments with minimal fees. |
There was a problem hiding this comment.
would delete, I think the paragraph above sums it up pretty well
Summary: The Need for a New Approach
There was a problem hiding this comment.
Agree, deleted.
| 4. Data returned immediately | ||
| ``` | ||
|
|
||
|  |
There was a problem hiding this comment.
can you delete or create a new image? it looks a bit bad with the coinbase logo on the facilitator since we have ones already on avalanche
There was a problem hiding this comment.
I tried to find a simple example/scenario like this, but I couldn't find any. Otherwise I'll try to create an image or delete that and explain in some way
There was a problem hiding this comment.
To me this file still feels very long and detailed to read - thinking of what is the objective for the student, i like the layout of introducing x402, what is the payment problem, what is the ai agent problem, and some quick examples to get him in the right context of what/why/how he is going to learn about
But this to me feels like too many in depth details about the usecases - something a bit more similar to the image below with a nice foto i think would be more effective
https://www.dynamic.xyz/blog/how-x402-and-dynamic-enable-internet-native-payments-for-ai-and-apis
Use Cases that x402 Unlocks Section in the link above
There was a problem hiding this comment.
Yes, I understand what you mean, it's not easy and smooth to read. With that section, I wanted to give some potential ideas for creating services to sell with x402, so I tried to be broad enough not to mention the usual few use cases. I'll leave it on hold for now and try to figure out how I can improve it
| ### Payment Requirements Object (`accepts` array) | ||
|
|
||
| Each payment option in the `accepts` array contains: | ||
|
|
||
| | Field | Type | Required | Description | | ||
| |-------|------|----------|-------------| | ||
| | `scheme` | string | Yes | Payment scheme | | ||
| | `network` | string | Yes | Blockchain network identifier | | ||
| | `maxAmountRequired` | string | Yes | Maximum payment amount required (in token base units) | | ||
| | `resource` | string | Yes | Resource path being requested | | ||
| | `payTo` | string | Yes | Recipient blockchain address | | ||
| | `asset` | string | Yes | Token contract address | | ||
| | `maxTimeoutSeconds` | number | No | Maximum time to complete payment | | ||
| | `description` | string | No | Human-readable description | |
There was a problem hiding this comment.
can the explanations belowe be listed in the same order as the array (first scheme, then network)
it foes from amount (3) to asset (6) to network (2)
also maybe we can just extend the descriptions and make this shorter (except for the scheme) - below an example
| maxAmountRequired | string | Yes | Maximum payment amount required (in token base units) (e.g: USDC has 6 decimals so 1 USDC => "maxAmountRequired": "1000000" |
There was a problem hiding this comment.
Nice catch on listing in the same order.
For the table description, I would prefer not to change it, otherwise with 8 fields, even if there were only two rows each, it would become a very large table that would take up more than half the screen.
But I've changed a bit the maxAmountRequiered description below to make it shorter and more coincise.
| ### Step 1: Configure Network in Wallet | ||
|
|
||
| Add Fuji testnet to MetaMask or Core wallet: | ||
|
|
||
| ```javascript | ||
| // Network configuration | ||
| { | ||
| networkName: "Avalanche Fuji Testnet", | ||
| rpcUrl: "https://api.avax-test.network/ext/bc/C/rpc", | ||
| chainId: 43113, | ||
| symbol: "AVAX", | ||
| explorerUrl: "https://testnet.snowtrace.io/" | ||
| } | ||
| ``` | ||
|
|
||
| Add Fuji to your wallet using the configuration above. Core Wallet has Fuji pre-configured. | ||
|
|
There was a problem hiding this comment.
i would just explain this for core, academy users most likley need to have it if they want to do anything with the console
There was a problem hiding this comment.
Yeah it depend on the SDK that we can find and which wallet integrations are available. Idk if there's any Avalanche specific sdk available that integrate Core
There was a problem hiding this comment.
I would just stick to explaining how to implement one (and maybe linking the guides to how to do the others)
When learning something new offering too many options just makes it confusing, especially if its something complicated
There was a problem hiding this comment.
Yeah, probably I can describe there only the facilitator used in the SDK and then mention the documentation for the others.
navillanueva
left a comment
navillanueva
left a comment
There was a problem hiding this comment.
Finished the second review, I liked the improvements some files have made, but I would like to know what is the overall objective for the person taking this course?
To me this course is about "what x402 is and how to implement it" which should give you a basic understanding of x402 and what SDKs you can use to implement it. I say this because there are some files in the technical architecture that are very in-depth and look s like they are for someone becoming an "expert on x402"
For me a good analogy is Account Abstraction, many people use it through any SDK like Biconomy, and a good course would explain its key elements like Bundler and the Entry point contract - but you probably dont need to know about all the security implications of running a bundler if you are going to just use an SDK
So for this course, the security considerations, blockchain settlements files, are these things that any user needs to know? or will all of this complexity/knowledge be abstracted away if they are just using Thirdweb to set up their x402?
|
Pushed some of the changes (the one with the 👍 are made). Need to search or create some SDK to make it easy for user to start working with x402 |
Added the x402 academy course.
Introduction and technical architecture already explained, as well as the current avalanche facilitators.
A tutorial with the actual implementation process will need to be added.