New Cel2 Version of Docs #1500
Open
New Cel2 Version of Docs #1500
Conversation
This file contains 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
Co-authored-by: Aaron DeRuvo <[email protected]>
Co-authored-by: Aaron DeRuvo <[email protected]>
swap out user with octocat
✅ Deploy Preview for celo-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
sodofi
requested review from
marekolszewski,
lvpeschke and
katen0ra
and removed request for
alvarof2
sodofi
changed the title
lvpeschke
approved these changes
Oct 1, 2024
|
Note: I did not review every page, relying on the other reviewers to have a look here. |
lvpeschke
reviewed
Oct 1, 2024
aaronmgdr
reviewed
Oct 4, 2024
aaronmgdr
reviewed
Oct 4, 2024
aaronmgdr
reviewed
Oct 4, 2024
| @@ -0,0 +1,20 @@ | |||
| --- | |||
| title: Verify with Celo Explorer | |||
There was a problem hiding this comment.
this should be replace with blockscout verifiucation page.
aaronmgdr
reviewed
Oct 4, 2024
|
|
||
| Celo wallets should follow [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki) for deriving private keys from [BIP39 mnemonics](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki). Celo's key derivation path is `m/44'/52752'/0'/0`. The first key is typically the `account key` for balance transfers, while the second key can be derived as the `dataEncryptionKey` for encrypting information. | ||
|
|
||
| ### Identity Protocol |
aaronmgdr
reviewed
Oct 4, 2024
|
|
||
| ### Wallet Address Management | ||
|
|
||
| When transferring assets, wallets should check the receiving account's `walletAddress`. Smart contract accounts may have different recovery characteristics but receive funds at a different address. A `walletAddress` of `0x0` indicates that a different mechanism is required to acquire the `walletAddress`. |
There was a problem hiding this comment.
i dont think this is really true
aaronmgdr
requested changes
Oct 4, 2024
|
remember that sweet bridging page @therealharpaljadeja made for the dango launch? lets bring that back |
aaronmgdr
reviewed
Oct 4, 2024
|
|
||
| ### Key Derivation | ||
|
|
||
| Celo wallets should follow [BIP44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki) for deriving private keys from [BIP39 mnemonics](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki). Celo's key derivation path is `m/44'/52752'/0'/0`. The first key is typically the `account key` for balance transfers, while the second key can be derived as the `dataEncryptionKey` for encrypting information. |
There was a problem hiding this comment.
note to self about derivation key standard. re defaulting to ethereum
Co-authored-by: Victoria <[email protected]>
Co-authored-by: Victoria <[email protected]>
Co-authored-by: Aaron DeRuvo <[email protected]>
Co-authored-by: Aaron DeRuvo <[email protected]>
…dev-v2-edits merging latest branch updates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.