Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Research on Lite Server Provisioning #3057

Open
Tracked by #2716
swift1337 opened this issue Oct 28, 2024 · 4 comments
Open
Tracked by #2716

Research on Lite Server Provisioning #3057

swift1337 opened this issue Oct 28, 2024 · 4 comments
Assignees
@morde08
Labels
chain:ton operation Operation related (no codebase change involved)

Comments

@swift1337
Copy link
Contributor

swift1337 commented Oct 28, 2024 •
edited
Loading

  • Investigate how to run lite-server on testnet / mainnet
  • Prepare a playbook for further deployment by observer&siginers

Read more
@swift1337 swift1337 mentioned this issue Oct 28, 2024
Open
@swift1337 swift1337 added operation Operation related (no codebase change involved) chain:ton labels Oct 28, 2024
@swift1337 swift1337 changed the title Research on Lite Client Provisioning Research on Lite Server Provisioning Oct 28, 2024
@swift1337
Copy link
Contributor Author

cc @CharlieMc0 @CryptoFewka

@morde08 morde08 self-assigned this Oct 28, 2024
@CryptoFewka
Copy link
Contributor

@swift1337 two questions:

Is ZetaClient going to be a liteclient which must connect to a liteserver?

If yes, will ZetaClient be using the ADNL API, the REST API, or both?

@CryptoFewka
Copy link
Contributor

CryptoFewka commented Oct 28, 2024 •
edited
Loading

Based on the use of the tongo library, it seems like ADNL is required rather than using the REST API, necessitating the creation of a private full or archive node.

@swift1337
Copy link
Contributor Author

@CryptoFewka we're using ADNL over UDP, yes.

necessitating the creation of a private full or archive node.

I set up a testnet full-node + lite-server. Based on my research the default archival param is --archive-ttl 2592000 which means the full-node has ~ 30 days of history.

Shall we close the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@morde08 morde08

Labels
chain:ton operation Operation related (no codebase change involved)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@morde08 @swift1337 @CryptoFewka