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

[Quantum_Mechanics]

Just made a quick tuto about setting up an online paper wallet generator like XEMpw: here

Tell me if something's wrong or insecure, still learning

[Thingamajig]

There is nothing going on with hthis coin, multiple years of development and "marketing" and still begging for simple infographics. This coin is stale.

Keep telling yourself that, looks like you're not even convinced ...

You sure? They still got "NEM" in their signature. Lol.

Typical troll/fudster if i ever saw one. One minute, they'll be praising nem, next they'll be running it down. Quite predictable. BTT in a nutshell.

[Trollollo]

There is nothing going on with hthis coin, multiple years of development and "marketing" and still begging for simple infographics. This coin is stale.

Keep telling yourself that, looks like you're not even convinced ...

You sure? They still got "NEM" in their signature. Lol.

Typical troll/fudster if i ever saw one. One minute, they'll be praising nem, next they'll be running it down. Quite predictable. BTT in a nutshell.

He is Taunsew or another person caught on socks

[haggis]

Just made a quick tuto about setting up an online paper wallet generator like XEMpw: here

Tell me if something's wrong or insecure, still learning

Thanks for that read. But please, never ever center code   

[Quantum_Mechanics]

Just made a quick tuto about setting up an online paper wallet generator like XEMpw: here

Tell me if something's wrong or insecure, still learning

Thanks for that read. But please, never ever center code  

Yes, I'll clean it, it's the first time I actually quote code inside a web page so..

[EDIT] Done

[jelin1984]

Eletherium

Fuk these coin

[patmast3r]

Why not run a local NIS ? That way you're supporting the network

That would be nice but my old laptop just can't do it,  I'll buy a VPS and a Pi for that later but for now I'm dry

that website runs on an old laptop ? plenty of free webspace around

The website is hosted on a web shared plan actually, so I can't run NIS or NCC on it, my working station is quite old, with small RAM (2GiB) but way enough for what i'm doing
Bad experiences with free hosting, I still prefer to pay if I have to.

I tried to use TransferSendRequest post request (NCC API) and got

Code:

{"timeStamp":11379450,"error":"Bad Request","message":"expected value for property type, but none was found","status":400} 

Well, did you provide a value for type ?
It's easier for us to help you if you also show the code that produces the error or at least the json you POSTed

[jelin1984]

Try to put these coin at some big exchange

Like

Coinbase
Or krakem


Or bitstamp

[Quantum_Mechanics]

Why not run a local NIS ? That way you're supporting the network

That would be nice but my old laptop just can't do it,  I'll buy a VPS and a Pi for that later but for now I'm dry

that website runs on an old laptop ? plenty of free webspace around

The website is hosted on a web shared plan actually, so I can't run NIS or NCC on it, my working station is quite old, with small RAM (2GiB) but way enough for what i'm doing
Bad experiences with free hosting, I still prefer to pay if I have to.

I tried to use TransferSendRequest post request (NCC API) and got

Code:

{"timeStamp":11379450,"error":"Bad Request","message":"expected value for property type, but none was found","status":400} 

Well, did you provide a value for type ?
It's easier for us to help you if you also show the code that produces the error or at least the json you POSTed

Sure, I used the model view provided here and no type in it.

Code:

$maindata = <<<JSON
{
    "wallet": "KrakenLabs",
    "password": "********",
    "account" : "NCIZTWNWFWY4LT7DEKPRSCIKXMVXZS6FL6CE7IS4",
    "recipient": "NAJPXZAQ2HMK72JILFPLJBC6MQLA3LPRLP4Y4NZN",
    "amount": 6000000, //1000000 = 1XEM right ?
    "fee": 4000000,
    "message": "Testing",
    "encrypt": 1,
    "hoursDue": 18
}
JSON;

echo $nem->ncc_post('/wallet/account/transaction/send',$maindata);

[patmast3r]

...

Sure, I used the model view provided here and no type in it.

Code:

$maindata = <<<JSON
{
    "wallet": "KrakenLabs",
    "password": "********",
    "account" : "NCIZTWNWFWY4LT7DEKPRSCIKXMVXZS6FL6CE7IS4",
    "recipient": "NAJPXZAQ2HMK72JILFPLJBC6MQLA3LPRLP4Y4NZN",
    "amount": 6000000, //1000000 = 1XEM right ?
    "fee": 4000000,
    "message": "Testing",
    "encrypt": 1,
    "hoursDue": 18
}
JSON;

echo $nem->ncc_post('/wallet/account/transaction/send',$maindata);

I guess the viemodel must be incomplete. It seems you ned to provide a value for "type" as well.
Can't tell you what without looking it up in the docs.

[Quantum_Mechanics]

...

Sure, I used the model view provided here and no type in it.

Code:

$maindata = <<<JSON
{
    "wallet": "KrakenLabs",
    "password": "********",
    "account" : "NCIZTWNWFWY4LT7DEKPRSCIKXMVXZS6FL6CE7IS4",
    "recipient": "NAJPXZAQ2HMK72JILFPLJBC6MQLA3LPRLP4Y4NZN",
    "amount": 6000000, //1000000 = 1XEM right ?
    "fee": 4000000,
    "message": "Testing",
    "encrypt": 1,
    "hoursDue": 18
}
JSON;

echo $nem->ncc_post('/wallet/account/transaction/send',$maindata);

I guess the viemodel must be incomplete. It seems you ned to provide a value for "type" as well.
Can't tell you what without looking it up in the docs.

Thanks, added the type but now I have

Code:

{"timeStamp":11449180,"error":"Bad Request","message":"expected value for property hexMessage, but none was found","status":400} 

Code:

$maindata = <<<JSON
{
    "wallet": "KrakenLabs",
    "password": "********",
    "account" : "NCIZTWNWFWY4LT7DEKPRSCIKXMVXZS6FL6CE7IS4",
    "recipient": "NAJPXZAQ2HMK72JILFPLJBC6MQLA3LPRLP4Y4NZN",
    "amount": 6000000,
    "fee": 4000000,
    "message": "Testing",
    "encrypt": 1,
    "type": 257,
    "hoursDue": 18
}
JSON;

Seems it's incomplete indeed

[BloodyRookie]

You need

wallet
password
account
recipient
amount
fee
multisigFee
message
hexMessage
encrypt
hoursDue
type

where hexMessage indicates how ncc should interpret the bytes (0=normal message, 1=hexadecimal string).

optional is

multisigAccount

[Trollollo]

Try to put these coin at some big exchange

Like

Coinbase
Or krakem


Or bitstamp

I think it was mistake,to put XEM to many exchanges.A lot of people are trading between exchanges and if they see difference in 1 satoshi,they are buying for 50 sat. at one exchange,and dumping on other exchange for 51 satoshi.This shit is pushing price down.

[Quantum_Mechanics]

You need

wallet
password
account
recipient
amount
fee
multisigFee
message
hexMessage
encrypt
hoursDue
type

where hexMessage indicates how ncc should interpret the bytes (0=normal message, 1=hexadecimal string).

optional is

multisigAccount

Thanks, I have now to deal with fees, for 10 XEM I tried 2, 4 and 5 in both fee and multisigFee but got TRANSACTION_REJECTED_INSUFFICIENT_FEE.

10 XEM transaction minimum fee on NCC is 2 XEM

Code:

$maindata = <<<JSON
{
    "wallet": "KrakenLabs",
    "password": "****",
    "account" : "NCIZTWNWFWY4LT7DEKPRSCIKXMVXZS6FL6CE7IS4",
    "recipient": "NAJPXZAQ2HMK72JILFPLJBC6MQLA3LPRLP4Y4NZN",
    "amount":  10000000,
    "fee": 5000000,
    "multisigFee": 5000000,
    "message": "Testing",
    "hexMessage": 0,
    "encrypt": 1,
    "hoursDue": 18,
    "type": 257
}
JSON;

[BloodyRookie]

Message encryption adds another 6 xem transfer fee since the message is longer than an unencrypted message.
That makes the fee for your transaction 2 + (2 + 6) (xem transfer fee + encryted message transfer fee).

[Quantum_Mechanics]

Message encryption adds another 6 xem transfer fee since the message is longer than an unencrypted message.
That makes the fee for your transaction 2 + (2 + 6) (xem transfer fee + encryted message transfer fee).

Thanks I take note, now I got

Code:

{"timeStamp":11461840,"error":null,"message":"TRANSACTION_REJECTED_SIGNATURE_NOT_VERIFIABLE","status":1208} 

[EDIT] OK now

[nembit86]

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 !!!!!!

[greentea]

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?

[Quantum_Mechanics]

@BloodyRookie

I find out what was the problem, I had to remove "message" from json, I do not know why it didn't worked with it (maybe I did something wrong but I tried "message": with and without text and got same signature error).

The model view I used for '/wallet/account/transaction/send'

Code:

{
    "wallet": "KrakenLabs",
    "password": "***",
    "account" : "NCIZTWNWFWY4LT7DEKPRSCIKXMVXZS6FL6CE7IS4",
    "recipient": "NAJPXZAQ2HMK72JILFPLJBC6MQLA3LPRLP4Y4NZN",
    "amount":  10000000,
    "fee": 4000000,
    "hexMessage": 0,
    "type": 257,
    "encrypt": 0,
    "hoursDue": 1,
    "multisigFee": 0
}

SUCCESS !

Code:

{"innerTransactionHash":{},"code":1,"type":1,"message":"SUCCESS","transactionHash":{"data":"f751c59b96ce95ee0205fdea8c1b28c43b75f06f74fa43d82acfde93a5217027"}} 

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).

Using multisig would be really cool but nothing in the NCC API doc.
I found on github in TransactionController.java that there is actually an API for multisig. Is it ready for use ?

[EDIT] Just read NIS API docs about multi-sig after patmast3r message, I know where to go now and I'm pretty excited to use this.

[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.