NEM (XEM) Official Thread - 100% New Code - Easy To Use APIs

[Damelon]

Gives the scroll button a workout!

[makoto1337]

I tried my best to answer this, though it seems that some of the categories are arbitrary. Maybe someone else can comment if they disagree with me.

NEM
Operational	No
Consensus Mechanism	POI
Block Production Time	60s
Recommended Confirmation Time	10 blocks
Worst Case for Confirmation Time	360 blocks
Transaction Load	2 tps
Anonymous Transactions	Future TBD
Transaction Fee Costs	Progressive
Network Security Costs	Transaction Fees
Share Supply	8.99 billion
Share Divisibility (precision)	6 decimal places
Profit Sharing	no
Market Pegged Assets	In Development
User Issued Assets	In Development
Order Matching	In Development
User Registered Accounts	In Development
Messaging	yes
Cross-Chain Trading Support	In Development
Multisignature	Yes
Smart Contracts	In Development
Hardware Wallet	In Development
Mobile Wallet	In Development
Decentralised Exchange	In Development
Pruning	In Development
Voting System	In Development
Instant Transactions	In Development
Automated Transactions	In Development
Mesh Networking	In Development
Account Control	In Developmentt
Marketplace	In Development
Brain Wallet	In Development
Alias System	In Development
Encrypted Blockchain Messaging	yes
Merchant Tools	In Development
Inflation	0%

Regarding TPS: this is still being looked into. We did extensive tests and exceeding 120 trans/block makes the blocks too big for people with poor internet connections to share with their peers easily. We may increase the number of transactions in the future based on the health of the network and usage (e.g., avg size of attached messages, etc).

[Damelon]

I tried my best to answer this, though it seems that some of the categories are arbitrary. Maybe someone else can comment if they disagree with me.

Yes, please add things or put question marks where needed

Thanks for filling it out!

[makoto1337]

quoting simply because this is ridiculous behaviour(especially coming from someone highly involved in nxt marketing iirc) and i want to set it in stone.

Cross posting this from Nxt forum, because I feel there is some miscommunication here

https://nxtforum.org/general-discussion/this-is-who-you-picked-to-do-marketing-for-nxt/msg147255/#msg147255

I think salsa posted this so we can work on this: https://nxtforum.org/general-discussion/help-design-a-comparative-matrix-for-presentation-and-nxt-wiki/msg147223/#new

As I read it, it's just a question of filling it in so we have accurate info on that matrix, nothing more.

The post comes in the middle of some less fun discussion on your thread which indeed is about just a poll.

Polls on BCT are fun, but their information value is next to useless, I agree with that.

Anyway, as the person who asked to make this matrix, I apologise if you guys feel slighted by it.

That is certainly nót the intention and I hope you know me well enough to know this.

yes my mistake already solved on nxtforum deepest apologies to salsacz. purely bad timing following edeaqa's posts.

ps. could we remove all the lists except one? :L its guna make the page awfully long

This is called "priming." It's interesting that introducing bias can have a large impact on subsequent perception.

[salsacz]

thanks, Lon. Missed you in HK conf. Will you be in upcoming Singapore/Shanghai/HK confs?

[rockethead]

I tried my best to answer this, though it seems that some of the categories are arbitrary. Maybe someone else can comment if they disagree with me.

NEM
Operational	No
Consensus Mechanism	POI
Block Production Time	60s
Recommended Confirmation Time	10 blocks
Worst Case for Confirmation Time	360 blocks
Transaction Load	2 tps
Anonymous Transactions	Future TBD
Transaction Fee Costs	Progressive
Network Security Costs	Transaction Fees
Share Supply	8.99 billion
Share Divisibility (precision)	6 decimal places
Profit Sharing	no
Market Pegged Assets	In Development
User Issued Assets	In Development
Order Matching	In Development
User Registered Accounts	In Development
Messaging	yes
Cross-Chain Trading Support	In Development
Multisignature	Yes
Smart Contracts	In Development
Hardware Wallet	In Development
Mobile Wallet	In Development
Decentralised Exchange	In Development
Pruning	In Development
Voting System	In Development
Instant Transactions	In Development
Automated Transactions	In Development
Mesh Networking	In Development
Account Control	In Developmentt
Marketplace	In Development
Brain Wallet	In Development
Alias System	In Development
Encrypted Blockchain Messaging	yes
Merchant Tools	In Development
Inflation	0%

Regarding TPS: this is still being looked into. We did extensive tests and exceeding 120 trans/block makes the blocks too big for people with poor internet connections to share with their peers easily. We may increase the number of transactions in the future based on the health of the network and usage (e.g., avg size of attached messages, etc).

I believe ours is a mesh network. If it is multi-node to multi-node communication, it is a mesh, which is our case.

[Eadeqa]

elliptic curve: "Switched elliptic curve from secp256k1 to ed25519: Ed25519 is a state of the art elliptic curve. Verification of signatures is about 6 times faster for ed25519. This will speed up the synchronization process."

Last time I looked it up, there were no good (reviewed) / fast implementations of Ed25519 in Java. What library are using for Ed25519 ?

[jabo38]

The NEM devs aren't messing around 

[makoto1337]

elliptic curve: "Switched elliptic curve from secp256k1 to ed25519: Ed25519 is a state of the art elliptic curve. Verification of signatures is about 6 times faster for ed25519. This will speed up the synchronization process."

Last time I looked it up, there were no good (reviewed) / fast implementations of Ed25519 in Java. What library are using for Ed25519 ?

That is correct. Unfortunately there were no good java implementations of this curve so we had to do it ourselves.

[jabo38]

The NEM devs aren't messing around  

it's real time

[Eadeqa]

elliptic curve: "Switched elliptic curve from secp256k1 to ed25519: Ed25519 is a state of the art elliptic curve. Verification of signatures is about 6 times faster for ed25519. This will speed up the synchronization process."

Last time I looked it up, there were no good (reviewed) / fast implementations of Ed25519 in Java. What library are using for Ed25519 ?

That is correct. Unfortunately there were no good java implementations of this curve so we had to do it ourselves.

How do you know you implemented it correctly?  Should it not be reviewed by some crypto guru who understands ECC?

[jabo38]

NEM has 5 very well educated and very experienced core devs.  There might very well be a guru or two on the team.  Apparently building a new code from scratch and doing it well is quite a challenge.

As pretty much everyone knows, I don't know hardly anything from the technical perspective, but I talked to a programmer who independently decompiled the code and was very impressed.  

Ethereum had a massive pre-sale and so it is open source pre-launch, but pretty much only the coins with massive pre-sales are open-source pre-launch.  

That said, it is not completely locked away either.  It is possible to decompile it and have a good look.  @Eadeqa, please take a moment to decompile it and take a look.  I hope you can look at it and come back and say good things!

[Eadeqa]

NEM has 5 very well educated and very experienced core devs.  There might very well be a guru or two on the team.  

There is no cryptographer among the 5. They are all programmers.

@Eadeqa, please take a moment to decompile it and take a look

I pretty sure they implemented (probably just copied C++ version) of ed25519 correctly, but still are they 100% sure?

[makoto1337]

Any Greek NEMsters?

[BloodyRookie]

For those of you who are asking themselves what the starting point for the ed25519 implementation was:

http://lmgtfy.com/?q=Bloody+Rookie+ed25519

[gimre]

For those of you who are asking themselves what the starting point for the ed25519 implementation was:

http://lmgtfy.com/?q=Bloody+Rookie+ed25519

What you'll find there is only part of our changes, it'll all be visible, once nem.core will become public
(so that NXT will be able to borrow ed25519 if they'll want to)

There is no cryptographer among the 5. They are all programmers.

We went thorugh curve25519 paper, and ed25519 paper (and bloodyrookie went through some more papers). It's math. We're NOT BAD at math.

[Eadeqa]

For those of you who are asking themselves what the starting point for the ed25519 implementation was:

http://lmgtfy.com/?q=Bloody+Rookie+ed25519

I saw that before but wasn't clear this version is being used in nem. You yourself wrote:

https://github.com/BloodyRookie/ed25519-java

"There are no guarantees that this is secure for use. Tests against the data from the Python implementation are passing, but this has not yet been audited by a professional cryptographer."

[gimre]

http://lmgtfy.com/?q=Bloody+Rookie+ed25519

"There are no guarantees that this is secure for use. Tests against the data from the Python implementation are passing, but this has not yet been audited by a professional cryptographer."

You do realize, this is text from FORKed implementation...

[Eadeqa]

(so that NXT will be able to borrow ed25519 if they'll want to)

Pretty unlikely Nxt would switch to anything else, at this point. It's probably impossible now.

We went through curve25519 paper, and ed25519 paper (and bloodyrookie went through some more papers). It's math. We're NOT BAD at math.

The basic rule is that you don't implement your own crypto and use well tested implementation.

[gimre]

The basic rule is that you don't implement your own crypto and use well tested implementation.

Do not mix implementing OWN crypto, with porting implementation.