Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 1116. (Read 2761629 times)

hero member
Activity: 597
Merit: 500
correct, this is not a problem for new users or users without unicode keyphrases but don't know how many e.g. chinese users we have now using chinese symbols as keyphrase.
anyway, i am finishing apphub now. it was already planed to include unicode into hive and apphub is part of this.

Is it possible to postpone release a little so other AE client devs catch u?

it's already postponed because i need a little more time to test AE and include the DNA i mentioned before
but since i intend to start 1. march with hive my intension is to realease apphub latest end month, better
a week earlier.
full member
Activity: 350
Merit: 100
If pointing out your last resort of snarks/eyerolls is ignorant and rude, so be it. I just don't think it's productive (neither is my bitching about your bitching, so I should probably just STFU now).

Hey, I don't enjoy sounding like a prick either Sad

Ok, I guess, fair enough. I should probably try one more time to convince him with arguments, instead of just bitching.

So James, consider this:

To test the old system you need to go and ask Jean-Luc to build-in a distributed cryptographic accumulator and then the rest of the libzerocoin via c++/java bridge, all this so you could just see for yourself, how horrible that system is.

Then, in a couple of months, when zerocash comes out, you're gonna come back and ask him to scratch all that and replace it with a distributed Merkle tree and a completely different ZK-proof system, based on SHA256 code, translated by a specially modified GCC compiler into code for a custom VM (which also needs to be implemented in our system, by the way).

Is this your plan? Because, frankly, it doesn't look very practical.

You, sir, are a scholar and a gentleman.

Now I gotta read a dozen cryptopapers to understand most of what you wrote.  Cheesy
full member
Activity: 168
Merit: 100
quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

blah blah...
hero member
Activity: 834
Merit: 524
Nxt NEM

....
bs... bss.. more bs...
...

Please people never forget that our emule is a professional investor...

https://bitcointalksearch.org/topic/m.4260845

he has massively invested in crypto -  Grin Grin Grin Grin Grin

and btw. still dumping?


He already dumped. Now he is waiting for lower price to buy back.

Did the NXT course fall due to that dump ... to 0.00006 BTC or lower  ?
I've inactively followed the course, but lately it has been 0.00007x .. 0.00008x
hero member
Activity: 784
Merit: 500


We must have solid answers for these kind of questions, people on the other crypto are not stupid.

Are you sure?  Wink
hero member
Activity: 840
Merit: 1002
Simcoin Developer
Damn, I missed both 1440 and 1500 Sad
full member
Activity: 180
Merit: 100
I still hope Nxt will have pool forging implemented at some point. come from beyond tweeted about it some time ago.
so everyone gets the same interest % (although very low). that would make it even fair-er.



Its just a concept now, but if NXT distribution will be better it could be a feature.
The concept is about leasing forging power to a Pool (Forging Hub) without sending money to another account.

more details:
https://bitcointalksearch.org/topic/m.4410102

I think that quoted text is very important.

Todays forging is like mining Bitcoins with GPU or altcoins solo mining.

In case I could tell somebody: Nxt is great, you can forge instead of mining and it is so good and future. He will believe me and buy 10.000 NXT. In case he will actually forge every week NXT, he will be so happy and tell it to his friends etc.. This situation will not happend until pooled forging without sending money to the pool will work.

In case price will go up, newcomers will not have enough money to buy even 10k or 1k NXT for forging.

We must have solid answers for these kind of questions, people on the other crypto are not stupid.
legendary
Activity: 2142
Merit: 1010
Newbie
correct, this is not a problem for new users or users without unicode keyphrases but don't know how many e.g. chinese users we have now using chinese symbols as keyphrase.
anyway, i am finishing apphub now. it was already planed to include unicode into hive and apphub is part of this.

Is it possible to postpone release a little so other AE client devs catch u?
hero member
Activity: 597
Merit: 500
quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Good news! When can we test it?  Tongue

this not so good, because as mentioned above existing accounts with unicode keyphrases are not supported this way. this has to be solved.

account holder with unicode keyphases don;t have to use your client till it's fixed.

but new users can begin immediately with your format.

correct, this is not a problem for new users or users without unicode keyphrases but don't know how many e.g. chinese users we have now using chinese symbols as keyphrase.
anyway, i am finishing apphub now. it was already planed to include unicode into hive and apphub is part of this.

member
Activity: 96
Merit: 10

Let sum up what we have finished here:

- Decentralized Alias System / DNS: yes but not Complete
- Basic DDoS Protection: Complete?
- Decentralized Asset Exchange / Colored Coins:NO
- Transparent Mining:NO
- Arbitrary Messaging: Complete but absolete
- Instant Transactions:NO
- Decentralized Marketplace / Auction:NO
- Distributed Storage:NO
- Multi-signatures:NO
- Blockchain Shrinking:NO
- Two-phase Payments:NO
- Voting System:NO
- Reputation System:NO
- Decentralized Mixing Service:NO
- Distributed Computing:NO
- Smart Contracts:NO
- Hardware Wallets:NO
- Advanced DDoS Protection Project Kharo:NO
- white paper: NO
- Client:NO

What do we have:

bloated Blockchain that uses GB's of traffic that no one can afford!
hot air
unclaimed coins
12 laughing rich initial founders.
rats leaving the sinking ship already


hero member
Activity: 840
Merit: 1002
Simcoin Developer
If pointing out your last resort of snarks/eyerolls is ignorant and rude, so be it. I just don't think it's productive (neither is my bitching about your bitching, so I should probably just STFU now).

Hey, I don't enjoy sounding like a prick either Sad

Ok, I guess, fair enough. I should probably try one more time to convince him with arguments, instead of just bitching.

So James, consider this:

To test the old system you need to go and ask Jean-Luc to build-in a distributed cryptographic accumulator and then the rest of the libzerocoin via c++/java bridge, all this so you could just see for yourself, how horrible that system is.

Then, in a couple of months, when zerocash comes out, you're gonna come back and ask him to scratch all that and replace it with a distributed Merkle tree and a completely different ZK-proof system, based on SHA256 code, translated by a specially modified GCC compiler into code for a custom VM (which also needs to be implemented in our system, by the way).

Is this your plan? Because, frankly, it doesn't look very practical.
legendary
Activity: 868
Merit: 1000
Cryptotalk.org - Get paid for every post!
quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Good news! When can we test it?  Tongue

this not so good, because as mentioned above existing accounts with unicode keyphrases are not supported this way. this has to be solved.

The setup using the secret phrase is unfortunately not a universal solution.  It depends on what browser you were using when you set it up.  If you happened to be on windows browser, then you won't have UTF-8 encoding.  So when you walk up to another machine, say an android phone, your pass phrase won't work in certain cases.  

This is just a flaw that really doesn't have a solution.
member
Activity: 67
Merit: 10
Blockchain Explorer shows support in my marketing account for the continuation of website and networking. I very much appreciate it! Thank you.
newbie
Activity: 51
Merit: 0
quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.
Just tell us WHEN?
legendary
Activity: 2184
Merit: 1000
quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Good news! When can we test it?  Tongue

this not so good, because as mentioned above existing accounts with unicode keyphrases are not supported this way. this has to be solved.

account holder with unicode keyphases don;t have to use your client till it's fixed.

but new users can begin immediately with your format.
hero member
Activity: 597
Merit: 500
quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Good news! When can we test it?  Tongue

this not so good, because as mentioned above existing accounts with unicode keyphrases are not supported this way. this has to be solved.
member
Activity: 80
Merit: 10
NXT AROUND THE WORLD in 8 MINUTES!



What do you guys think about this IDEA.

https://nextcoin.org/index.php/topic,3807.msg36016/topicseen.html#msg36016


Nice Idea! If we can make a nice video of this. It'll be awesome!
legendary
Activity: 2184
Merit: 1000
NXT AROUND THE WORLD in 8 MINUTES!



What do you guys think about this IDEA.

https://nextcoin.org/index.php/topic,3807.msg36016/topicseen.html#msg36016
member
Activity: 80
Merit: 10
quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.

Good news! When can we test it?  Tongue
hero member
Activity: 597
Merit: 500
quick apphub update.

have tested all basic functions account/alias/amessage (asset exchange close to complete) so far and it's working as expected, fast and stable but
there is a problem with keyphrases containing unicode characters. utf-8 encoding at codelevel is working but the gui engine supports iso 8859-15.

working on this.
Jump to: