it's official, CFB is now more involved in nem than nxt 
Join the club!
Topic: NEM (XEM) Official Thread - 100% New Code - Easy To Use APIs - page 1275. (Read 2985503 times)
Join the club!
Why is my vested balance exactly 10% of that of my current balance?
Each day 10% of your unvested balance becomes vested. (you need 10k XEM vested to start harvesting) What's the latest guess on a release date - haven't seen any updates recently?
It was released yesterday
https://forum.ournem.com/nem-news-alerts/nem-is-launching!/
https://poloniex.com/exchange#btc_xem
What's the latest guess on a release date - haven't seen any updates recently?
its already released. Check OP
What's the latest guess on a release date - haven't seen any updates recently?
Posting addresses here is forbidden. Please remove it!
Why is my vested balance exactly 10% of that of my current balance?
The installer has a typo, its prompting "Checking java verstion". I'm not a grammer nazi, just for future releases 
Found 4 blocks, 0 Fees... Unlucky?
Yaaay, empty blocks 
Before you ask questions again and again, please check out our tutorials. We wrote them just for you 
http://blog.nem.io/nem-tutorial-list/
http://blog.nem.io/nem-tutorial-list/
Come-from-Beyond is BCNext and UtopianFuture at the same time?
maybe he is also Come-from-Above and Moneroman88
it has been shown b4 that cfb might also be satoshi nakamoto and vitalik buterin
wow this be mysterious
that means he's also taunsew and I wouldnt be surprised if he goes by name Jean-Luc too
maybe he is also Come-from-Above and Moneroman88
it has been shown b4 that cfb might also be satoshi nakamoto and vitalik buterin
wow this be mysterious
that means he's also taunsew and I wouldnt be surprised if he goes by name Jean-Luc too
Found 4 blocks, 0 Fees... Unlucky?
..Too..many..posts...
Could you please answer this one?
No they don't have to run at the same time. Only the node you're harvesting on needs to run.
Anything else would defeat the point of the excecise.
Ah nice..
So the approach is:
- Setup remote node with NIS and NCC
- Set remote node's address in local settings -> host
- Activate delegated harvesting
Is this correct?
Could you please answer this one?
Will local node and remote node have to run at the same time to do delegated harvesting?
No they don't have to run at the same time. Only the node you're harvesting on needs to run.
Anything else would defeat the point of the excecise.
So the approach is:
- Setup remote node with NIS and NCC
- Set remote node's address in local settings -> host
- Activate delegated harvesting
Is this correct?
I would first setup a local NIS and NCC and get that working to be sure that there is no principal problem. Then activate delegated harvesting.
Meanwhile you can setup a remote NIS. Once the delegated harvesting is activated (needs 360 blocks) shut down local NIS and start remote NIS with the remote key as boot key.
Then change setting in ncc to connect to the remote NIS.
32bit machine --- > http://blog.nem.io/windows-installation-guide-standalone/
64bit machine --- > follow the link from page 1
good luck!
64bit machine --- > follow the link from page 1
good luck!
IMHO, Come-from-Beyond in/+ NEM team will be awesome synergy
No, the hit and target (it is called like in Nxt) requires only hashing. But as implemented the harvesting account is always generating a block (even when the node is not publishing the block) and that of course requires signing.
What task is solved by generating a block even if it's not published? If there are 2 accounts on a node, one of them contributes less into security of the blockchain and it's a waste of CPU cycles to use it for signing unless you have something special.
1) we were discussing your attack scenario
2) I've explained that unlike in NXT, you'd have to generate block for every "delegated" account that attacker owns
3) I gave you the number that's sensible for an attacker to handle
ok I think I know what you had in mind - yes it'd be possible to decide who's gonna score best block from those attacker's 10000 accounts upfront.
No, the hit and target (it is called like in Nxt) requires only hashing. But as implemented the harvesting account is always generating a block (even when the node is not publishing the block) and that of course requires signing.
What task is solved by generating a block even if it's not published? If there are 2 accounts on a node, one of them contributes less into security of the blockchain and it's a waste of CPU cycles to use it for signing unless you have something special.
IIRC, signing (in java) is <300 microseconds (depends on hardware ofc) , so 1M accounts = 300 seconds, that's bit too much (network could be much further already...)
OFC, you could go with C implementation.
but 10_000 accounts should be doable.
OFC, you could go with C implementation.
but 10_000 accounts should be doable.
You rely on signing in NEM to decide who harvests the next block?
In Nxt only SHA256 is required to pick the forger among accounts when effective balance is known, this is why it's that fast.
No, the hit and target (it is called like in Nxt) requires only hashing. But as implemented the harvesting account is always generating a block (even when the node is not publishing the block) and that of course requires signing.
..Too..many..posts...
Could you please answer this one?
No they don't have to run at the same time. Only the node you're harvesting on needs to run.
Anything else would defeat the point of the excecise.
Ah nice..
So the approach is:
- Setup remote node with NIS and NCC
- Set remote node's address in local settings -> host
- Activate delegated harvesting
Is this correct?
Could you please answer this one?
Will local node and remote node have to run at the same time to do delegated harvesting?
No they don't have to run at the same time. Only the node you're harvesting on needs to run.
Anything else would defeat the point of the excecise.
So the approach is:
- Setup remote node with NIS and NCC
- Set remote node's address in local settings -> host
- Activate delegated harvesting
Is this correct?
I would first setup a local NIS and NCC and get that working to be sure that there is no principal problem. Then activate delegated harvesting.
Meanwhile you can setup a remote NIS. Once the delegated harvesting is activated (needs 360 blocks) shut down local NIS and start remote NIS with the remote key as boot key.
Then change setting in ncc to connect to the remote NIS.
IIRC, signing (in java) is <300 microseconds (depends on hardware ofc) , so 1M accounts = 300 seconds, that's bit too much (network could be much further already...)
OFC, you could go with C implementation.
but 10_000 accounts should be doable.
OFC, you could go with C implementation.
but 10_000 accounts should be doable.
You rely on signing in NEM to decide who harvests the next block?
In Nxt only SHA256 is required to pick the forger among accounts when effective balance is known, this is why it's that fast.
Jump to: