Topic: BitShares PTS (formerly ProtoShares) Mandatory Upgrade & Snapshot Announcement - page 59. (Read 218419 times)
November 06, 2013, 08:58:28 AM
any blockchain explorer?
November 06, 2013, 08:53:24 AM
Mined 2 blocks, and the price is around 0.01 BTC/ PTC - which means I have a BTC!! woot 
Firstly try to sell them
.Everybody wants to sell PTS, but nobody wants to buy. It seems that price 0.01 BTC per PTS is overvalued.
Indeed, where did you pluck this price from?
You are right. I saw in one thread that some trades went at that price so I got excited.
Maybe the price will pick up after the difficulty adjust, or people will just dump and collapse the price.
November 06, 2013, 08:38:09 AM
I would have the same question aswell, would be nice if one of the devs could fill us in on there itentions/reasons for that
It was my mistake that it was set to 2 weeks rather than 1 week. The 1 week difficultly was a parameter chosen by ByteMaster and he might be able fill in some more details about this choice later - I suspect he's asleep at the moment.
I think there will be fewer miners when the difficulty adjusts, but I doubt we'll fall off a cliff. There's probably 2x as much hash power than is reflected in the block chain already, because of the stale and orphan blocks.
November 06, 2013, 08:31:15 AM
Is there a chance that difficulty goes to oblivion or beyond on the next retarget and we get stuck there for some time ?
What is the point of having 2 coin weeks retarget ( or one week as originally intended) instead of a much lower retarget time ?
Just asking, not arguing.
What is the point of having 2 coin weeks retarget ( or one week as originally intended) instead of a much lower retarget time ?
Just asking, not arguing.
I would have the same question aswell, would be nice if one of the devs could fill us in on there itentions/reasons for that
November 06, 2013, 07:39:50 AM
Is there a chance that difficulty goes to oblivion or beyond on the next retarget and we get stuck there for some time ?
What is the point of having 2 coin weeks retarget ( or one week as originally intended) instead of a much lower retarget time ?
Just asking, not arguing.
What is the point of having 2 coin weeks retarget ( or one week as originally intended) instead of a much lower retarget time ?
Just asking, not arguing.
November 06, 2013, 07:21:26 AM
The price maybe dates back to before the feeding frenzy of the usual pump and dump folks got underway with all the rented by the hour servers and such, likely most miners over the next 20 hours or whatever will be the usual folk who are only here for a quick dump...
-MarkM-
-MarkM-
November 06, 2013, 07:16:34 AM
Mined 2 blocks, and the price is around 0.01 BTC/ PTC - which means I have a BTC!! woot
Firstly try to sell them
.Everybody wants to sell PTS, but nobody wants to buy. It seems that price 0.01 BTC per PTS is overvalued.
Indeed, where did you pluck this price from?
November 06, 2013, 07:15:31 AM
I ran the client like 15 minutes ago, and it still can't connect to the network.
I'm working on Windows 7, enabled all the firewall exceptions it asked me to, and have never had similar problems with bitcoin-qt / litecoin-qt etc.
I'm just seeing zero peers.
I'm working on Windows 7, enabled all the firewall exceptions it asked me to, and have never had similar problems with bitcoin-qt / litecoin-qt etc.
I'm just seeing zero peers.
November 06, 2013, 07:11:05 AM
Definitely needs some sort of pool now that team digitalOcean has joined hard.
otherwise this could effect dispersion, and thus in a slight way the principals of the new algorithm.
definitely not a game changer , but a pool wouldn't hurt at this stage.
otherwise this could effect dispersion, and thus in a slight way the principals of the new algorithm.
definitely not a game changer , but a pool wouldn't hurt at this stage.
November 06, 2013, 06:21:40 AM
I'm done after half a dozen or so stales and 2 orphans
good luck =p
good luck =p
November 06, 2013, 06:18:15 AM
Mined 2 blocks, and the price is around 0.01 BTC/ PTC - which means I have a BTC!! woot
Firstly try to sell them
.Everybody wants to sell PTS, but nobody wants to buy. It seems that price 0.01 BTC per PTS is overvalued.
November 06, 2013, 06:12:09 AM
You may have noticed the block difficulty hasn't adjusted as expected at block 2016. I made a mistake with the parameters, and the block difficultly adjustment is set to 2 weeks rather than 1. I've had a quick discussion with ByteMaster, and we've decided the course of action is to leave difficultly adjustment at 2 weeks for now, and consider releasing a patch later to bring the difficulty adjustment back down to 1 week.
What this means is a further 24 hours or so of low-difficulty mining before the difficultly adjusts at block 4032.
What this means is a further 24 hours or so of low-difficulty mining before the difficultly adjusts at block 4032.
I really don't see an issue , Re adjustment. It's untested , so it won't be exposed to anything like possible swings that an sCrypt or SHA256 would.
There is really no problem.
November 06, 2013, 05:58:43 AM
Mined 2 blocks, and the price is around 0.01 BTC/ PTC - which means I have a BTC!! woot
November 06, 2013, 05:30:37 AM
Can anyone that tested the AWS cluster instance with 32 cores and 60G RAM care to share the results ?
I tested them and got some bad results. With 32 threads memory load is around 24G , but it seems the memory is slow as hell. I couldn't get any instance to hash.
I tested them and got some bad results. With 32 threads memory load is around 24G , but it seems the memory is slow as hell. I couldn't get any instance to hash.
November 06, 2013, 05:22:35 AM
... but then wouldn't that be a new hash?
I think this is probably what happened ->
2013-11-06 08:37:30 (Approximate start time of hash)
2013-11-06 08:37:32 received block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a
2013-11-06 08:37:37 CreateNewBlock(): total size 1225 (probably from a different thread)
2013-11-06 08:37:37 Found Hash 000f8536079f4f9368e295a1a4552fb27687ddd872444b07467dc86ca724d9b2
November 06, 2013, 05:19:08 AM
... but then wouldn't that be a new hash?
I think this is probably what happened ->
2013-11-06 08:37:30 (Approximate start time of hash)
2013-11-06 08:37:32 received block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a
2013-11-06 08:37:37 CreateNewBlock(): total size 1225 (probably from a different thread)
2013-11-06 08:37:37 Found Hash 000f8536079f4f9368e295a1a4552fb27687ddd872444b07467dc86ca724d9b2
November 06, 2013, 05:09:50 AM
They aren't even orphans though, they're coming up stale. I'm receiving the blocks, but it's working on the block prior
The latest one happened with 3 cores being used out of 8 on a xeon 1270v3
The latest one happened with 3 cores being used out of 8 on a xeon 1270v3
It's a similar issue - the code only checks for new transactions at the start of the hash, and doesn't interrupt ongoing hashes when new blocks come in. The code is not optimized and not designed to gracefully deal with these conditions.
Code:
2013-11-06 08:37:32 received block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a
2013-11-06 08:37:32 Committing 2 changed transactions to coin database...
2013-11-06 08:37:32 SetBestChain: new best=0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a height=2368 log2_work=23.210415 tx=2670 date=2013-11-06 08:37:06 progress=0.000053
2013-11-06 08:37:32 ProcessBlock: ACCEPTED
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:32 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:33 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:33 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:33 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:33 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:33 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:33 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:33 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:33 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:34 received getdata for: block 0008685bf909d5316ac79e1b2f0f40f09af0c45219cd2f1776979acf8af8d30a limit 500
2013-11-06 08:37:37 testHash 80a9a8e430a940eab285ee66cf7e358cb39bf822ae03ab316cb2bb743f7dc411
2013-11-06 08:37:37 Hash Target 000fff0000000000000000000000000000000000000000000000000000000000
2013-11-06 08:37:37 CreateNewBlock(): total size 1225
2013-11-06 08:37:37 Running ProtoSharesMiner with 2 transactions in block (421 bytes)
2013-11-06 08:37:37 testHash 000f8536079f4f9368e295a1a4552fb27687ddd872444b07467dc86ca724d9b2
2013-11-06 08:37:37 Hash Target 000fff0000000000000000000000000000000000000000000000000000000000
2013-11-06 08:37:37 Found Hash 000f8536079f4f9368e295a1a4552fb27687ddd872444b07467dc86ca724d9b2
2013-11-06 08:37:37 hash 000f8536079f4f9368e295a1a4552fb27687ddd872444b07467dc86ca724d9b2
2013-11-06 08:37:37 hash2 000f8536079f4f9368e295a1a4552fb27687ddd872444b07467dc86ca724d9b2
2013-11-06 08:37:37 ProtoSharesMiner:
2013-11-06 08:37:37 proof-of-work found
2013-11-06 08:37:37 CBlock(hash=000f8536079f4f9368e295a1a4552fb27687ddd872444b07467dc86ca724d9b2, ver=2, hashPrevBlock=000a1f6692b2a78e89ab3e82bd04fead89e240774ef9203e9c293825133f485f, hashMerkleRoot=fc1c23eed0a5f6c77b1a2d34247c6dc0f34de96c4ae416f8227d1e33e93440b5, nTime=1383727041, nBits=20000fff, nNonce=2, vtx=1, birthdayA=55398462, birthdayB=64046174)
2013-11-06 08:37:37 CTransaction(hash=fc1c23eed0a5f6c77b1a2d34247c6dc0f34de96c4ae416f8227d1e33e93440b5, ver=1, vin.size=1, vout.size=1, nLockTime=0)
2013-11-06 08:37:37 generated 47.50
2013-11-06 08:37:37 ERROR: ProtoSharesMiner : generated block is stale
... but then wouldn't that be a new hash?
ed: Oh, I see. There's one going for each thread. I guess that means it's probably better to disable hyperthreading
November 06, 2013, 05:03:51 AM
They aren't even orphans though, they're coming up stale. I'm receiving the blocks, but it's working on the block prior
The latest one happened with 3 cores being used out of 8 on a xeon 1270v3
The latest one happened with 3 cores being used out of 8 on a xeon 1270v3
It's a similar issue - the code only checks for new transactions at the start of the hash, and doesn't interrupt ongoing hashes when new blocks come in. The code is not optimized and not designed to gracefully deal with these conditions.
November 06, 2013, 04:55:46 AM
There's a lot of orphans right now because the difficultly is still low and we're getting new blocks every 30 seconds. This was unexpected and should be considered atypical conditions. This will become much less of an issue after difficulty adjustment at block 4032.
They aren't even orphans though, they're coming up stale. I'm receiving the blocks, but it's working on the block prior
The latest one happened with 3 cores being used out of 8 on a xeon 1270v3
November 06, 2013, 04:49:57 AM
There's a lot of orphans right now because the difficultly is still low and we're getting new blocks every 30 seconds. This was unexpected and should be considered atypical conditions. This will become much less of an issue after difficulty adjustment at block 4032.
Jump to: