NXT :: descendant of Bitcoin - Updated Information

[pinarello]

CfB,

result of the rewards vote for sites and social media.

would you be so kind to pay the people that won, thank you.

S3MKi               82 (31.3%)
allwelder       57 (21.8%)
Mac Red       42 (16%)
yulkisa       39 (14.9%)
Damelon       13 (5%)
Passion_ltc       11 (4.2%)
Coinonaer       8 (3.1%)
apenzl       3 (1.1%)
Mises_77       3 (1.1%)
pablito89       2 (0.8%)
^[GS]^       2 (0.8%)


1) 50,000
2) 30,000
3) 20,000
4) 5,000
5) 5,000
6) 5,000
7) 5,000
8)3,000
9)3,000
10)3,000
11)2,000

[ImmortAlex]

The Bible 2.0 shouldn't be very thick, leave some room for picture, kids don't like to read walls of text.

Do we need to spend some coins to Marvel? Childen like new superheroes! Why do we always talk about promoting among Joe Sixpack? What about his son Jimmy The Chav?

[jl777]

(...)
plan B.
Let us assume there is a group account that holds all the BTC that backs the Assets issued by all the group members and there was a mechanism for deposits and withdrawals to be processed that can be trusted, it could work.
On deposit to any of the BTC variants, actual BTC goes to BTC variant holder, they issue the BTC variant asset and deposit to shared BTC acct.
On withdrawal, anybody that holds any of the BTC variants can redeem it from the shared BTC acct directly using automated mechanism that recognizes all the BTC variants. This side actually seems doable.
The key to make this work is enforcing the "they issue the BTC variant asset and deposit to shared BTC acct". We cannot control when an account issues an Asset. However, we can track in realtime all issued BTC variants and all deposits credited to that variant. Some sort of realtime audit system could then disable withdrawals for any BTC variant that goes out of balance, with associated public message as to the problem issuer's status.
In order to make that foolproof, all participating issuers would need to NOT issue their asset, until there was confirmation of deposit into the shared acct.
So, my long answer, is yes, this is possible, though ultimately boils down to all participants needing to trust the deposit/withdrawal software and all following strict rules of issuing assets.

Ok nice plan B. We have to explain it to everyone.

I think Alias says planB can be reasonably quickly actually implemented using DAC and XCP, but I have no idea how it is done. I am only good for coming up with crazy ideas that sometimes aren't so crazy

James

[sherpico77]

Everyone should Vote here:

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

NXT is on top - DO IT!

Done 

[salsacz]

salsacz, please correct you post or you will create one more myth - I am not a full-time developer of any Nxt appication.

Aye, we don't need too many myths. The Bible 2.0 shouldn't be very thick, leave some room for picture, kids don't like to read walls of text.

the paper is only the source of the information (will be with all citations) for the infographics and for the video

[Come-from-Beyond]

CfB,

result of the rewards vote for sites and social media.

would you be so kind to pay the people that won, thank you.

S3MKi               82 (31.3%)
allwelder       57 (21.8%)
Mac Red       42 (16%)
yulkisa       39 (14.9%)
Damelon       13 (5%)
Passion_ltc       11 (4.2%)
Coinonaer       8 (3.1%)
apenzl       3 (1.1%)
Mises_77       3 (1.1%)
pablito89       2 (0.8%)
^[GS]^       2 (0.8%)


1) 50,000
2) 30,000
3) 20,000
4) 5,000
5) 5,000
6) 5,000
7) 5,000
8)3,000
9)3,000
10)3,000
11)2,000

Any chance that u have their accounts ready?

[marcus03]

Since I need to take a day off of programming, here's the first version of my, yet unnamed, NXT client for Windows.
...

I'm releasing version 1.1. of my Windows NXT client (still no personal account management, NTX transfer options in it or anything that needs your account secret).

Version 1.2. of my Windows NXT client "NXT Solaris" is available: ...

Here is version 1.3 of my Windows NXT client "NXT Solaris".

Download
NXTSolaris-v1.3.zip (39.2 MB) – Download here

SHA256 checksum for NXTSolaris-v1.3.zip: 95B5139E599EFD404E6D317D0A366483E6E30198CE8C3CA14B8CAAE6D3B63C92

SHA256 checksum for nxtapi.dll (v1.3): 2734F788249EF7A1E5836102D66FD97521B0F46E04E95508ABEDDF437468B46D
SHA256 checksum for NXTSolaris.exe (v1.3): 283B18858920FA67BFE8E8CC6EAE5692BE342290FC12D6EA5EF341A67789B288





For more screenshots, please visit: http://nxtsolaris.wordpress.com/


Installation
Simply unzip the archive and run the NXTSolaris.exe file.

If you tried a previous version, simply overwrite all existing files, with the files in the v1.3 zip archive.


Changes for v1.3
-Moved all http API calls and the secret input dialog to a separate open-source dll (source is included together with a a build.bat file)
-Added “Send NXT” function
-Added “Send message” function
-Added “Assign alias” function
-Added alias and message list in personal account management
-Added address book
-Got rid of the ugly button toolbars and switched to a ribbon interface
-Now showing Date/Time of last transaction in the personal account management (also defines the sort order)
-Showing cumulativeDifficulty and totalEffectiveBalance on the status page
-Showing chance to forge in personal account management
-Attachment columns in transactions lists now show decoded plain text messages as a hint
-Bug fix: Public keys in the account lists could get lost
-Fixed logging
-A bunch of other small GUI changes

My TODO list for the next versions in no special order
-Create “new account” function in the API dll (including secure password generator)
-Market data charts
-Show value of NXT in fiat currencies
-Offer a simple and advanced GUI, with the simple GUI targeted at new and casual users
-Orphan cleanup
-Bundle NRS with NXT Solaris (or maybe switch to another implementation if it is available)
-Arbitrary message encryption
-Reed Solomon addresses
-GUI and data retrieval optimization
-Asset exchange support

Donations
I hope you like my client and I’d be extremely happy to see some donations for the future of this project!

NXT: 1758531264253431177

[S3MKi]

hi dudes. Is it current block?
   43606      12292439833850569026      17 Cтyдзeнь 2014 19:37:53   
      
      0      0 + 0      0 B   
      
      2      4445643119525148577      257 %

[EmoneyRu]

hi dudes. Is it current block?
   43606      12292439833850569026      17 Cтyдзeнь 2014 19:37:53   
      
      0      0 + 0      0 B   
      
      2      4445643119525148577      257 %

+1

[Come-from-Beyond]

-Arbitrary message encryption

What algo r u going to use?

[Anon136]

wow marcus03, that looks amazing. too bad i dont use windows.

[Mac Red]

CfB,

result of the rewards vote for sites and social media.

would you be so kind to pay the people that won, thank you.

S3MKi               82 (31.3%)
allwelder       57 (21.8%)
Mac Red       42 (16%)
yulkisa       39 (14.9%)
Damelon       13 (5%)
Passion_ltc       11 (4.2%)
Coinonaer       8 (3.1%)
apenzl       3 (1.1%)
Mises_77       3 (1.1%)
pablito89       2 (0.8%)
^[GS]^       2 (0.8%)


1) 50,000
2) 30,000
3) 20,000
4) 5,000
5) 5,000
6) 5,000
7) 5,000
8)3,000
9)3,000
10)3,000
11)2,000

Any chance that u have their accounts ready?

Mine is: 4263528265010429437

[msin]

Nice work marcus03, lookin good.

[Damelon]

Any chance that u have their accounts ready?

Mine is 18229868146885750725

[marcus03]

-Arbitrary message encryption

What algo r u going to use?

Still looking for a Curve25519 implementation in Delphi/Pascal, but I'm pessimistic. Would make much sense to use the existing private and public keys.

Any chance of API calls to let NRS do encryption, decryption, signing and verification for clients?

[Alias]

(...)
plan B.
Let us assume there is a group account that holds all the BTC that backs the Assets issued by all the group members and there was a mechanism for deposits and withdrawals to be processed that can be trusted, it could work.
On deposit to any of the BTC variants, actual BTC goes to BTC variant holder, they issue the BTC variant asset and deposit to shared BTC acct.
On withdrawal, anybody that holds any of the BTC variants can redeem it from the shared BTC acct directly using automated mechanism that recognizes all the BTC variants. This side actually seems doable.
The key to make this work is enforcing the "they issue the BTC variant asset and deposit to shared BTC acct". We cannot control when an account issues an Asset. However, we can track in realtime all issued BTC variants and all deposits credited to that variant. Some sort of realtime audit system could then disable withdrawals for any BTC variant that goes out of balance, with associated public message as to the problem issuer's status.
In order to make that foolproof, all participating issuers would need to NOT issue their asset, until there was confirmation of deposit into the shared acct.
So, my long answer, is yes, this is possible, though ultimately boils down to all participants needing to trust the deposit/withdrawal software and all following strict rules of issuing assets.

Ok nice plan B. We have to explain it to everyone.

Basically you create an application which anyone can run on their computers (call it Duck 1.0) which interfaces with the NXT client (and with the BTC client/daemon). Everyone who runs Duck is now a part of the Duck community (much like everyone who runs the NXT client is a part of the NXT community). Duck contains code which was developed (by community consensus and is open source etc.) to perform one main function - to handle/issue a NXT asset which we might call ReserveBTC. Someone (Issuer 1) running Duck can define their own BTC pegged asset - lets call it myBTC1. They can then send the BTC backing their asset to Duck. Someone else (Issuer 2) does the same for myBTC2.

When I want to buy some myBTC1 Issuer 1 sends me some myBTC1. Duck will always buy or sell ReserveBTC, myBTC1, myBTC2 and any other BTC variant because it always has the BTC to back it up/redeem it.

For running the Duck software, the issuers publicly display their trustworthiness which encourages customers and there may be other benefits too.

[BitcoinForumator]

marcus03, wow man thumbs up good work

[Come-from-Beyond]

Any chance of API calls to let NRS do encryption, decryption, signing and verification for clients?

This is insecure, we r moving away of this.

[msin]

@CFB.  I have a question regarding AM.  Can we make messages sent to any particular account public?  I was thinking we could use public messages as a feedback/trust system.  For example, if account "x" was selling something, I could go on blockchain explorer, lookup up that particular account, view public messages sent from previous users who had successfully purchased from account "x".  Thanks.

[pinarello]

CfB,

result of the rewards vote for sites and social media.

would you be so kind to pay the people that won, thank you.

S3MKi               82 (31.3%)
allwelder       57 (21.8%)
Mac Red       42 (16%)
yulkisa       39 (14.9%)
Damelon       13 (5%)
Passion_ltc       11 (4.2%)
Coinonaer       8 (3.1%)
apenzl       3 (1.1%)
Mises_77       3 (1.1%)
pablito89       2 (0.8%)
^[GS]^       2 (0.8%)


1) 50,000
2) 30,000
3) 20,000
4) 5,000
5) 5,000
6) 5,000
7) 5,000
8)3,000
9)3,000
10)3,000
11)2,000

Any chance that u have their accounts ready?

I will provide them to you.

Winners can you sent me the accountnumbers please