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

[vaporware asset wizard]

News......News.......News....!!!!!!!!!

https://forum.ournem.com/proposals-for-community-projects/crypto-apex's-application-for-nem-community-funding-3349/new/#new

Check it out!!!!!!!

Company formed to build an exchange for the benefit of NEM.
Voting will start in 5 days..to determine if Community Funds can be put to use there.....please participate !!!!

Voting will last for 5 days !!!!!!

"interested" (do I get a freebie for posting that?) 

[Quantum_Mechanics]

@patmast3r

Awesome ! I'll work on it

..
additional coding work, sorry
..

That's exactly what I am looking for

[rigel]

News......News.......News....!!!!!!!!!

https://forum.ournem.com/proposals-for-community-projects/crypto-apex's-application-for-nem-community-funding-3349/new/#new

Check it out!!!!!!!

Company formed to build an exchange for the benefit of NEM.
Voting will start in 5 days..to determine if Community Funds can be put to use there.....please participate !!!!

Voting will last for 5 days !!!!!!

Wow this is cool ...

Is this something that 'set aside funds' should be supporting?

Absolutely.

Anyone can ask for funds: https://forum.ournem.com/proposals-for-community-projects/proposals-for-community-funding

[jabo38]

...

But I'm not sure it is a good way to automate transactions.
First I was thinking about using two accounts, an account to send automated payments to faucet users, this account would only contain small amount of XEM for security reasons. Every hours or days a bot send N XEM from main account to faucet account to refill it. So main account is safe. If anything's wrong only a small amount of XEM is lost.

Configuration would be:
[APP] => [NCC] => [NIS]
Request to remote NCC connected to remote NIS (don't know if it could work).
A cron would do the automated payment sending '/wallet/account/transaction/send' request to remote NCC, but wallet password still exposed if someone manage to access the server (main reason I thought about 2 accounts but the problem still there).

You can use multi-sig and anautomatated service to secure the funds so that they are secure even if the wallet on the server is compromised.
Setup a multi-sig account with 3 co-signatories (Raise the number for security if you like and have some machines that need something todo).

1 - faucet
2,3 - automated signing (additional coding work, sorry )

faucet initiated the tx on request by the user. the automated signing kicks in either every x minutes or is constantly checking for signing requests.
Now with some additional checks you can make one of those automated signers (or both) into watchdogs.
-only sign x tx per hour
-only sign tx with amount x
-limit withdrawal to x XEM per day
-anything you can think of
As soon as you suspect compromisation you can also simply remove the compromised wallet from the cosignatories.

If you deploy the 3 signatories i.e. faucet and 2 watchdogs on 3 different servers and you got yourself one very freaking secure faucet . I'm sure you'll find some people on slack who are willing to help out with their vps too.

I'd also suggest to use browserfingerprinting to make it harder to request a lot of drips from the faucet.

Might I think you just suggested the first ever decentralized smart faucet???

[patmast3r]

...

But I'm not sure it is a good way to automate transactions.
First I was thinking about using two accounts, an account to send automated payments to faucet users, this account would only contain small amount of XEM for security reasons. Every hours or days a bot send N XEM from main account to faucet account to refill it. So main account is safe. If anything's wrong only a small amount of XEM is lost.

Configuration would be:
[APP] => [NCC] => [NIS]
Request to remote NCC connected to remote NIS (don't know if it could work).
A cron would do the automated payment sending '/wallet/account/transaction/send' request to remote NCC, but wallet password still exposed if someone manage to access the server (main reason I thought about 2 accounts but the problem still there).

You can use multi-sig and anautomatated service to secure the funds so that they are secure even if the wallet on the server is compromised.
Setup a multi-sig account with 3 co-signatories (Raise the number for security if you like and have some machines that need something todo).

1 - faucet
2,3 - automated signing (additional coding work, sorry )

faucet initiated the tx on request by the user. the automated signing kicks in either every x minutes or is constantly checking for signing requests.
Now with some additional checks you can make one of those automated signers (or both) into watchdogs.
-only sign x tx per hour
-only sign tx with amount x
-limit withdrawal to x XEM per day
-anything you can think of
As soon as you suspect compromisation you can also simply remove the compromised wallet from the cosignatories.

If you deploy the 3 signatories i.e. faucet and 2 watchdogs on 3 different servers and you got yourself one very freaking secure faucet . I'm sure you'll find some people on slack who are willing to help out with their vps too.

I'd also suggest to use browserfingerprinting to make it harder to request a lot of drips from the faucet.

Might I think you just suggested the first ever decentralized smart faucet???

Only the sending of the drips or rather the signing of the tx happens decentralized. The faucet itself i.e. the website would still be centralized

[jabo38]

We are in a last ditch effort to merge the old forum to Discourse but we ran into problems. If anybody has any experience with this kind of thing. Please help us out. Saul was able to get the accounts merged but not the posts on the threads. It is not just him. Lots of people have had this problem and had to hack their way through it, just our hacking hasn't turned out so well. One of our main sticking points is Ruby. Here is a thread documenting the problems. https://meta.discourse.org/t/importer-for-simple-machines-2-forums/17656/53

[patmast3r]

We are in a last ditch effort to merge the old forum to Discourse but we ran into problems. If anybody has any experience with this kind of thing. Please help us out. Saul was able to get the accounts merged but not the posts on the threads. It is not just him. Lots of people have had this problem and had to hack their way through it, just our hacking hasn't turned out so well. One of our main sticking points is Ruby. Here is a thread documenting the problems. https://meta.discourse.org/t/importer-for-simple-machines-2-forums/17656/53

You're having all of those problems ? Could you mabe post some specific error message or something like that ? I really don't feel like reading the whole thing since it's prob mostly useless.

[haggis]

Can someone please point me to some reads about the so called "Business Rules"? In particular I'm interested in a whitepaper and at best, a tutorial and/or example application to play with.

[BloodyRookie]

@haggis: business rules are not yet thorrowly discussed so there is nothing at the moment we can present to you.

[haggis]

@haggis: business rules are not yet thorrowly discussed so there is nothing at the moment we can present to you.

Thanks. Is there any ETA on this? As an originaly stakeholder (still) I'd rather like to experiment on this with NEM than Ether or something else 

[patmast3r]

@haggis: business rules are not yet thorrowly discussed so there is nothing at the moment we can present to you.

Thanks. Is there any ETA on this? As an originaly stakeholder (still) I'd rather like to experiment on this with NEM than Ether or something else 

Go ahead and play with the other platforms and then come back and tell us what NEM should do better
It's always best to learn from other's mistakes

[jabo38]

We are in a last ditch effort to merge the old forum to Discourse but we ran into problems. If anybody has any experience with this kind of thing. Please help us out. Saul was able to get the accounts merged but not the posts on the threads. It is not just him. Lots of people have had this problem and had to hack their way through it, just our hacking hasn't turned out so well. One of our main sticking points is Ruby. Here is a thread documenting the problems. https://meta.discourse.org/t/importer-for-simple-machines-2-forums/17656/53

You're having all of those problems ? Could you mabe post some specific error message or something like that ? I really don't feel like reading the whole thing since it's prob mostly useless.

Okay so maybe Saul can comment here but this is what he has written elsewhere.



Hi there, I have been trying to run this import script for awhile now. I have made some progress, but now am pretty stuck, and am not receiving any errors, so I have no clue what is preventing the import.

I am using a VM running Ubuntu 15.04, I have succesfully set up a discourse development environment using this guide: https://meta.discourse.org/t/beginners-guide-to-install-discourse-on-ubuntu-for-development/14727, and have a fully functional smf forum at /var/www/html.
I have managed to import all users (about 1k), but I get stuck on creating posts. To make sure it was stuck at creating posts, and not just taking awhile, I gave my VM 3 cores and 10gb of memory, and left it running for nearly 2 days, not a single post was created.
Anyone have an idea why I am getting stuck on creating posts? Let me know if there is a log or more details I can post.

Can't upload an image, but I'll explain what I am seeing:
creating groups
1/1 (100.0%)
creating users
33/0 (Inf%) )
creating posts
/
Note all though it says 33/0 for users, it has actually imported 1006 users, maybe this is related to the posts not being created, but I have no clue, as in reality, all users have been imported succesfully, regardless of what the output says.


Basically from what I have talked to Saul, he runs the script and there isn't an error exactly in relation to the posts, it just doesn't merge the info.  He can leave it for a day going with all his resources and not even 1 post transfers. 


There are some errors though concerning the user data.  It says it isn't transferred yet it really is.

[Quantum_Mechanics]

Was about to give a try to multi sig but I can't set more than one cosignatory.
Every time I add an address in new cosignatory’s field it got blank when I'm going to the next.

Any idea ?

[BloodyRookie]

@Quantum-mechanics: what do you mean with " I'm going to the next."?

[Quantum_Mechanics]

@Quantum-mechanics: what do you mean with " I'm going to the next."?

I add the address then when I click on "+add cosignatory", the address disappear, the field goes blank, only the top cosignatory address still set

[evi_stale]

This is exactly right. "These are still early days."

PayPal processes $240 billion worth of transactions a year and has a marketcap of $45 billion. https://finance.yahoo.com/q?s=PYPL
Visa processes $4.8 trillion worth of transactions a year and has a marketcap of $181 billion. https://finance.yahoo.com/q?s=V

A $9 billion marketcap is nothing for a technology that will most likely compete with all current financial institutions.

Bitcoin has first-mover advantage and is the top brand, but NEM will have second-mover advantage being more efficient and feature-rich.

Bitcoin
-Has inflation (14,437,800 btc in circulation, that leaves 6,562,200 btc still left to mine). https://blockchain.info/charts/total-bitcoins   https://en.bitcoin.it/wiki/Controlled_supply
-Energy hog Proof-of-Work block reward algorithm. (PoW a.k.a. Proof-of-Waste)
-PoW mining causes monetary inflation.
-Slow 10 minute transaction confirmation.
-Poor initial distribution.
-No asset exchange.

NEM
+Zero inflation (fixed supply, all 9 billion coins released at launch).
+Energy efficient Proof-of-Importance block reward algorithm. (PoI is environmentally friendly and rewards only the most active nodes.)
+PoI harvesting, no monetary inflation, coins are earned solely from transaction fees.
+Fast 1 minute transaction confirmation.
+Relatively large egalitarian distribution.
+Delegated harvesting.
+Encrypted messaging.
+m-of-n Multi-signature.
+Eigentrust++ peer reputation management.
+One-click install client.
+Ninja releases!  
future:
  +Business rules.
  +Decentralized asset exchange.
  +Mobile wallet for Android and IOS.
  +...

NEM is built 100% from scratch (not a fork of Bitcoin or Nxt). The devs engineered NEM for the future with 9 billion* XEM.
*actually 8,999,999,999 XEM (Burning 1 XEM gave us that "fortunate" eight at the beginning.)

Estimated population, based on current growth trends, to reach 9 billion in 2040.  https://en.wikipedia.org/wiki/Projections_of_population_growth
World population to exceed 9 billion by 2050.  http://www.un.org/esa/population/publications/wpp2008/pressrelease.pdf

Bitcoin: 21 million/1 satoshi = 2.1 quadrillion units.
NEM: 9 billion/0.000001 = 9 quadrillion units.

The unregulated derivatives market is ~$1.5 quadrillion dollars. http://moneymorning.com/2014/10/01/taking-profits-in-a-1-5-quadrillion-bubble/

NEM is designed to accommodate our entire global economy.



NEM has great potential. In the future I can easily see 1 XEM being valued at 1 fiat dollar.

Nice summary someone needs to make an infographic out of this ...

That is a very good summary. 

I would love to see it become an infographic, and I could even add a few more nice things about NEM.

If somebody is has the ability to make nice infographics, I will pay them 100,000 XEM bounty out of my own wallet. 

bumping this

Since no one replied I put something together. What do you think of this.

[patmast3r]

@Quantum-mechanics: what do you mean with " I'm going to the next."?

I add the address then when I click on "+add cosignatory", the address disappear, the field goes blank, only the top cosignatory address still set

That sounds extremely weird. What browser are you using and are you maybe using any plug-ins ? Could you take a screen-capture (video) of this phenomenon ?

[Quantum_Mechanics]

@patmast3r



I am using firefox last version, no extra plug-ins, surely an issue from my side, maybe a bunch of updates I need to make (Ubuntu), I'll look at it but still weird.

Btw if someone wants to use the online paper wallet generator locally with no NIS or NCC running, code is now on GitHub.
Only local server, like wamp, lampp needed.

No need to worry about storing key now, just run your own, with a bit of knowledge you can even personalise it

[patmast3r]

@patmast3r

*image_removed_for_space*

I am using firefox last version, surely an issue from my side, maybe a bunch of updates I need to make (Ubuntu), I'll look at it but still weird.

Btw if someone wants to use the online paper wallet generator locally with no NIS or NCC running, code is now on GitHub.
Only local server, like wamp, lampp needed.

No need to worry about storing key now, just run your own, with a bit of knowledge you can even personalise it

Ahh...Now I see what you mean.
I guess it's best if you open an issue on github so the devs can see if there is a way to reproduce and then fix it.
Haven't heard of this one before.

Btw. there is an open-source organisation for all NEM stuff https://github.com/neweconomymovement/.
Would you be willing to move the paper-wallet there ? If so someone needs to give you permission though.

[Quantum_Mechanics]

Ok, I'm doing it now

Btw. there is an open-source organisation for all NEM stuff https://github.com/neweconomymovement/.
Would you be willing to move the paper-wallet there ? If so someone needs to give you permission though.

Sure no problems but it needs to be cleaned a bit ^^