Improve readability and navigation of docs through updated info arch.#329
Improve readability and navigation of docs through updated info arch.#329johnnymatthews wants to merge 11 commits into
Conversation
Deploying docs with
|
| Latest commit: |
f366534
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://596794a9.docs-czv.pages.dev |
| Branch Preview URL: | https://refactor-info-arch-restructu.docs-czv.pages.dev |
| +++ | ||
| draft = true | ||
| title = "Publish & earn" | ||
| description = "How to publish Views to the network and earn SHNZ from consumption." |
There was a problem hiding this comment.
Nitpick: We wont be incentivizing view creation by paying the view author.
| cp -r ~/.defra/keys /mnt/backup-drive/ | ||
| ``` | ||
|
|
||
| ### What types of data are indexed? |
There was a problem hiding this comment.
| ### What types of data are indexed? | |
| ### What type of data is indexed? |
|
|
||
| ### How long does it take to sync? | ||
|
|
||
| Sync time depends entirely on the chosen start height. The further back the Generator client begins, the longer it will take to catch up to the current block height. The Generator client processes blocks approximately 2–4 seconds per block, which is faster than Ethereum's 12-second block time. This allows the Generator client to gradually close any sync gap after initial backfilling. |
There was a problem hiding this comment.
We should consider rewriting this to discuss how syncing the generator is not a priority since the host only writes blocks as they are written. No need to discuss archive nodes atm. Data in data out, theres no way for a host to request 'synced' blocks atm
|
|
||
| ### What is the difference between a Host and a Generator? | ||
|
|
||
| Generator clients are the write side: they read raw blocks from an Ethereum execution node, sign the data, and gossip it over P2P. Host clients are the read side: they receive those signed primitives, verify them, run WebAssembly lens transforms to build Views, and serve the results to applications over GraphQL. A Generator client talks to a source-chain node; a Host client never does. See the [Run a Host](/run/run-a-host/) overview for more. |
There was a problem hiding this comment.
would be good to add something about attestations being the record of which source wrote which blocks/document.
|
|
||
| A public Generator client you can point at is planned; this page will link it once it's live. | ||
|
|
||
| ### Can I connect my Host client to my own Generator client? |
There was a problem hiding this comment.
if it is on the same machine then they need to change the common ports 9181, 9171, 8080
| @@ -0,0 +1,28 @@ | |||
| +++ | |||
| title = "Views" | |||
There was a problem hiding this comment.
add section on materialized v non materialized
Co-authored-by: dvncan <44993570+dvncan@users.noreply.github.com> Co-authored-by: Johnny <9611008+johnnymatthews@users.noreply.github.com>
PREVIEW HERE
Closes #242
For testing:
/llms.txtandllms-full.txtrespectivly.