Rols
|
|
December 18, 2016, 11:16:17 PM |
|
Sorry to say, but Windows version still crashes when mining: [/quote Hm that error maybe have something to do with orphanes.
|
|
|
|
|
|
Once a transaction has 6 confirmations, it is extremely unlikely that an attacker without at least 50% of the network's computation power would be able to reverse it.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
gjhiggins
Legendary
Offline
Activity: 2254
Merit: 1278
|
|
December 18, 2016, 11:55:19 PM |
|
Hm that error maybe have something to do with orphanes.
pictureshack.ru is inaccessible atm but peering at the image reveals a boost exception with the unedifying message: “The attempted operation is not supported for the type of object referenced.” At least there *is* an error message, it's a starting point. * gjhiggins wanders off to investigate whether wine can still install Qt, one never knows. Cheers Graham
|
|
|
|
ArchitektoR
|
|
December 19, 2016, 01:11:53 AM |
|
pictureshack.ru is inaccessible atm
main ESXi with router stuff crashed to PurpleScrrenOfDeath, now rebooted and link restored (it was mining SlimCoin in the meanwhile on one of the VMs... so debug logs some time later, just recovered all VMs).
|
|
|
|
casper77
Legendary
Offline
Activity: 2884
Merit: 1035
|
|
December 19, 2016, 01:41:26 AM |
|
gjhiggins, are you going to revive Fantom (FNX) ?
|
|
|
|
ArchitektoR
|
|
December 19, 2016, 02:24:36 AM |
|
here is a debug.log around crash 2016-12-19 01:45:49 UTC RandAddSeed() 150364 bytes 2016-12-19 01:45:49 UTC received: inv (37 bytes) got inventory: block fd7dc464a207ec9f1d14 new askfor block fd7dc464a207ec9f1d14 0 sending getdata: block fd7dc464a207ec9f1d14 2016-12-19 01:45:49 UTC sending: getdata (37 bytes) 2016-12-19 01:45:50 UTC received: inv (37 bytes) got inventory: block fd7dc464a207ec9f1d14 new askfor block fd7dc464a207ec9f1d14 1482111949000000 2016-12-19 01:45:50 UTC received: block (546 bytes) received block fd7dc464a207ec9f1d14 CBlock(hash=fd7dc464a207ec9f1d14, ver=1, hashPrevBlock=000000b511c9e3db2702, hashMerkleRoot=a9d7e24a26, nTime=1482111941, nBits=1d1fd5b2, nNonce=0, vtx=2, vchBlockSig=3045022100889a64149ca931780aa5b4615216d5fc538afe65373bc11bd356776eecc4a03602200cbe693e5b00921e4075977f92c141f820d647c0d4a80cf61716b2dc805a653d) CBlock General PoB(nBurnBits=1d0134a9 nEffectiveBurnCoins=786167806765 (formatted 786167.806765)) Coinbase(hash=2937e1dc6f, nTime=1482111941, ver=1, vin.size=1, vout.size=1, nLockTime=0) CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, -1), coinbase 04c53b575802b501062f503253482f) CTxOut(empty) Coinstake(hash=89f2fb73ff, nTime=1482111941, ver=1, vin.size=1, vout.size=3, nLockTime=0) CTxIn(COutPoint(75cd70945ce906aa64cd727225e217a7cbbb24419d698b9b4ea357c2d0a28f0b, 0), scriptSig=30450221008e5c173c860b8b) CTxOut(empty) CTxOut(nValue=8.65, scriptPubKey=03fad597f3ea9b03a43e48b8f804face48ca78f57777fe41b9f35e623dbc521b28 OP_CHECKSIG) CTxOut(nValue=8.656478, scriptPubKey=03fad597f3ea9b03a43e48b8f804face48ca78f57777fe41b9f35e623dbc521b28 OP_CHECKSIG) vMerkleTree: CheckStakeKernelHash() : using modifier 0xac0ba920207e4a67 at height=822727 timestamp=2016-11-26 18:06:23 UTC for block from height=814402 timestamp=2016-11-17 20:57:41 UTC CheckStakeKernelHash() : check protocol=0.3 modifier=0xac0ba920207e4a67 nTimeBlockFrom=1479416261 nTxPrevOffset=170 nTimeTxPrev=1479416261 nPrevout=0 nTimeTx=1482111941 hashProof=00003015f75044971b0b8cc5fa7b98d0c6b49817441a33149d504e2cc7089ed7 ComputeNextStakeModifier: prev modifier=0x0f6ee22f8a913631 time=2016-12-19 00:02:11 UTC epoch=1482105731 SetBestChain: new best=fd7dc464a207ec9f1d14 height=844117 trust=20007633313655 moneysupply=13738011.644397 nEffectiveBurnCoins=786167.806765 ProcessBlock: ACCEPTED 2016-12-19 01:45:52 UTC received: inv (37 bytes) got inventory: block fd7dc464a207ec9f1d14 have 2016-12-19 01:45:53 UTC sending: getblocks (1029 bytes) force request: block fd7dc464a207ec9f1d14 2016-12-19 01:45:54 UTC sending: inv (37 bytes) connection timeout 2016-12-19 01:45:54 UTC Flushing wallet.dat trying connection 186.94.240.221:41682 lastseen=-21187.9hrs Flushed wallet.dat 2515ms connection timeout trying connection 59.188.237.35:41682 lastseen=-22212.0hrs connection timeout trying connection 81.161.243.118:41682 lastseen=-22230.4hrs connection timeout trying connection 206.72.192.204:41682 lastseen=-16272.5hrs connection timeout trying connection 213.111.122.124:41682 lastseen=-22234.3hrs connection timeout trying connection 151.233.224.137:41682 lastseen=-1058.5hrs connection timeout trying connection 177.98.128.221:41682 lastseen=-22313.6hrs connection timeout trying connection 42.112.19.43:41682 lastseen=-21671.6hrs connection timeout trying connection 2.187.77.3:41682 lastseen=-16979.0hrs connection timeout trying connection 95.90.206.237:41682 lastseen=-16532.6hrs connection timeout trying connection 65.75.78.212:41682 lastseen=-22136.8hrs connection timeout trying connection 200.165.20.102:41682 lastseen=-22347.4hrs trying connection 62.152.54.44:41682 lastseen=-383920.0hrs connected 62.152.54.44:41682 2016-12-19 01:47:07 UTC sending: version (223 bytes) socket closed 2016-12-19 01:47:07 UTC disconnecting node 62.152.54.44:41682 trying connection 85.25.214.107:41682 lastseen=-383920.0hrs connection timeout trying connection 121.170.243.22:41682 lastseen=-22478.1hrs connection timeout trying connection 201.109.14.3:41682 lastseen=-383920.0hrs connection timeout trying connection 123.15.42.226:41682 lastseen=-14776.3hrs connection timeout trying connection 104.131.114.226:41682 lastseen=-383920.0hrs connection timeout trying connection 176.41.12.235:41682 lastseen=-19452.9hrs connection timeout trying connection 187.21.162.164:41682 lastseen=-383920.0hrs connection timeout connection timeout trying connection 213.165.83.122:41682 lastseen=-383920.0hrs trying connection 122.166.231.83:41682 lastseen=-21143.0hrs connection timeout trying connection 5.9.38.137:41682 lastseen=-383920.0hrs connection timeout trying connection 186.45.18.41:41682 lastseen=-22125.7hrs connection timeout trying connection 62.117.14.199:41682 lastseen=-383920.0hrs connection timeout trying connection 123.150.234.172:41682 lastseen=-20090.9hrs connection timeout connection timeout trying connection 109.92.240.190:41682 lastseen=-19893.8hrs connection timeout trying connection 213.162.125.106:41682 lastseen=-16765.4hrs connection timeout trying connection 62.30.194.230:41682 lastseen=-16047.4hrs connection timeout trying connection 5.105.5.239:41682 lastseen=-9761.0hrs connection timeout trying connection 109.228.4.72:41682 lastseen=-22216.6hrs connection timeout trying connection 151.233.73.179:41682 lastseen=-7843.3hrs connection timeout trying connection 189.173.33.164:41682 lastseen=-399.7hrs connection timeout trying connection 2.187.80.59:41682 lastseen=-19479.4hrs connection timeout trying connection 2.187.76.31:41682 lastseen=-16605.7hrs
************************ EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE cancel: The attempted operation is not supported for the type of object referenced C:\=Coins\SLIMCoin\slimcoin-qt-2016.exe in ThreadRPCServer()
connection timeout trying connection 188.244.138.15:41682 lastseen=-21174.8hrs connection timeout trying connection 71.53.105.179:41682 lastseen=-22049.6hrs connection timeout trying connection 151.233.225.80:41682 lastseen=-1532.7hrs connection timeout trying connection 115.242.227.38:41682 lastseen=-22303.7hrs connection timeout trying connection 168.187.121.147:41682 lastseen=-22292.2hrs connection timeout trying connection 185.29.165.89:41682 lastseen=-21716.7hrs connection timeout trying connection 151.233.224.52:41682 lastseen=-1224.8hrs connection timeout trying connection 2.187.89.6:41682 lastseen=-21477.1hrs connection timeout trying connection 81.39.58.123:41682 lastseen=-972.6hrs connection timeout ResendWalletTransactions() trying connection 151.232.196.75:41682 lastseen=-12089.0hrs Relaying wtx c70f0f7684 trying connection 62.152.54.44:41682 lastseen=-383920.1hrs connected 62.152.54.44:41682 2016-12-19 01:49:47 UTC sending: version (223 bytes) connection timeout trying connection 85.25.214.107:41682 lastseen=-383920.1hrs trying connection 151.233.74.30:41682 lastseen=-7987.2hrs connection timeout connection timeout trying connection 201.109.14.3:41682 lastseen=-383920.1hrs trying connection 88.184.64.208:41682 lastseen=-22383.8hrs socket closed 2016-12-19 01:49:54 UTC disconnecting node 62.152.54.44:41682 connection timeout trying connection 104.131.114.226:41682 lastseen=-383920.1hrs connection timeout trying connection 2.187.65.183:41682 lastseen=-20202.3hrs connection timeout trying connection 187.21.162.164:41682 lastseen=-383920.1hrs connection timeout trying connection 68.54.118.59:41682 lastseen=-21983.2hrs connection timeout trying connection 213.165.83.122:41682 lastseen=-383920.1hrs connection timeout trying connection 54.209.197.207:41682 lastseen=-22466.3hrs connection timeout trying connection 5.9.38.137:41682 lastseen=-383920.1hrs connection timeout trying connection 58.34.141.177:41682 lastseen=-22489.8hrs connection timeout trying connection 62.117.14.199:41682 lastseen=-383920.1hrs connection timeout trying connection 54.86.193.114:41682 lastseen=-22460.8hrs connection timeout connection timeout trying connection 151.12.206.42:41682 lastseen=-16608.5hrs connection timeout trying connection 212.74.203.100:41682 lastseen=-355.6hrs 2016-12-19 01:50:37 UTC received: getdata (145 bytes) received getdata for: block e1b9e7e8944f5b46b6d6 nHeight: 844108 2016-12-19 01:50:37 UTC sending: block (356 bytes)
received getdata for: block 6be13b769dab6842dead nHeight: 844109 2016-12-19 01:50:37 UTC sending: block (545 bytes)
received getdata for: block c69a5e7cc4600cc4164a nHeight: 844110 2016-12-19 01:50:37 UTC sending: block (543 bytes)
received getdata for: block cdc3c91277c78203dcb6 nHeight: 844112 2016-12-19 01:50:37 UTC sending: block (355 bytes)
connection timeout trying connection 46.51.192.182:41682 lastseen=-22466.8hrs connection timeout trying connection 70.210.132.182:41682 lastseen=-22056.3hrs connection timeout trying connection 125.253.120.105:41682 lastseen=-16205.5hrs connection timeout trying connection 93.137.116.75:41682 lastseen=-22360.3hrs connection timeout trying connection 47.55.177.73:41682 lastseen=-301.3hrs connection timeout trying connection 2.187.95.200:41682 lastseen=-21338.1hrs connection timeout trying connection 190.73.42.102:41682 lastseen=-16865.2hrs connection timeout trying connection 180.190.224.85:41682 lastseen=-18465.5hrs connection timeout trying connection 118.186.196.110:41682 lastseen=-10008.7hrs connection timeout trying connection 2.187.69.243:41682 lastseen=-18017.7hrs connection timeout trying connection 85.25.195.74:41682 lastseen=-16266.5hrs connection timeout trying connection 95.212.133.114:41682 lastseen=-22211.7hrs connection timeout trying connection 188.22.107.213:41682 lastseen=-18790.9hrs connection timeout trying connection 163.239.255.24:41682 lastseen=-22155.5hrs connection timeout trying connection 139.193.64.61:41682 lastseen=-13921.0hrs DBFlush(false) addr.dat refcount=0 ThreadAfterBurner exiting, 0 threads remaining ThreadSocketHandler exiting addr.dat checkpoint addr.dat detach ThreadMessageHandler exiting addr.dat closed blkindex.dat refcount=0 blkindex.dat checkpoint blkindex.dat detach ThreadStakeMinter exiting, 0 threads remaining
|
|
|
|
gjhiggins
Legendary
Offline
Activity: 2254
Merit: 1278
|
|
December 19, 2016, 04:28:09 AM |
|
here is a debug.log around crash
Thank you. I think I may be able to set up a Windows 10 VM which might allow me to reproduce the problem. Cheers Graham
|
|
|
|
ArchitektoR
|
|
December 19, 2016, 09:14:04 AM |
|
Thank you. I think I may be able to set up a Windows 10 VM which might allow me to reproduce the problem.
this is from XP x64 VM. Can test on a 7 x64 VM - but I don't think it matters.
|
|
|
|
gavrilo77
|
|
December 19, 2016, 11:22:11 AM |
|
Windows client g154b52a-alpha works well. It is synced and mining is OK. Blocks are coming. I am using Windows 10 64 bit
|
|
|
|
gavrilo77
|
|
December 19, 2016, 05:38:04 PM Last edit: December 19, 2016, 08:21:36 PM by gavrilo77 |
|
First block from Burnt coins came as well for the new wallet
However, i wrote to BTER about possibility to list SLM again.
|
|
|
|
gavrilo77
|
|
December 19, 2016, 09:24:18 PM |
|
Here is the bootstrap https://mega.nz/#!PotnDaCT!_P5nhOr8SjvCD-2xVajS6zc16d8uVG7Xnz2HI1XfDck Copy to your appdata/roaming/slimcoin folder
|
|
|
|
ptrace
Newbie
Offline
Activity: 34
Merit: 0
|
|
December 19, 2016, 11:02:08 PM |
|
Here is the bootstrap https://mega.nz/#!PotnDaCT!_P5nhOr8SjvCD-2xVajS6zc16d8uVG7Xnz2HI1XfDck Copy to your appdata/roaming/slimcoin folder Thanks for the upload! I downloaded it here previously: https://bchain.info/SLM/bootstrap.dat
|
|
|
|
gjhiggins
Legendary
Offline
Activity: 2254
Merit: 1278
|
|
December 20, 2016, 02:18:36 AM |
|
Thank you. I think I may be able to set up a Windows 10 VM which might allow me to reproduce the problem.
this is from XP x64 VM. Can test on a 7 x64 VM - but I don't think it matters. Ah, okay. Sorry but I can't help with anything other than contemporary OS versions. Cheers Graham
|
|
|
|
Anapple
Newbie
Offline
Activity: 21
Merit: 0
|
|
December 20, 2016, 12:32:06 PM |
|
Are there any other proof-of-burn coins in active development? Slimcoin is the only one that I could find with at least some activity, although very silent with this coin also..
|
|
|
|
Anapple
Newbie
Offline
Activity: 21
Merit: 0
|
|
December 20, 2016, 01:21:51 PM |
|
Is there actually any Proof-of-Stake used currently in Slimcoin? It is mentioned but there is very little information about the PoS side..
|
|
|
|
ArchitektoR
|
|
December 20, 2016, 01:59:13 PM |
|
Is there actually any Proof-of-Stake used currently in Slimcoin? It is mentioned but there is very little information about the PoS side..
yes and it works
|
|
|
|
psycodad
Legendary
Offline
Activity: 1596
Merit: 1540
精神分析的爸
|
|
December 20, 2016, 03:52:42 PM Last edit: December 20, 2016, 09:04:17 PM by psycodad |
|
Came across Slimcoin because Graham mentioned the integrated block explorer in another thread on bct, that made me curious and I decided to give it a try. So far I think Slimcoin is pretty unique and its Proof of Burn very interesting. I am runing the QT wallet from https://github.com/slimcoin-project/Slimcoin on Debian Wheezy (7) 64-bit and I have so far two issues: - Entering "help" in the debug window closes the QT client immediately, without any notice in debug.log - synching is repeatedly stuck after exactly 530 blocks: I deleted everything except wallet.dat and restarted, after a few seconds I am again stuck at exactly block #530. The error is mostly something like ERROR: CheckBlock() : coinbase reward exceeded 153.34 > 50.00These errors repeat since about 30mins and I get no more new blocks on synching even so I have 3-4 connections all the time. Did the same a 3rd time with slimcoind and have the same results, stuck at 530. It seems the coinbase transaction does not match the requirements of the client somehow. I am using the addnodes from OP, and I noticed that Slimcoin does not use a peers.dat for storing peers, how does the Slimecoin client keep peers information between two restarts? Cheers - psycodad
|
|
|
|
gavrilo77
|
|
December 20, 2016, 09:00:55 PM |
|
I am happy to see diff went up. It seems people are more attracted
|
|
|
|
enerbyte
|
|
December 20, 2016, 10:03:09 PM |
|
I am happy to see diff went up. It seems people are more attracted
It's good to see this
|
|
|
|
ArchitektoR
|
|
December 21, 2016, 08:21:48 AM |
|
Came across Slimcoin because Graham mentioned the integrated block explorer in another thread on bct, that made me curious and I decided to give it a try. So far I think Slimcoin is pretty unique and its Proof of Burn very interesting. I am runing the QT wallet from https://github.com/slimcoin-project/Slimcoin on Debian Wheezy (7) 64-bit and I have so far two issues: - Entering "help" in the debug window closes the QT client immediately, without any notice in debug.log - synching is repeatedly stuck after exactly 530 blocks: I deleted everything except wallet.dat and restarted, after a few seconds I am again stuck at exactly block #530. The error is mostly something like ERROR: CheckBlock() : coinbase reward exceeded 153.34 > 50.00These errors repeat since about 30mins and I get no more new blocks on synching even so I have 3-4 connections all the time. Did the same a 3rd time with slimcoind and have the same results, stuck at 530. It seems the coinbase transaction does not match the requirements of the client somehow. I am using the addnodes from OP, and I noticed that Slimcoin does not use a peers.dat for storing peers, how does the Slimecoin client keep peers information between two restarts? Cheers - psycodad yes - console slimcoind stucks on 530 block too... only exporting full blockchain from Windows client worked for me
|
|
|
|
gavrilo77
|
|
December 21, 2016, 08:48:42 AM |
|
Can we do something to have SLM listed on some exchange?
|
|
|
|
|