pip-27: add PIP-27 for Pruned Node #132
Conversation
|
The commit 4802812 (as a parent of 7d7703b) contains errors. |
|
@b00f Please fix lint issue first. |
| @@ -0,0 +1,127 @@ | |||
| --- | |||
| pip: 27 | |||
| title: Pruned Node | |||
There was a problem hiding this comment.
I think it's better to call it light node or light client since every protocol did it. I mean everyone knows this concept as the light client so it can cause misunderstanding.
| We need to add a new command named `import` to `pactus-daemon`. | ||
| The `import` command shows a list of available databases that can be imported from a centralized server. | ||
| Once the user chooses a database, it downloads and extracts it into the working directory. | ||
| If a database already exists, it should show an error before downloading. |
There was a problem hiding this comment.
In this case, the pruned node is downloading only some part of the chain! not the whole chain from Genesis, so can we still trust the centralized server by verifying?
We are only verifying and seeing some parts of the chain, is there any way for manipulation by a centralized server?
And one more important issue, we are syncing some blocks at all, what about indexed data extracted from transactions? balances, stakes, and in future contracts states?
When we have a whole chain, we can retrieve states by reading whole blocks and indexing the changes that a transaction makes, such as bonding a new validator, sending a native coin, or a contract deploy.
But when we don't have the whole chain we need these data and we need to verify them as well.
There was a problem hiding this comment.
Let's continue this discussion on #134
b00f
changed the title
This PR drafts a new PIP to define Pruned Nodes in Pactus.
It is in draft mode and should be discussed and get completed.