But how does my super long password become stronger with a public key? I can only think it has to do with the blockchain and the information it contains. So is this assumption correct? When was this implemented, and when was it made a necessity to have a public key as this seems to be only after new year I read about this. I think it was wrote a lot of times, but I write it again  You password is private key. It is used to generate public key. Then public key is used to generate hash. Then part of the hash became your account ID. Until you get any transaction, there's no account in blockchain. You can "unlock" any number of accounts in client software - it doesn't mean anything for network. So when you get at least one transaction, blockchain store you account ID. But until you send any transaction, it is only account ID, and nothing else. When you send transaction, it is signed with your private key. At the same time public key is send, so other nodes can verify this signature, and verify that you send coins from your own account. So when you send at least one transaction, blockchain store you account's public key. It is by design, and the same scheme is in BTC too for years, except that BTC account ID is 160 bit length, while Nxt uses only 64 bit now. When some thief want to steal your money, he need to find your private key. When you have sent transaction, thief need to generate private key that match you known public key. It is almost impossible. When you have no transactions out, thief need to generate private key that match only account ID. It's hard now, but will be possible in some years. Btw, in Nxt you need not to send coins to make public key available in blockchain. Simplest and cheapest way is to create some alias with 1 NXT fee. Or if you have some amounts of coins just wait until you account forge one block, even empty one. |
|
|
|
Hey gang, Any thoughts on this? https://nextcoin.org/index.php/topic,2418.0.htmlWhen a POST is done with "processBlock", there is no sanity check on "payloadLength". This means, an attacker could use this issue to DoS a node by keeping its heap exhausted all the time. This would trigger various OOM exceptions in other parts of the code. Simple request causing 662.2 megs to be allocated: curl " http://localhost:7874/nxt" -d '{"protocol": 1, "requestType": "processBlock", "version": 1, "blockTimestamp": 666, "timestamp": 666, "previousBlock": "666", "numberOfTransactions": 0, "totalAmount": 666, "totalFee": 1, "payloadLength": 662200000, "payloadHash": "deadbeef", "generatorPublicKey": "deadbeef", "generationSignature": "deadbeef", "blockSignature": "deadbeef"}' * Tested against 0.5.0 Isn't this memory garbage collected? It's not a matter of garbage collections. The problem is that NSR trust some numbers from outside. Dealing with OOME is not that simple... I'm looking through the source, and have strong feeling that payloadLength can be easily ignored at all. Ignored and throwed out from protocol. In generateBlock() local variable is used to check on MAX_PAYLOAD_LENGTH limit, than just set to corresponding block variable. In pushBlock() it is used in checks in the begininng, but checks easely can be done later, on transaction checking. In loading thread and "processBlock" request it is used to create ByteBuffer with desired size, but it's always better to use dynamic-sized buffer anyway, with some checks on max size. In "getNextBlock" request it is used to limit response, but again you can calc it dynamically with transactions. Elsewhere it is just readed from JSON and writed back. |
|
|
|
|
"Немного", ага. На i5-3750 прирост минимум вдвое.
"difficulty" : 167.07290598
|
|
|
|
А кто-нибудь хоть раз видел выпадающий конденсат при выключении фермы в -20 на улице?
Я понять не могу, откуда там влага-то возьмется, которая выпадет?
Так это точка росы, конденсат из воздуха Едрен-крипто-батон, я каждый день горячую машину глушу на улице, никакая роса на ней не выпадает. |
|
|
|
А кто-нибудь хоть раз видел выпадающий конденсат при выключении фермы в -20 на улице?
Я понять не могу, откуда там влага-то возьмется, которая выпадет?
Никакой влаги! Мы говорим о заносе в тепло Какой занос в тепло? Стояла ферма себе работала и вырубилась. Но как стояла на улице так и стоит. Откуда роса? |
|
|
|
so does anyone know about this account 2176239447854173275 sending 1Nxt to a lot of other random accounts?
is it something sneaky going on again? .... ;|
Or it is faucet. |
|
|
|
А вообще есть сейчас работающая с некстами биржа? (dgex, разумеется, не предлагать)
nxtchg.com Но там объемы небольшие. |
|
|
|
might not be the right thread - you can ignore..
right now there's 1 MB needed to store 5000 transactions in transactions.nxt
how compares NXT blockchain size to BTC chainsize in the future? I guess it's similar?
when CfB talkes about possible 1000 ta/s in the future, how can any decentralized network store this?
distributed storage? HD storage and internet bandwith will not scale up infinitely.
In NXT, I believe that there is a maximum blockchain size (meaning, it will never go beyond a certain limit) because of the way proof of stake works. Right now it is 2 31 blocks and 2 31 transactions (due to internal structures, nonsense in perspective), plus usual file size limit (nonsense on any modern FS). |
|
|
|
initializeKeyPair returns an account id that is used to unlock an account.
However, the account number is comprised of only the first 8 bytes of the hash of the account's public key.
It was discussed since the beginning If you do at least one transaction (even alias), account public key will be revealed to blockchain, so it protect you account from stealing. The only problem remains is account ids collision. C-f-B promised that when such collisions appears in real life, devs just increase number of used bytes from hash. So it's not a bug, but a feature. |
|
|
|
might not be the right thread - you can ignore..
right now there's 1 MB needed to store 5000 transactions in transactions.nxt
how compares NXT blockchain size to BTC chainsize in the future? I guess it's similar?
when CfB talkes about possible 1000 ta/s in the future, how can any decentralized network store this?
distributed storage? HD storage and internet bandwith will not scale up infinitely.
Blockchain shrinking was promised by BCNext. Blockchain structure is much simplier in Nxt, than Bitcoin, so it can be programmed with much less effort, I think. |
|
|
|
I would suggest hitting up bybitcoin, Noitev, and buybitcoinscanada. They all seem to have an interest in helping the community.
They do good job selling their stake at the very beginning. At least I remember bybitcoin sell a lot of 1M for 0.6 BTC. I was so stupid, lazy and ignoramus that time... |
|
|
|
For people late to the this thread, I just wanted to remind everyone of a parallel thread going on that also contains a good discussion about the code ( https://bitcointalk.org/index.php?topic=397214.0). It's mostly focused on more minor flaws than this thread, but some good contributions have been made there. I try to focus that thread not on flaws/bugs, but on code quality. I failed a bit because Jean-Luc do a lot of refactorings already, or have some of them in TODO list. I'm still not finished to read code, so maybe there will be some posts more. |
|
|
|
Edit: Wait a minute. Maybe I got a typo..
Yes, you just make a typo |
|
|
|
|
Имхо, если ребята, которые десятками подымали велл-ноун ноды на VPS и RPi, не разбегутся - пока что подымать выделенные ноды больше смысла нет.
А если сделать в клиенте сохранение пиров между перезапусками, как в битке, то и от велл-ноун зависимости будет куда меньше.
ЗЫ: очень хочу увидеть полноценную андроид-ноду с форжингом. Даже интересно, вытянет ли батарейка в мобиле сутки онлайна.
|
|
|
|
Есть 2 свежих входа: 120 NVC и 8 NVC. Чтоб PoS лучше майнился их лучше объединить или лучше не надо?
Ничего не надо делать. Можно чуть подробнее? А что подробней? При нонешней сложности инпут в 120 NVC скорее всего в потолок из 10 NVC не упрётся, если его после 30 дней не залёживать, зато "сработает" быстрее. |
|
|
|
нужен пул.. я спрашивал владельца данного пула coinmine.pl ... он сказал что постарается ... правда уже прошло дня 2 и пака тихо)) ну и нужна команда разработчиков кто будет поддерживать даную крипту.. так как создателя данного фока уже больше 3х месяцев на форуме не видно... ))
а смысл в чем? "difficulty" : 115.16546881 Да, щас если всё бросить, оно дней десять будет до 20.0 падать... А зачем пул - пока что не понятно. У меня щас Core i5-3750, так вполне себе блоки находит один за другим. Думаю, даже на более слабом проце вполне можно соло майнить. |
|
|
|
Loch Ness is best known for alleged sightings of the cryptozoological Loch Ness Monster, also known affectionately as "Nessie".
In cryptozoology and sometimes in cryptobotany, a cryptid (from the Greek κρύπτω, krypto, meaning "hide") is a creature or plant whose existence has been suggested but is not recognized by scientific consensus.
Nessie! Dude, you're genius! Everyone see it, no one can catch it. |
|
|
|
Nice one, but that's not it. The nodes I mean reply with the Nullpointer every time. You can try wget -q -S -O - --post-data='{"protocol":1,"requestType":"getCumulativeDifficulty"}' ' http://node81.nxtbase.com:7874/nxt' this one has been in that state for a few hours now. http://node81.nxtbase.com:7874/nxt?requestType=getState {"lastBlock":"2680262203532249785","numberOfAliases":0, "numberOfBlocks":0,"numberOfPeers":182, "lastBlockchainFeeder":null,"totalMemory":709558272,"freeMemory":637372280,"maxMemory":912261120,"numberOfTransactions":0,"numberOfUsers":0,"version":"0.5.0","numberOfOrders":0,"time":3726746,"availableProcessors":1,"numberOfAssets":0,"numberOfAccounts":0} It's dead, man. Dead and smells bad. Yes, there is some combination of circumstances (aka bug) that prevent a portion of my nodes from never getting the blockchain. I'm not the best with tcpdump but I could probably dig around. This is very unusial situation. Take a look at "getState" query: response.put("numberOfBlocks", blocks.size());There's no call like remove() on blocks collection. Even popBlock() doesn't flush block from it. So it can be empty only because of bad startup. Very bad startup, because even if blocks.nxt doesn't exists or damaged, genesis block is synthesized and putted to collection. Or there may be some new code which we do not have. |
|
|
|
Block class does not contain hashcode of previous block, only block id and pushBlock() does not check anything into this direction. Isn't it possible to modify old blocks afterwards (By the original author of the block)?
It contains prev block hash in 0.5.0. At least I see it in decompiled code. Don't know, is it fixed flaw, or injected. |
|
|
|
Nice one, but that's not it. The nodes I mean reply with the Nullpointer every time. You can try wget -q -S -O - --post-data='{"protocol":1,"requestType":"getCumulativeDifficulty"}' ' http://node81.nxtbase.com:7874/nxt' this one has been in that state for a few hours now. http://node81.nxtbase.com:7874/nxt?requestType=getState {"lastBlock":"2680262203532249785","numberOfAliases":0, "numberOfBlocks":0,"numberOfPeers":182, "lastBlockchainFeeder":null,"totalMemory":709558272,"freeMemory":637372280,"maxMemory":912261120,"numberOfTransactions":0,"numberOfUsers":0,"version":"0.5.0","numberOfOrders":0,"time":3726746,"availableProcessors":1,"numberOfAssets":0,"numberOfAccounts":0} It's dead, man. Dead and smells bad. |
|
|
|
|
Show Posts
