We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As i see it user must be able just provide us an url of RPC endpint and from it we sopouse create crawler from it.
So add new chain just by 1 url provided must go by next steps:
--name
--RPC
Flow:
Request endpoints:
Decide if it side chain(mark in chains database name convention user_id)
Autogenerate cli create client/models/deploy scripts/migrations/PRs?
create client
models
deploy scripts
migrations
PRs?
Run backwards and forward crawl
\blockchain_name defeniton.proto client.go index_models.py labels_models.py
(@Andrei-Dolgolev see it as merge of dbv3 repo into seer )
table 1. rpcs array<strings> 2. chain_name 3. index db URI 4. labes db URI 5. user_id uuid
1 crawler instance per chain and as well move out of or growing envs
2 chains per user
Seer runtime chains/crawler configs.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As i see it user must be able just provide us an url of RPC endpint and from it we sopouse create crawler from it.
So add new chain just by 1 url provided must go by next steps:
Add chain cli
--name
short name with underscores(unique across chains address uniqueness issue to sergei)--RPC
endpoint for request chainFlow:
Request endpoints:
Decide if it side chain(mark in chains database name convention user_id)
Autogenerate cli
create client
/models
/deploy scripts
/migrations
/PRs?
Run backwards and forward crawl
(@Andrei-Dolgolev see it as merge of dbv3 repo into seer )
We have only some list of clients(EVM) for l1/l2/l3 and have chains tables
1 crawler instance per chain and as well move out of or growing envs
2 chains per user
Seer runtime chains/crawler configs.
The text was updated successfully, but these errors were encountered: