Bitcoin Forum
May 02, 2024, 04:37:07 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Delete me  (Read 261 times)
SatosheePoW (OP)
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
April 19, 2024, 02:10:15 AM
Last edit: April 28, 2024, 07:19:11 PM by SatosheePoW
 #1

Delete me
The block chain is the main innovation of Bitcoin. It is the first distributed timestamping system.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714624627
Hero Member
*
Offline Offline

Posts: 1714624627

View Profile Personal Message (Offline)

Ignore
1714624627
Reply with quote  #2

1714624627
Report to moderator
CryptoGirl.y
Sr. Member
****
Offline Offline

Activity: 624
Merit: 260



View Profile
April 19, 2024, 07:20:36 AM
 #2

At the moment, the Xeggex exchange has suspended the withdrawal of the BitcoinPow coin; if the withdrawal is not available until April 27th, then I believe that the fork of the coin will need to be postponed, since many people buy BTCW in order to receive BSP after the fork.
CryptoGirl.y
Sr. Member
****
Offline Offline

Activity: 624
Merit: 260



View Profile
April 22, 2024, 02:53:37 PM
 #3

The withdrawal of the BTCW coin was opened on the Xeggex exchange. Those who wanted to purchase this coin before the fork in order to receive the second BSP coin on April 27th, then do it now, because Xeggex has problems with the servers, perhaps they will close the withdrawal of coins again.
sdnz
Newbie
*
Offline Offline

Activity: 50
Merit: 0


View Profile
April 23, 2024, 11:49:17 PM
 #4

Is 256 going to be enough to distribute centralised mining to more miners? Maybe need 1024 (or 4096 or even more)?

Anyway the intention of adding 256 times PoW seems reasonable but it will introduces an undesirable impact on nodes as well (not miners) because when new blocks are synchronised each node also has to run that loop to verify the hash, which will logically slows down blockchain sync with a bit of pain when new node joins.

It may be more efficient if this is improved so only intend to change mining algo.

* It could be possible to put the loop index in the block header, nNonce which is now simply dead part as always set to 0xFEEDBEEF.
* This may be a right time to make this change along with the hard fork at #21111 rather than later time in case needed.
 
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!