 Show Posts
|
|
Pages: « 1 2 [3] 4 5 »
|
I tried to compile the latest source from github for linux and the version i obtain is "0.2.3.1 [BDB]", i want to get the same version than windows "0.2.3.1 [LLD]". How can i obtain the 0.2.3.1 LLD version from github?
I found how to do, so for others who want to compile the LLD version here how to do: instead of compiling using : make -f makefile.unix use : make -f makefile.unix USE_LLD=1 I think it should be integrated in the compile option of the linux build info (doc/build-linux.MD) in github |
|
|
|
|
I tried to compile the latest source from github for linux and the version i obtain is "0.2.3.1 [BDB]", i want to get the same version than windows "0.2.3.1 [LLD]". How can i obtain the 0.2.3.1 LLD version from github?
|
|
|
|
Happy birthday OK Cash!!!  It was a fuckin' good year  Hope a lot of PIMPers are still around  |
|
|
|
I've some question about the roadmap and the airdrop (which is the same thing in fact  ) How do you intend to add value to your token if your only project is an airdrop? Why do you need 11 Dev for just an airdrop? And most important 34% of the airdrop go to Italian locals folk but how do you go to proof that's not you and your buddies who's going to get a free 34% to dump on sheep? I still plan to participate in the airdrop but there are still some concern to have. |
|
|
|
Joined airdrop, Thanks |
|
|
|
|
Just to clarify a few things:
Findcoin network has always been a bit shaky, especially with only 3 or 4 people keeping it alive.
I have seen this happen several times during the year (more than 5 times) and I think this is due to posv1 protocol that accumulates the coinage, so if a person with lots of old stacked coin (more than 100 split) start his wallet once every 1 or 2 months, and opens his wallet for staking before having finished downloading the entire blockchain a fork occurs. Dev Findcoin is no longer here and thus no more checkpoint and therefore fork.
I advise anyone who has made a transaction on 01/29 restart the daemon or qt with -rescan option (eg findcoin-qt.exe -rescan) to see if the coin are getting through or not.
|
|
|
|
|
I've checked my findcoin debug.log after i've seen a lot of orphan in my transaction list.
I think the blockchain had a fork or was attacked, on 01/29 at 20:08 GMT my debug.log shows that my blockchain reorganize:
REORGANIZE
REORGANIZE: Disconnect blocks 300; 3ee2393e4814c1f6d8c9(block 226617)..42baf9bf84bd896a8476(block 226917)
REORGANIZE: Connect 45 blocks; 3ee2393e4814c1f6d8c9(block 226617)..6bd3f383ff1b2d3f6d81(block 226662)
3ee2393e4814c1f6d8c9 = block 226617 at 08:51 GMT (common chain)
6bd3f383ff1b2d3f6d81 = block 226662 at 20:08 GMT (new chain)
And if you look at the blockexplorer we see block 226618 was generated at 19:44 GMT
So every transaction made between the 01/29 at 8:51 GMT and 19:44 GMT are null
|
|
|
|
|
Is there a way to have an armv7 build (Odroid, Raspberry Pi 2) for the next release?
|
|
|
|
Ok, we are on forks now. I finally sync to block height 1051199. The block info matches with the blockchain explorer: {
"hash" : "0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e",
"confirmations" : 1,
"size" : 456,
"height" : 1051199,
"version" : 4,
"merkleroot" : "7c9654256dfcf5df770792291d4c046ec7437259afdb10c947d15ac481027646",
"mint" : 0.44082100,
"time" : 1427468644,
"nonce" : 0,
"bits" : "1d2061fc",
"difficulty" : 0.03088017,
"previousblockhash" : "3ff511bee5c904af9efe85dc468c1bbd93034714f0afd8316af684e913ccf777",
"flags" : "proof-of-stake",
"proofhash" : "00003097b04a19889b8b7f8b877182c7377a060cac47d191abb27e66f4af4e1f",
"entropybit" : 0,
"modifier" : "08c3f63cea5ac37a",
"modifierchecksum" : "f81eee14",
"tx" : [
"81bb88e2761b7c29e4e8d9d25dedafe6ac422f3468e203de0f5dc46426c7695a",
"2285803fc773fb19a9203b81d25d436d2c29bca040c000c19d85941931d3b401"
],
"signature" : "3046022100a43a1a1cd87875c991e6dcaa11bae24ecdd5ae6a20db4902645753e31f217b3c02210 0e9d3e58f1c910ea03378b93830fd3f689e674dad36e4bc50409b18aaa0f60c67"
}
And according to the blockchain explorer, we have at least 7 forks at block height 1051200. Each one has different block hash and different time stamp. That is why my wallet cannot go further beyond block height 1051199. Bittrex’s wallet should have the same issue. https://bittrex.com/StatusSince someone raised a concern about potential attack, I’d suggest to have Jan sync to block height 1051199 first (if he has not done so) and have him to mine 1051200 onwards until he feels comfortable he should be the largest chain. This will kill all other forks currently mining from 1051200 along with attacks (if any) on these forks. And more importantly, all funds on Bittrex will be safe. We need to protect investors currently buying this coin too. Why Jan? Just because everyone here trusts him and I suppose there is no motivation for him to attack the network.  Everyone agrees with it? Agreed Thank you sir. Agreed. do i need to stop my Raspberry which are stuck at block 1051199? Check if your block hash for 1051199 matches with the blockchain explorer or not first (just to play safe). If it does match, just keep your Raspberry running unless Jan asks you to stop. If it doesn’t match or it already syncs beyond 1051200, stop your Raspberry immediately. P.S.: Everyone please check block hash now. Don’t just check block height. Block heights are meaningless under the current fork situation. For example we already have at least 7 different block hashes for the same block height 1051200. Block hash: getblockhash 1051199
0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e Confirm it is the same block as in the blockexplorer. Same block here. |
|
|
|
Ok, we are on forks now. I finally sync to block height 1051199. The block info matches with the blockchain explorer: {
"hash" : "0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e",
"confirmations" : 1,
"size" : 456,
"height" : 1051199,
"version" : 4,
"merkleroot" : "7c9654256dfcf5df770792291d4c046ec7437259afdb10c947d15ac481027646",
"mint" : 0.44082100,
"time" : 1427468644,
"nonce" : 0,
"bits" : "1d2061fc",
"difficulty" : 0.03088017,
"previousblockhash" : "3ff511bee5c904af9efe85dc468c1bbd93034714f0afd8316af684e913ccf777",
"flags" : "proof-of-stake",
"proofhash" : "00003097b04a19889b8b7f8b877182c7377a060cac47d191abb27e66f4af4e1f",
"entropybit" : 0,
"modifier" : "08c3f63cea5ac37a",
"modifierchecksum" : "f81eee14",
"tx" : [
"81bb88e2761b7c29e4e8d9d25dedafe6ac422f3468e203de0f5dc46426c7695a",
"2285803fc773fb19a9203b81d25d436d2c29bca040c000c19d85941931d3b401"
],
"signature" : "3046022100a43a1a1cd87875c991e6dcaa11bae24ecdd5ae6a20db4902645753e31f217b3c02210 0e9d3e58f1c910ea03378b93830fd3f689e674dad36e4bc50409b18aaa0f60c67"
}
And according to the blockchain explorer, we have at least 7 forks at block height 1051200. Each one has different block hash and different time stamp. That is why my wallet cannot go further beyond block height 1051199. Bittrex’s wallet should have the same issue. https://bittrex.com/StatusSince someone raised a concern about potential attack, I’d suggest to have Jan sync to block height 1051199 first (if he has not done so) and have him to mine 1051200 onwards until he feels comfortable he should be the largest chain. This will kill all other forks currently mining from 1051200 along with attacks (if any) on these forks. And more importantly, all funds on Bittrex will be safe. We need to protect investors currently buying this coin too. Why Jan? Just because everyone here trusts him and I suppose there is no motivation for him to attack the network. Everyone agrees with it? Agreed Thank you sir. Agreed. do i need to stop my Raspberry which are stuck at block 1051199? |
|
|
|
Hi community, There is a big problem! Now for 7 hour wallets don't synq! Here a picture I just took from my PI  I hope EenrgyCR is active and can solve the problem. Can others olso take action? Same problem here, it seems like the blockchain is blocked. I've 17 connections and 13 are stuck at block 1051199 and the others are at block inferior. So nobody has passed block 1051199. Need dev asap to check this. |
|
|
|
Not loading on Firefox 36.0.1 "NetworkError: 404 Not Found - https://horizonplatform.io/js/jquery.min.js" jquery.min.js TypeError: $ is not a function $("table").addClass("table table-striped table-condensed").wrap('<div class="tab... ?page=g...h=nodes (Zeile 629, Spalte 2) TypeError: $ is not a function $("#graphlinks").show(); ?page=g...h=nodes (Zeile 561, Spalte 4) Both loading fine for me. with Firefox 36.0.4 |
|
|
|
Did you open your port in your firewall?
sudo iptables -A INPUT -p tcp -d 0/0 -s 0/0 --dport AeroMe_Port_Here -j ACCEPT
Yes, I open port in firewall and still 0 connections  try: addnode=23.25.245.218 in your aerome.conf |
|
|
|
Hi
I have problem with RaspberryPi wallet. Everything build fine, but when I run wallet I have 0 active connections. I Create aerome.conf file but without any result. Please give me some nodes or conf example.
Did you open your port in your firewall? sudo iptables -A INPUT -p tcp -d 0/0 -s 0/0 --dport AeroMe_Port_Here -j ACCEPT |
|
|
|
So the amount of SDT created increases faster than SDC are destroyed?
How does that work dasource?
From what i heard on irc: It's because each time you make a transaction SDT to SDT, you increase the number of SDT available for new ring-sig without destroying any SDC. thanks waecrum that's ingenious Here's the exact quote from SDCDev on irc: Mar 02 14:36:00 <@SDCDev> mmm SDT->SDT would increase it, SDC->SDT would increase it, SDT->SDC is just converting back to normal funds anonymously |
|
|
|
Thank You Dasource ! With regards. Cornett So the amount of SDT created increases faster than SDC are destroyed? How does that work dasource? From what i heard on irc: It's because each time you make a transaction SDT to SDT, you increase the number of SDT available for new ring-sig without destroying any SDC. |
|
|
|
I have most of my NFD on BTER. Even before the hack there were problems with withdrawing and I failed to get them out then.
Can someone push on them to make it possible to retrieve NFD from there?
+1 I have same probleme The problem with withdrawal NFD funds, was almost a month ago. Now the problem isn't present - 2 weeks ago quickly and without problems I withdraw NFD. Try now - everything shall work Here's the message i get when i try to withdraw: NFD withdrawal is disabled 因技术维护，虚拟币提取暂停，感谢您谅解和支持。 |
|
|
|
I have most of my NFD on BTER. Even before the hack there were problems with withdrawing and I failed to get them out then.
Can someone push on them to make it possible to retrieve NFD from there?
+1 I have same probleme |
|
|
|
|
