Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

Support starknet.py full node #76

Open
ca11ab1e opened this issue Jul 26, 2022 · 0 comments
Open

Support starknet.py full node #76

ca11ab1e opened this issue Jul 26, 2022 · 0 comments
Assignees
@antazoey
Labels
size: 3 pieces Moderately challenging, well-defined, may require a bit of research

Comments

@ca11ab1e
Copy link
Contributor

ca11ab1e commented Jul 26, 2022 •
edited by NotPeopling2day
Loading

Overview

Support full node.

Specification

When the user specifies a URI that is not testnet or mainnet, have it use a FullnodeClient from Starknet.py instead of the GatewayClient it uses currently.

The more challenging part here (with unknowns) is any potential differences that arise. Hopefully it is minimal in which case this a simple feature to support.

NOTE This will be needed for using Alchemy as a Starknet provider

Dependencies

Understanding of full node.

Review imports at the beginning of work.

Unknowns

Schema might be different vs the current returned value
@antazoey antazoey added the size: 3 pieces Moderately challenging, well-defined, may require a bit of research label Aug 22, 2022
@antazoey antazoey mentioned this issue Sep 27, 2022
Open
@antazoey antazoey self-assigned this Oct 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@antazoey antazoey

Labels
size: 3 pieces Moderately challenging, well-defined, may require a bit of research
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@antazoey @ca11ab1e