 Show Posts
|
|
Pages: [1] 2 3 »
|
I really recommend looking into the full paper: https://www.hertzbleed.com/hertzbleed.pdfThey point to the paper "Luca De Feo, Nadia El Mrabet, Aymeric Genêt, Novak Kalud̄erović, Natacha Linard de Guertechin, Simon Pontié, and Élise Tasso. SIKE channels. Cryptology ePrint Archive, Report 2022/054, 2022." https://eprint.iacr.org/2022/054 which describes the main problem: a zero-value attack on the crypto algorithm. It is possible to construct input data for the algorithm SIKE where it can get on a sequence of all zeros in its calculation. They do describe in section 5 countermeasures. Only because the selected crypto algorithm generates a sequence of calculations with zeros is there a big difference in CPU calculations, which lead to the CPU changing frequency. I don't see for now a general problem. Nonetheless software developers should be aware of this type of attack. |
|
|
|
Currently, IOTA is around $ 2.173. The one-year forecast is around $ 11. This means from the current price, it will rise almost fourfold. The iota price prediction for 5 years is $ 38. This means that from the current price, it will be able to increase significantly. This is the reason why it is one of the best cryptocurrencies to invest in currently. Also, a credit investment of $ 100 will be around $ 1782 in 2022. This marks a 17 fold increase. This is the reason why many of the investors are looking to invest in this cryptocurrency. https://smartereum.com/3358/iota-price-predictions-2018-the-cryptocurrency-iota-price-iota-coin-iota-cryptocurrency-news-4-march-sun/Wow! This link now passes on to: https://smartereum.com/3358/iota-price-predictions-2019-the-cryptocurrency-to-look-upwards-iota-forecast-iota-news-today-iota-cryptocurrency-news-mon-apr-15/So they updated their predictions from a year ago. The new predictions are: IOTA price prediction for 5 years is $ 38.
This is the reason why currently it is one of the best cryptocurrencies to invest in. Also, a credit investment of $ 100 will be around $ 1782 in 2022. This marks a 17 fold increase. All these predictions catch the attention of the investors who are looking to invest in this cryptocurrency. Ok, so it is still $38 in 5 years? Now it is 2019. 2022 is in 3 years. So I guess the original price prediction to push IOTA was really from 2017. Just removing obviously false sentences. |
|
|
|
IOTA team: How about us responding to the attack? We still think an attack would not be successful.
DCI: We are done with you, don't insult us. We are going to publish.
I guess you forgot to mention the: IOTA team: Neha, are you sober? just before the don't insult us. |
|
|
|
|
If you just want to have a Catcoin post an address and I'll send you one.
|
|
|
|
And just to put something into perspective for you, when we started the ZEIT Knights, the price to attain 100 Million coin requirement was only ~$75 US. Now the price to attain 100 million coin requirement is ~$5753 US So saying our price has not changed verses fiat is incorrect on your part.  Just to put something into perspective for you: ZEIT is at the moment on cryptopia at an exchangerate of 1 Satoshi, because that is the lowest possible exchange rate there. Your price increase was achieved by waiting for Bitcoin to rise so that the lowest possible exchange rate rises. If you look at the sell orders you see 15 million ZEIT for this lowest possible exchange rate and halve a billion for 2 Satoshi. On the buy orders side you see exactly nil, nada, nothing. The same on coinexchange. And there is really nothing done to improve this. Just sitting back and waiting for success to appear magically. Just writing as an owner of 20000 ZEIT for playing with a POS coin |
|
|
|
|
There are 62 libboost-dev packages!
But luckily I got it compiled by downgrading libssl-dev (version 1.1) to libssl1.0-dev. So it is probably this API change in OpenSSL. It broke a lot of software. After starting it did synchronize VERY quickly, but then it stopped at 1 hour behind. Processed 121171 blocks. At the moment it has 4 peers, three with 0.9.3 and one with 0.9.2. I started a verifychain. Maybe there is an issue.
Thanks.
PS: Or maybe the problem was the chain itself? Now I am up to date with 121172 blocks.
|
|
|
|
|
Yes, I am running Debian 9.2. I can't compile the CLI and the QT version. Both have problems with errors in bignum.h. I heard about an API change in OpenSLL. I assume that is the reason for this. Stretch has OpenSSL version 1.1.
The error messages are all like:
bignum.h: In function 'bool operator>(const CBigNum&, const CBigNum&)':
bignum.h:588:83: error: cannot convert 'const CBigNum*' to 'const BIGNUM* {aka const bignum_st*}' for argument '1' to 'int BN_cmp(const BIGNUM*, const BIGNUM*)'
operator>(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) > 0); }
^
(the pointer points to the last ")" in the previous line)
or for the QT version e.g.:
rc/base58.h: In function 'bool DecodeBase58(const char*, std::vector<unsigned char>&)':
src/base58.h:100:42: error: cannot convert 'CBigNum*' to 'BIGNUM* {aka bignum_st*}' for argument '1' to 'int BN_mul(BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)'
if (!BN_mul(&bn, &bn, &bn58, pctx))
^
(pointer pointing to the ")" before the last ")")
|
|
|
|
|
Will there be a version which compiles in new Debian Stable?
|
|
|
|
|
Deleted yesterday again the blockchain and started new with 3.0.1. Today all is fine! Thanks.
|
|
|
|
|
Thanks for the new release.
Have now 3.0.1 running for about halve a day. Have made addnode for a lot of the 3.0.1 IPs. When I started it there where three 3.0.0 peers. One or two hours later two addintional 3.0.1 peers which had no newer blocks. Now I am back to only three 3.0.0 peers and still no newer blocks. Will let it run. Hopefully it will catch up.
|
|
|
|
After running 2.0.0 recently I had problems syncing. So I downloaded the blockchain from the first posting and kept the wallet.dat. Same problem. Stops two days ago. So I dumped my complete blockchain and kept the wallet.dat. Still same problem. The change from good to bad is here: 2017-06-12 06:29:29 Block:CBlockIndex(pprev=0x7effcc6620c0, nHeight=263563, merkle=afe6b8242cbf55cd0d314ad700ba7dc1a203f305b5692908a03e25e7f8488eb2, hashBlock=
00000022dc8b3454c01a2f41acf30522ed5916ae747da7aaeb8d73ea3cddcbcf, nNonce=9102, nTime=1497004161, location=181639, finalcalculation=3466460353)
2017-06-12 06:29:29 UpdateTip: new best=000000196028bbe4106503223374025ed3c05b676dca913521174b2df4a3df7c height=263564 log2_work=42.03274 tx=527478 date=20
17-06-09 10:29:55 progress=0.994632 cache=51.1MiB(236282tx)
2017-06-12 06:29:29 Block:CBlockIndex(pprev=0x7effcc6621d0, nHeight=263564, merkle=be1de94570219064b6aedb92b38c857c21ae6a5ad003d6e79bee360884c78bcc, hashBlock=
000000196028bbe4106503223374025ed3c05b676dca913521174b2df4a3df7c, nNonce=391, nTime=1497004195, location=145891, finalcalculation=270786450)
2017-06-12 06:29:29 UpdateTip: new best=000001b2a918550c53abd3dd8b5bba31d0bdbe4d
0611de6da4b056958de06b96 height=263565 log2_work=42.032743 tx=527479 date=2017-06-09 10:34:57 progress=0.994638 cache=51.1MiB(236283tx)
2017-06-12 06:29:29 Block:CBlockIndex(pprev=0x7effcc6622e0, nHeight=263565, merkle=7ff54c14374342920d52f7a94234b794170838a13f57c9d1ce21ab40c36c2072, hashBlock=000001b2a918550c53abd3dd8b5bba31d0bdbe4d0611de6da4b056958de06b96, nNonce=7958, nTime=1497004497, location=239772, finalcalculation=2902672910)
2017-06-12 06:29:29 UpdateTip: new best=000000067097c568a158f9c379b2b5a47cea881683001407a7c354f1b687d1fa height=263566 log2_work=42.032745 tx=527480 date=2017-06-09 10:34:58 progress=0.994638 cache=51.1MiB(236284tx)
2017-06-12 06:29:29 Block:CBlockIndex(pprev=0x7effcc6623f0, nHeight=263566, merkle=9c08d4eedf8d2ceb16d71443d5724e3c1784c206019fdba4196df00f655fb588, hashBlock=000000067097c568a158f9c379b2b5a47cea881683001407a7c354f1b687d1fa, nNonce=3008, nTime=1497004498, location=178589, finalcalculation=3131149817)
2017-06-12 06:29:29 ERROR: CheckInputs(): d4858b0970b57a97e266f8d61635144dc1d7435e080e637db40a0c104f7bde90 value in (0.00242305) < value out (0.06149373)
2017-06-12 06:29:29 Misbehaving: 71.226.74.120:1989 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-06-12 06:29:29 InvalidChainFound: invalid block=0000007695c99b3f795f9a6c6487a583fdc857f9db0ab6c395d41e49b3e8ae0b height=263567 log2_work=42.032748 date=2017-06-09 10:48:41
2017-06-12 06:29:29 InvalidChainFound: current best=000000067097c568a158f9c379b2b5a47cea881683001407a7c354f1b687d1fa height=263566 log2_work=42.032745 date=2017-06-09 10:34:58
2017-06-12 06:29:29 ERROR: ConnectTip(): ConnectBlock 0000007695c99b3f795f9a6c6487a583fdc857f9db0ab6c395d41e49b3e8ae0b failed
2017-06-12 06:29:29 InvalidChainFound: invalid block=0000007695c99b3f795f9a6c6487a583fdc857f9db0ab6c395d41e49b3e8ae0b height=263567 log2_work=42.032748 date=2017-06-09 10:48:41
2017-06-12 06:29:29 InvalidChainFound: current best=000000067097c568a158f9c379b2b5a47cea881683001407a7c354f1b687d1fa height=263566 log2_work=42.032745 date=2017-06-09 10:34:58
2017-06-12 06:29:29 receive version message: /HOdlcoin:3.0.0/: version 250000, blocks=265084, us=46.85.20.134:41361, peer=43
2017-06-12 06:29:36 receive version message: /HOdlcoin:3.0.0/: version 250000, blocks=265084, us=46.85.20.134:38682, peer=44
2017-06-12 06:31:23 ERROR: AcceptBlockHeader: block is marked invalid
2017-06-12 06:31:23 ERROR: invalid header received
2017-06-12 06:31:23 ProcessMessages(headers, 178003 bytes) FAILED peer=41
2017-06-12 06:31:24 ERROR: AcceptBlockHeader: block is marked invalid
2017-06-12 06:31:24 ERROR: invalid header received
2017-06-12 06:31:24 ProcessMessages(headers, 178003 bytes) FAILED peer=28
2017-06-12 06:31:29 ERROR: AcceptBlockHeader: block is marked invalid
2017-06-12 06:31:29 ERROR: invalid header received
2017-06-12 06:31:29 ProcessMessages(headers, 178003 bytes) FAILED peer=32
2017-06-12 06:35:54 ERROR: AcceptBlockHeader: block is marked invalid
2017-06-12 06:35:54 ERROR: invalid header received
2017-06-12 06:35:54 ProcessMessages(headers, 178003 bytes) FAILED peer=28
2017-06-12 06:35:55 ERROR: AcceptBlockHeader: block is marked invalid
2017-06-12 06:35:55 ERROR: invalid header received I use 3.0.0 on Linux. |
|
|
|
Oder wenn ich mal wieder in Wien bin.  |
|
|
|
|
Ich wollte gestern zwei Kollegen dorthin einladen um mal mit Bitcoin zu bezahlen. Leider haben wir es dort, wo es sein sollte, nicht gefunden. Ich nehme an, dass es zugemacht hat. Bloed gelaufen.
|
|
|
|
|
I just wanted to do the Real Thing. Paying by CC is paying by CC.
|
|
|
|
|
I wanted today to eat at the restaurant here which accepts Bitcoin. It wasn't there anymore! That's what stopped me using Bitcoin today. And I probably never ever will get a chance to pay in a restaurant with Bitcoin.
|
|
|
|
|
I got with 250kHps in about 20 days nil, nothing, nichts, nada. So I finally stopped my catcoin mining.
|
|
|
|
Probably someone with access to a large amount of computers, a school or lab or so Wow! It really got up! |
|
|
|
|
Probably libjansson-dev missing, or whatever it is called in Ubuntu.
|
|
|
|
|
I think these are all IPs I have ever seen:
"addr" : "108.61.10.90:9933"
"addr" : "109.182.144.114:9933"
"addr" : "146.0.32.101:9933"
"addr" : "167.160.36.82:9933"
"addr" : "173.254.235.58:9933"
"addr" : "69.118.78.156:9933"
"addr" : "98.115.147.74:9933"
|
|
|
|
|
I got the two IP from the initial posting in this thread in my catcoin.conf. I don't get the entries you get, just something like:
2016-03-27 10:38:14 trying connection 96.125.240.228:9933 lastseen=6550.5hrs
2016-03-27 10:38:19 connection timeout
which I assume is ok. With just 7 connections it is probably trying to find more.
But I am now mining at least 6 times the expected time to find a block hash without any result. It is probably more likely that here is something wrong than it is just bad luck.
|
|
|
|
|
