|
slimcoin (OP)
|
 |
July 10, 2014, 04:45:09 PM |
|
I pushed a new non-mandatory update that includes the signrawtransaction and sendrawtransaction rpc commands.
|
-Much Donate
BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
TheRealSteve
|
|
July 10, 2014, 05:45:08 PM |
|
Very nice! Glad they got it up and running after the changes  |
|
|
|
BTMan
Full Member
 Offline
Activity: 126
Merit: 100
BTMan
|
|
July 10, 2014, 05:50:11 PM |
|
VERY GOOD FOR UPDATE THE TOPIC.
|
|
|
|
ustcstone
Newbie
Offline
Activity: 49
Merit: 0
|
|
July 10, 2014, 05:56:49 PM |
|
the difficulty has been this high before due to PoS blocks. but the network hash rate of 9mh seems to be a all-time high.
My coins are in my wallet since 1 week and 4 days ago... and still no stake... how to fix this? me too!is this a bug? |
|
|
|
|
|
|
|
slimcoin (OP)
|
|
July 10, 2014, 08:15:58 PM |
|
That block is listed as PoW?
|
-Much Donate
BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
|
|
|
|
TheRealSteve
|
|
July 10, 2014, 08:22:26 PM |
|
appears to be listed as PoB on the main page (the list of blocks) - probably just a glitch ( still needs fixing, of course ) |
|
|
|
|
slimcoin (OP)
|
|
July 10, 2014, 08:35:50 PM |
|
Could I have more feedback regarding having a switch to enable/disable PoS minting on the client. See my long post 1 page back for details.
|
-Much Donate
BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
|
|
|
|
rfcdejong
|
|
July 10, 2014, 08:36:22 PM |
|
There should be at least two people working on a block explorer, the dev and a third party who only accidentally landed here; but the latter reported an issue that needs to be addressed first. In due time I just started a test to see if i will be able to fill a database with block information. That database can be indexed and i will be able to create a simple frontend to start with. I'm not sure if i continue with it, as i do too many things currently. The RPC is really slow, so filling the database takes time.. To quote myself (and leaving that big picture out)... i know why it was slow.. i was having all JSON set to log into the console window, lol  Now it parse ~20 blocks per second into the database, while mining slimcoin... |
|
|
|
|
|
rfcdejong
|
|
July 10, 2014, 08:37:46 PM |
|
Could I have more feedback regarding having a switch to enable/disable PoS minting on the client. See my long post 1 page back for details.
Better would be a button on the client instead of a startup parameter, but i don't have issues with PoS because i burn all.. don't ask me |
|
|
|
|
|
glop
|
|
July 10, 2014, 08:40:40 PM |
|
Could I have more feedback regarding having a switch to enable/disable PoS minting on the client. See my long post 1 page back for details.
Better would be a button on the client instead of a startup parameter, but i don't have issues with PoS because i burn all.. don't ask me Same for me... |
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
July 10, 2014, 08:47:02 PM |
|
Block propagation issue has not been completely fixed. I am running 10 qt clients in total and at least 20 times a day i need to restart one because they stop syncing.
If i leave them long enough (20 min - 1hour) they sync by themselves.
|
|
|
|
|
|
rfcdejong
|
|
July 10, 2014, 09:00:40 PM |
|
i found something strange with old blocks, it's not the explorer, it is the blockchain which has wrong timestamp on block 11807, which is a proof-of-burn block... it's 5 minutes in the past? http://www.blockexperts.com/slm/height/11806 June 11, 2014, 02:04:08 http://www.blockexperts.com/slm/height/11807 June 11, 2014, 01:59:36 http://www.blockexperts.com/slm/height/11808 June 11, 2014, 02:06:03 same with http://www.blockexperts.com/slm/height/13934 June 13, 2014, 08:23:39 http://www.blockexperts.com/slm/height/13935 June 13, 2014, 08:18:58 http://www.blockexperts.com/slm/height/13936 June 13, 2014, 08:24:21 those PoB Blocks are in the past... might be correct, but it looks odd (or might be because the blocks are old) |
|
|
|
|
|
glop
|
|
July 10, 2014, 09:55:12 PM |
|
Could I have more feedback regarding having a switch to enable/disable PoS minting on the client. See my long post 1 page back for details.
Better would be a button on the client instead of a startup parameter, but i don't have issues with PoS because i burn all.. don't ask me Same for me... Should have button in addition, not instead because when you run wallet headless it could be difficult in this case to deactivate POS... |
|
|
|
|
theprofileth
Full Member
Offline
Activity: 239
Merit: 100
Socialist Cryptocurrency Devote
|
|
July 11, 2014, 12:22:17 AM |
|
I think someone needs to get some new windows binaries up given that the stake reward has changed and the PoB targetting has changed so allowing clients that are not up to date just screw people over who dont have the proper tools to compile.
|
|
|
|
|
|
slimcoin (OP)
|
|
July 11, 2014, 03:37:33 AM |
|
They have not changed yet, I still have not pushed the updates.
|
-Much Donate
BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
|
|
|
jadefalke
Legendary
Offline
Activity: 1457
Merit: 1014
|
|
July 11, 2014, 06:14:36 AM |
|
i think a POS on/off would be nice, but would it not be easier to just set the Reserve to 5000 to avoid the Client staking?
If you want to stake you can lower the Reserve manualy.
|
|
|
|
|
|
yang5034
|
|
July 11, 2014, 07:08:01 AM |
|
They have not changed yet, I still have not pushed the updates.
thank you for your hard work. |
|
|
|
|
a123
Member
Offline
Activity: 98
Merit: 10
|
|
July 11, 2014, 08:05:10 AM |
|
Block propagation issue has not been completely fixed. I am running 10 qt clients in total and at least 20 times a day i need to restart one because they stop syncing.
If i leave them long enough (20 min - 1hour) they sync by themselves.
I might be noticing the same issue. I'm running a custom front-end that interfaces 2 daemons on separate machines at highest priority, over 2 different ISPs through 2 different continents (Asia and US, via SOCKS proxy) and feeds the miners the highest block count work, and the front-end regularly reports de-synchronisations (> 1 block difference) that resolves only after many blocks. In spite of this, I still occasionally get consecutive chunks of orphan chains, that seem somewhat dependant on network load (I.e. I don't see any orphans when network hash is ~ 3 mhps, but now I'm seeing like 20% orphan rate, and they come in chunks: i.e. t+0 accepted, t+1306 orphan, t+1418 orphan, t+1530 accepted, where t is about 3 hours before this post) so I assume even these two daemons don't seem to be working well. However, the mining pools don't seem to be orphaning as much, so it might just be an localised latency issue for me, so I'll be grateful for any advice. |
|
|
|
|
|
rfcdejong
|
|
July 11, 2014, 01:29:44 PM |
|
They have not changed yet, I still have not pushed the updates.
Somehow my client isn't finding any PoB anymore past 30 hours, maybe there is something changed? I normally find between 3 and 6 PoB every 24 hours. 2200 SLIM burned.. SetBestChain: new best=00000001540ac72c5c32 height=36278 trust=15616798614 moneysupply=376804.070875 nEffectiveBurnCoins=166191.691281 ProcessBlock: ACCEPTED SlimCoinAfterBurner(): Smallest Hash is 00000017e6fe0000000000000000000000000000000000000000000000000001 by tx 358e280c7076522ee09a2aa26644bccd0e84173460bd80050fd58f5a1bb0ffee with Block height 33666, transaction depth 1, vout depth 0 PoB Tartget is 000000014acb0000000000000000000000000000000000000000000000000000 nBurnBits=1d014acb, nEffectiveBurnCoins=166191691281 (formatted 166191.691281) |
|
|
|
|
|
