Author Topic: 111* days estimated for Difficulty to retarget. Could this kill PTS?  (Read 94743 times)

0 Members and 1 Guest are viewing this topic.

Offline testz

Re: 42 days estimated for Difficulty to retarget. Could this kill PTS?
« Reply #8 on: March 04, 2014, 01:23:33 am »
1-2 block per hour it's not a problem, the main problem which we have it's that not all pools include tx into blocks: https://bitsharestalk.org/index.php?topic=831.msg41839#msg41839

I found one, but as I see we have another one, which I can't find, maybe it's a solo miner.
re: the thread you linked, I'm 99% sure that doesn't apply here (and isn't practice by ypool anymore, anyway)

I'll quote Stan, since his extremely condescending reply on another thread would be appropriate here as well

Knowledge and understanding is the ultimate proof of work.

People are sending transactions with zero fees, there are no longer ~5-10 blocks every hour, now there are 1 or 2.  That means many of these transactions won't get into blocks for quite a long time.

I place it to ypool thread because I think it's connected to jh miner originally developed by ypool owner, anyway, in our case it's doesn't connected to fee, if you look to block explorer http://ptsexplorer.cloudapp.net/chain/BitShares-PTS the blocks with 1 transactions doesn't take transactions with fee as well.
And my investigation shows that most blocks produced with 1 transaction doesn't connected to any known pools.

Knowledge and understanding is the ultimate proof of work.
« Last Edit: March 04, 2014, 01:25:49 am by testz »

Offline zvs

  • Full Member
  • ***
  • Posts: 193
    • View Profile
Re: 42 days estimated for Difficulty to retarget. Could this kill PTS?
« Reply #7 on: March 03, 2014, 04:15:48 pm »
1-2 block per hour it's not a problem, the main problem which we have it's that not all pools include tx into blocks: https://bitsharestalk.org/index.php?topic=831.msg41839#msg41839

I found one, but as I see we have another one, which I can't find, maybe it's a solo miner.
re: the thread you linked, I'm 99% sure that doesn't apply here (and isn't practice by ypool anymore, anyway)

I'll quote Stan, since his extremely condescending reply on another thread would be appropriate here as well

Knowledge and understanding is the ultimate proof of work.

People are sending transactions with zero fees, there are no longer ~5-10 blocks every hour, now there are 1 or 2.  That means many of these transactions won't get into blocks for quite a long time.

Pls to join Primedice 3 and frolic about merrily whilst gambling awe-inspiring quantities of bitcoins. The power of Christ compels you.

I have a dogecoin p2pool at Nogleg.

Offline testz

Re: 42 days estimated for Difficulty to retarget. Could this kill PTS?
« Reply #6 on: March 03, 2014, 03:04:09 pm »
1-2 block per hour it's not a problem, the main problem which we have it's that not all pools include tx into blocks: https://bitsharestalk.org/index.php?topic=831.msg41839#msg41839

I found one, but as I see we have another one, which I can't find, maybe it's a solo miner.

Offline barwizi

  • Hero Member
  • *****
  • Posts: 764
  • Noirbits, NoirShares, NoirEx.....lol, noir anyone?
    • View Profile
    • Noirbitstalk.org
Re: 42 days estimated for Difficulty to retarget. Could this kill PTS?
« Reply #5 on: March 03, 2014, 08:53:33 am »
Maybe it's time to do a proof of burn into a proto-asset that actually trades on the first Bitshares chain.  Seems miners don't understand why they'd want to keep mining now that Bitshares has split off.

I don't think this is a good idea, I think it's good if PTS is kept "pure".

We actually don't care if there are barely any miners, we just care that they dropped so quickly that the difficulty doesn't have time to adjust and so blocks are slowed down

Implementation of the diff algo i use (PPC) for NRS with stronger limits may help. A hard limit on the maximum time that may pass before a block is solved will make retargets adjust to these swings in hash.

also recently there is talk of chain migration to PoS only. Everyone keeps their balance but we maintain high tx speed by way of micro PoS
--Bar--  PiNEJGUv4AZVZkLuF6hV4xwbYTRp5etWWJ

The magical land of crypto, no freebies people.

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
Re: 42 days estimated for Difficulty to retarget. Could this kill PTS?
« Reply #4 on: March 03, 2014, 08:31:56 am »
Maybe it's time to do a proof of burn into a proto-asset that actually trades on the first Bitshares chain.  Seems miners don't understand why they'd want to keep mining now that Bitshares has split off.

I don't think this is a good idea, I think it's good if PTS is kept "pure".

We actually don't care if there are barely any miners, we just care that they dropped so quickly that the difficulty doesn't have time to adjust and so blocks are slowed down
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline 029xue

  • Full Member
  • ***
  • Posts: 142
    • View Profile
Re: 42 days estimated for Difficulty to retarget. Could this kill PTS?
« Reply #3 on: March 03, 2014, 08:20:42 am »
That's a problem now, the transaction is very slow in recent days (avg. 1 confirmation per hr.)

Offline AdamBLevine

  • Sr. Member
  • ****
  • Posts: 492
    • View Profile
    • Let's Talk Bitcoin!
Re: 42 days estimated for Difficulty to retarget. Could this kill PTS?
« Reply #2 on: March 03, 2014, 05:44:36 am »
Maybe it's time to do a proof of burn into a proto-asset that actually trades on the first Bitshares chain.  Seems miners don't understand why they'd want to keep mining now that Bitshares has split off.
Email me at adam@letstalkbitcoin.com

Offline NewMine

  • Hero Member
  • *****
  • Posts: 552
    • View Profile
111* days estimated for Difficulty to retarget. Could this kill PTS?
« Reply #1 on: March 03, 2014, 05:41:40 am »
From: http://mrx.im/pts.php?cpm=4270

*new numbers edit

Blocks to retarget: 3098
Measured: 23.16%
Estimated difficulty: 0.00632337 (15.34%)
Time to retarget: 111d 07:06:46 (2014-08-26 07:34:58 UTC+9)

Network hashing speed:
Last 100 blocks: 3,557,881.87 cpm ETA: 107d 00:58:55
Last  50 blocks: 3,421,845.28 cpm ETA: 111d 07:06:46
Last  15 blocks: 2,604,555.19 cpm ETA: 146d 05:17:17
Last   5 blocks: 4,670,302.72 cpm ETA: 81d 13:04:31



Original post below:

Blocks to retarget: 2500
Measured: 38.00%
Estimated difficulty: 0.02562563 (70.73%)
Time to retarget: 42d 06:22:30 (2014-04-14 20:57:18 UTC+9)

Network hashing speed:
Last 100 blocks: 8,467,957.85 cpm ETA: 31d 21:37:55
Last  50 blocks: 6,391,461.77 cpm ETA: 42d 06:22:30
Last  15 blocks: 7,458,464.16 cpm ETA: 36d 05:15:33
Last   5 blocks: 12,018,548.16 cpm ETA: 22d 11:26:40


Am I reading his right?
« Last Edit: May 06, 2014, 03:32:05 pm by newmine »