feat(docs): added Foundry guide for AddressValidity#553
Merged
dineshpinto merged 6 commits intoflare-foundation:mainfrom Feb 11, 2025
nikerzetic-aflabs:main
Merged
feat(docs): added Foundry guide for AddressValidity#553dineshpinto merged 6 commits intoflare-foundation:mainfrom nikerzetic-aflabs:main
dineshpinto merged 6 commits intoflare-foundation:mainfrom
nikerzetic-aflabs:main
Conversation
nikerzetic-aflabs
requested review from
dineshpinto and
swarna1101
as code owners
swarna1101
changed the title
swarna1101
reviewed
Feb 8, 2025
docs/fdc/guides/address-validity.mdx
Outdated
| @@ -0,0 +1,661 @@ | |||
| --- | |||
| title: Address validity | |||
Collaborator
Author
There was a problem hiding this comment.
I intentionally omitted the "Check", to better reflect that the attestation type itself is the main focus of the guide.
docs/fdc/guides/fdc-overview.mdx
Outdated
| The first three types are the most generally useful, while the last three are used mostly in FAssets. | ||
|
|
||
| For all six attestation types, the workflow follows the same general steps. | ||
| Because of the waiting period between the first two parts, in which the round is finalised, we have split have the process into three sections. |
Contributor
There was a problem hiding this comment.
This will be a separate section:
## FDC Workflow
Every attestation follows a four-phase process, with a mandatory waiting period between request submission and data retrieval:
1. **Request Preparation** (Off-chain)
- Format attestation-specific data as JSON
- Submit to verifier server for validation
- Receive ABI-encoded request data
2. **Request Submission** (On-chain)
- Submit encoded request to FdcHub contract
- Pay required transaction fees
3. **Data Retrieval** (Off-chain)
- Wait for voting round completion (~90 seconds)
- Request proof from Data Availability Layer
- Verify proof against on-chain data
4. **Data Utilization** (On-chain)
- Use verified data in smart contracts
- Execute attestation-specific logic
nikerzetic-aflabs
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.