Re: [NEM] NEM -New Economy Movement - No Envy Movement - Updates+Discussion thread
...
1. I heard that Nem is different because you're translating the code. I don't think that's innovative.
2. I think POI is a flawed concept.
3. I'm not sure what is meant by "different types of node", maybe someone can enlighten me.
...
1. I heard that Nem is different because you're translating the code. I don't think that's innovative.
2. I think POI is a flawed concept.
3. I'm not sure what is meant by "different types of node", maybe someone can enlighten me.
...
I added the numbers in the above quite but i did not alter the text.
1. Translation is not the goal here. AFAIK NEM is also going to be built with JAVA so it's not the right word either. I think the goal is to have our own solid codebase and since quite a few things are being changed it's probably better to start over.
2. How so ? (I'm actually interested so plz do answer
)3. From the dev plan (I thought you read it ?):
Quote
NEM will have two types of nodes: server nodes and normal nodes.
Server nodes will store a full blockchain history. The full blockchain will serve as a public ledger, which will be important in order to preserve blockchain explorer functionality. Server nodes will publish all nodes and also a consolidated snapshot.
Normal nodes will connect to the network and request a consolidated snapshot from the server nodes. This snapshot will contain balance information for all accounts as well information about outstanding orders. Snapshots will be made daily and will include data from all confirmed blocks. After syncing the snapshot, the client will need to sync all blocks that were made after the snapshot up to the current time. After syncing those blocks, the client will be ready to begin interacting with the NEM network.
This should minimize the amount of time it takes a fresh client to sync the full blockchain and get online.
A snapshot will be generated daily. When a new snapshot is confirmed by the blockchain, a special no-fee snapshot transaction will be sent to a special account. New clients can validate the most recent snapshot by using hash attached to the last transaction sent to the special account. Snapshots will be validated after 1440 confirmations.
Server nodes will store a full blockchain history. The full blockchain will serve as a public ledger, which will be important in order to preserve blockchain explorer functionality. Server nodes will publish all nodes and also a consolidated snapshot.
Normal nodes will connect to the network and request a consolidated snapshot from the server nodes. This snapshot will contain balance information for all accounts as well information about outstanding orders. Snapshots will be made daily and will include data from all confirmed blocks. After syncing the snapshot, the client will need to sync all blocks that were made after the snapshot up to the current time. After syncing those blocks, the client will be ready to begin interacting with the NEM network.
This should minimize the amount of time it takes a fresh client to sync the full blockchain and get online.
A snapshot will be generated daily. When a new snapshot is confirmed by the blockchain, a special no-fee snapshot transaction will be sent to a special account. New clients can validate the most recent snapshot by using hash attached to the last transaction sent to the special account. Snapshots will be validated after 1440 confirmations.
How will POI deal with people who have dynamic IPs?
The server / normal node scheme seems like it adds a trust factor into the equation.
The same way NXT POS does. The transaction graph will be based on account numbers, not ip addresses.