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

[rigel]

XEMsign - Automated cosignature
Written in JavaScript for NodeJs.

Review, fork, use, improve => GitHub

Still pretty basic code that needs lots of improvements but it does the job

You absolutely must know how to correctly use multi signatures accounts before use or your XEMs can be lost forever !

Does your software cosign every transaction it sees or is it possible to define some rules?

It would be nice to have rules like:
sign transactions up to 1000 XEM
sign no more than 100 transactions per hour
sign no more than 1 transaction per day to the same recipient address
...

[patmast3r]

XEMsign - Automated cosignature
Written in JavaScript for NodeJs.

Review, fork, use, improve => GitHub

Still pretty basic code that needs lots of improvements but it does the job

You absolutely must know how to correctly use multi signatures accounts before use or your XEMs can be lost forever !

Does your software cosign every transaction it sees or is it possible to define some rules?

It would be nice to have rules like:
sign transactions up to 1000 XEM
sign no more than 100 transactions per hour
sign no more than 1 transaction per day to the same recipient address
...

The readme on github states that there are already some rules.
Obviously a lot more is possible.

[Quantum_Mechanics]

@patmast3r

Sounds good to me
Let's see what other nembers think

@rigel

Sure it can do a lot more, there is only a limit per tx and dayli amount for now. The multsignature transaction will be initiated faucet side to manage user claims. So addresses claiming from the faucet.

Actually the only issue is if there are too many requests closes to  each others. It only signs the last unconfirmed transaction it sees, some requests just could never be executed and included in blocks as when the limit is reached it does not sign anymore.

Ex:
T1: 2/3 (cosig 1 and 2)
T2: 2/3 (cosig 1 and 3)
T3: 2/3 (cosig 1 and 2)
...
Dayli amount reached, stop signing.
...

I found the solution, I'll try to implement batch co-signing today, to sign all valid unconfirmed transactions at once.

[jabo38]

http://www.coindesk.com/visa-blockchain-tech-innovation-labs/

It's happening. Banks and big companies and even some countries are starting to get interested in blockchains.

Sure is nice we are building the best blockchain for them.

It's NEM. It's here and soon it will be ready to go. 

[jabo38]

Few questions:

How many XEM would you like a faucet to give out ?
Do you want it instant or every n amount ?
How many time between claims ?

I think 1k to start with should be fine
Within a couple of minutes I'd like to see the pending tx in my account
Depensd on the amount. At 1k I'd say once every 48 hours.

I'd also set a daily limit for the faucet as a whole. Say 100k.

It depends on how much we get people to donate. I was going to donate some but as long as I was paying for iTunes was thinking 100 every three days.

To me the main point of a faucet is to get people to try to the wallet and get third party devs some coin to test with, not really as a way to make people rich. Though I'm not completely sure how other people think about it. If there is a big donator then definitely it is okay to give up to 1000

[mladen00]

vote for xem

https://bitcointalk.org/index.php?topic=1151078.0

[MemberCount+1]

vote for xem

https://bitcointalk.org/index.php?topic=1151078.0

check for XEM, QORA, XRP 

[nembit86]

vote for xem

https://bitcointalk.org/index.php?topic=1151078.0

Voted !

[jabo38]

from Jabo 38

'NEM brings back the early decentralized spirit of anybody and everybody running a node.  A one-click installer that lets a light server run in the background.'

This should be music to everyone's ears and these words should be relayed everywhere !!!!!!!!

 I think Nictoshi Szabomoto would be happy to see that coming back in style.  

[marcos19]

voted

[tyz]

Voted, too! XEM and Qora are the only coins at the moment to vote for. Hope we will get it.

vote for xem

https://bitcointalk.org/index.php?topic=1151078.0

[Quantum_Mechanics]

XEMsign - Automated cosignature improved !

Features:
- Batch transactions
- Detailed transaction informations

[jabo38]

XEMsign - Automated cosignature improved !

Features:
- Batch transactions
- Detailed transaction informations

I can tell you are working hard!

[Quantum_Mechanics]

I can tell you are working hard!

It's really basic code and I'm having a lot of fun playing with the APIs

Faucet is almost done, just need BrowserFingerPrinting, claiming parameters (chosen by the community) and some tests.
Then you can review it and deploy it where you want

[jabo38]

I can tell you are working hard!

It's really basic code and I'm having a lot of fun playing with the APIs

Faucet is almost done, just need BrowserFingerPrinting, claiming parameters (chosen by the community) and some tests.

I'll ask on Telegram about claiming parameters.

[jabo38]

This exchange project is a private concern and intends to make money from the community.
So this 50 million xem is a loan? Or is it a gift? It is about 6000 euro

It is not a gift or a loan.  It is a fund set up as a stimulus for the NEM ecosystem (XEM released at milestones).  So basically it is paying people to build on the NEM system. The community votes and decides which projects to help kickstart that will then in return help the NEM ecosystem with the business they bring.  

[patmast3r]

I can tell you are working hard!

It's really basic code and I'm having a lot of fun playing with the APIs

Faucet is almost done, just need BrowserFingerPrinting, claiming parameters (chosen by the community) and some tests.
Then you can review it and deploy it where you want

I suggest you use this https://github.com/Valve/fingerprintjs2 for the fingerprinting.
It's a new release of what we adapted for the claiming portal (adapted to make it harder to change ones fingerprint).

[Quantum_Mechanics]

I suggest you use this https://github.com/Valve/fingerprintjs2 for the fingerprinting.
It's a new release of what we adapted for the claiming portal (adapted to make it harder to change ones fingerprint).

It is exactly what I used  

[patmast3r]

I suggest you use this https://github.com/Valve/fingerprintjs2 for the fingerprinting.
It's a new release of what we adapted for the claiming portal (adapted to make it harder to change ones fingerprint).

It is exactly what I used  

Good

It also just occured to me that you should probably use a captcha and maybe we should block people indefinitely after 2 or 3 drips. I man a faucet is for people to check out NEM not to have a constant flow of XEM.

[Quantum_Mechanics]

Good

It also just occured to me that you should probably use a captcha and maybe we should block people indefinitely after 2 or 3 drips. I man a faucet is for people to check out NEM not to have a constant flow of XEM.

Did the captcha also (I just need to change for Recaptcha).
For blocking, if you want it, I can do it. The faucet core is ready and XEMbot can initiate batch multisignatures requests every x minutes for addresses meeting requirement. I can add a new counter for every claims from an address and block at n claims.
Still the design to do, some little tests and it's good