Did you want some TestNxt ?
yes please 8792941012231216832 Sent 3,5 K TestNxt. Enjoy it  |
|
|
|
|
Did you want some TestNxt ?
|
|
|
|
Currently, there is only 1 account that is able to forge at a certain time.
In the future, there shall be n accounts to do so in order to avoid DoS attacks.
Hmm, I need to look up where I read that...
Forging Groups. Forging Groups = Pool ...( it's similar ) |
|
|
|
I'll try again...
Would one solution be to have a sequence of nodes, where the next 'n' forging nodes are always known not necessarily in parallel but in close sequence, so node 1 identifies node 2 and node 2 identifies node 3 (based on 1 & 2), node 3 identifies 4 (based on 1,2,3), this would create a forging mesh within the network and clients could choose which node to send to based on latency and forging window. (mobile networks and phones do something like this all the time - yes I know about dropped calls its not perfect!)
The choice of node not just based on the current params but also its awareness of the network topography would mean a continual distribution of nodes resulting in statistically a node being close in latency and forging window to a client that wanted to transact...
Depending on the capacity required the nodes would seek an optimum connection with other nodes to achieve that capacity, also if the network can advertise its current processing capacity based on its current demand and ask for more nodes who might be sleeping because not needed before.
You don't have to deploy static network models like hub/spoke or regional or whatever...
Normally people think the a system is stronger than any one single part but what I read here is how for a moment one part has to stand out from all the rest and that makes it vulnerable.
This is why we need groups of forging accounts. groups of forging accounts = Pool  |
|
|
|
well said NxtMinnow. came to the same conclusion. following ethereum also from beginning and there are some nice ideas but mostly as concept/ideas,
nxt is here and now, no reason to overestimate ethereum. Q4 2014 is planned to launch but i guess we won't see them before Q1 2015. ethereum is also
more gearing into financial api, mostly usefull for old school finance, therefore the big interest from this side but nxt is far more people/user orientated.
nxt will have all they want fully operational before they launch thier basic structure.
Speaking of, how is your client coming along? working at the AE client atm. testing and balance tracing is going on but close to finish. the apphub client needs to refactor, enabling a distributed applications approach. means only the account handling is included make it max lightweigthed. alias and AM and some additional tools are loadable modules on demand via a distributed application layer. Did you want some TestNxt ? |
|
|
|
So... more nodes ?
It doesn't *change* the *latency* to have more nodes. The latency is due to the physical hardware of the internet itself and some of the software (in particular things like the GCF) that sit at the fairly low levels above that. Adding "more hops" can actually only make things *slower*. then What's the solution ? |
|
|
|
I proposed a simpler method, but CIYAM said it was impossible.
Do you think using current method (without the random factor) we can simply reduce the time between blocks to 50 seconds? 30 seconds? 10 seconds?
James
We can reduce. But if u set gap between blocks to 10 sec then u'll need 6 times more confirmations to get the same reliability. So... more nodes ? |
|
|
|
in what cases would you use broadcastTransaction API? Is it only for light-clients to use to send to a full node? I thought we were saying before that if some forger never picked up your transaction you could use broadcastTransaction to resend it, but that requires full bytes of the transaction, and you cannot obtain that unless you pull it from the blockchain, which means it is already *in* the blockchain.
I dont understand?
And can someone get me some testnxt please? 16155265664111966451
Some TestNXT to 15004211867702614232 Please!
Sent 5K TestNxt , enjoy it  . |
|
|
|
could you send me some more please? -> 9998590259914237067
- 20k testNXT sent! @ AE devs, did you made a balance tracking already and if so did you found any diffs between your filled/cancel orders if you unroll them back to inital balance? ps: thx abctc Unconfirmed balance bug is not fixed yet. hey, thanks for the testNXT! Hi , did you receive the 5K TestNxt ? From this address 4940924250576724047 ?? |
|
|
|
How to start 0.8.3? java -jar nxt.jar does not work. Error: no main manifest attribute, in nxt.jar
create start.bat with the following... java -Xmx1024M -cp nxt.jar;lib\*;conf nxt.NxtAlready got it running on Ubuntu: 1. chmod +x run.sh 2. ./run.sh EDIT: Server is running but I can not login into my accounts. After I entered the password, nothing happens. On HTTP it words, but on HTTPS not. Strange... use this : |
|
|
|
How to start 0.8.3? java -jar nxt.jar does not work. Error: no main manifest attribute, in nxt.jar
try this java -Xmx1024M -cp nxt.jar;lib\*;conf nxt.Nxt |
|
|
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Release 0.8.3 http://download.nxtcrypto.org/nxt-client-0.8.3.zipsha256: 9a59c60336e01e87a3a1484697dd35a57d8782747145f8049496e19cbffdd537 Change log: Fixed UI problems with display and updates of My Transactions. Consistent counting of transaction confirmations. Transactions included in the last block are considered having 0 confirmations. When a block is pushed, the BLOCK_PUSHED event is now emitted before the REMOVED_UNCONFIRMED_TRANSACTIONS and ADDED_CONFIRMED_TRANSACTIONS events. Added BlockchainProcessor.RESCAN_BEGIN and RESCAN_END events, triggered before and after a re-scan (not the regular start-up scan). Fixed a few null pointers caused by bad peer data. Improved handling of peer addresses and hallmarks. Added blacklisted status to peer info. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJTDkldAAoJEFOhyXc7+e2Ag+AP/2Loj424Fy7FWFC3Nr8xD9Y2 RaMaG8qSX6sKnSmvzp6ogLQF9RwNRdR+7ebhUjOB4NaObT2VcVFP6GUHpzXEQH+J v44pV/odFTzlnRCgGWREzteUmjG01xyoSpp7CEaqd8ZSnvFuLg0MCq2viHhCIg0M /tEYLK7RmrcGMrsPOUutg3xME1ERoRC1YjuMPCCJSSP9JHm2L7D2S4LxvH+xQT8x OwPoKXmgsMn8nXsudMRWMyVAwzpYT4AkgUqXYzsLBMeVKcLePfbwgqzMT6Z9IKUR MTStGn3dXYsm7+2n2zP+oDy1ob3FKGlnMmqa/BaHZySpwTLD0kebPLRVjkgoj3eD 2apwugeeP84eLVKy7o1LApRXrVSYdw3MW/ZIDe2H/8LF3HaHuINNXSAgX3aslvyR kJxkcRyAFl9C7nT0mSH2vUAHk3n3hA/1meuJ4rCOw03JxI3wMjJGjR4sHtWO4ik3 r7I4UywzG89ABXZOAM9Q7ItO3NL5HdrcGfsDSc0hVZehqKYDHOZSdrPpb03rJont NOYxo4oEsf8DGOLFiLtYGN9zCtWkjsVl3fKMvVmRIqutz/VqSXL2kQIdVR6oUI9k QMBXMUfzXAiEcOdYPx0VjqaJmbitLVF0qXL+TByTkROzP7TRYqJHWdCzqiAA3Jr3 9UpvYGW111MyHY53Hcyf =7618 -----END PGP SIGNATURE----- Thanks |
|
|
|
If someone need testNXT, write here, or PM me.
Yesterday I've tested AE a bit.. no problem found yet. You can try to buy some of my ABCs on testnet.
I could use some TestNXT, thanks! 7502128414076890972 If someone need testNXT, write here, or PM me.
Yesterday I've tested AE a bit.. no problem found yet. You can try to buy some of my ABCs on testnet.
could you send me some more please? -> 9998590259914237067 thx abctc me 2, please 14982679201235752929 Sent 5K TestNxt , enjoy it . |
|
|
|
If someone need testNXT, write here, or PM me.
Yesterday I've tested AE a bit.. no problem found yet. You can try to buy some of my ABCs on testnet.
could you send me some more please? -> 9998590259914237067 thx abctc If someone need testNXT, write here, or PM me.
Yesterday I've tested AE a bit.. no problem found yet. You can try to buy some of my ABCs on testnet.
Please man, some here 2457591381965084256 , Let me test, Prease. Sent 5K TestNxt , Enjoy it . |
|
|
|
If someone need testNXT, write here, or PM me.
Yesterday I've tested AE a bit.. no problem found yet. You can try to buy some of my ABCs on testnet.
May I ask what is your address number ? |
|
|
|
he says his second book will be called: How Bitcoin failed and how we can get the Next one right. So he knew about Nxt in September  Interesting. One of the guys who were sitting there could be BCNext... It can be BCnext .. maybe ... |
|
|
|
So it's Andreas? (I don't understand what he is talking about) he says his second book will be called: How Bitcoin failed and how we can get the Next one right. So he knew about Nxt in September He just said || Next ||, we do not know he was referring to NXT  |
|
|
|
@all: Where did you obtain your knowledge regarding the used algorithm in Nxt?
You should ask to Jean-Luc |
|
|
|
That's why WE need to start spreading the Nxt even in cities, in schools and in every place.
Let's create a Nxt virus and spread it via e-mail powerpointpresentations hahaha why not ?? |
|
|
|
I don't get your idea, or I get it. I don't know.
Instead of leasing forge power, you commit with your account to share fees among others in the same "share fee group" if you forge a node. You still try to forge a block on your own, but you commit to share the incentive with others if you are successful (with special conditions like committing to run the node for some time, ...). Could this be done with AT and would that make sense?
there really isnt much point in this mechanism. what you are describing is basically a rube goldberg contraption that produces the exact result of current NXT account/network forgingThe idea is that all forgers repeatedly get small incentives for trying to forge. It is a pure psychological reason.In the end, the fee distribution is the same. exact! But it is very important to keep alive the interest of forging every day because we want two things; every day we must keep network secure every day we must keep maximum decentralized network That's why WE need to start spreading the Nxt even in cities, in schools and in every place. |
|
|
|
|
Show Posts
