Bitcoin Forum
July 05, 2022, 12:20:21 AM *
News: Latest Bitcoin Core release: 23.0 [Torrent]
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 »
1  Alternate cryptocurrencies / Altcoin Discussion / Prevent PoS users from staking into the past and future? on: October 27, 2021, 07:59:25 AM
I'm interested to know different solutions to prevent people "cheating" on block time in PoS.

PoS generates a hash using various things including time, it is time that limits the hash power of PoS as if you stake too far into the future or past you generate a block that is rejected by the network.  For example the following shows a simplified version of how Peercoin generates a hash to check against the target difficulty. blockFrom.GetBlockTime() is the block time.

CDataStream ss;
ss << nStakeModifier << blockFrom.GetBlockTime() << nTxPrevOffset << txPrev->nTime << prevout.n << nTimeTx;
uint256 hashProofOfStake = Hash(ss.begin(), ss.end());

When mining you create a block with the current time and see if using it you generate a valid hash. To increase your chances of finding a valid hash you would also try generating blocks up to the past and future block time limits. This poses an advantage over those who do not if this behaviour is not built into the coin itself.

The result of baking this into your code to level the playing field is that the block time will start jumping around and after generating a block you'll likely see several more blocks at once, a new block will change the stake modifier giving all stakers full range of time to stake in again. After the flood of blocks there will be a period to wait while no one was able to generate a block in the next time window and has to wait a second a time on the future time limit. That flood of blocks is normally empty as only the first block was the one that took time to stake.

Networks appear to behave more sanely when "super staking" is not built into the code but this gives an advantage to those who know how to exploit it.

Solutions to this seem to be limiting the future and past time windows.

Does anyone know of any other savvy solutions to this?

This is not a new problem and I'm sure that there must have been attempts to solve this over time.
2  Bitcoin / Development & Technical Discussion / Re: Why not use fixed time instead of median for time in the past for new blocks? on: October 18, 2021, 09:39:34 AM
Thanks, that makes sense, otherwise a block on the edge could start being rejected during propagation.
3  Bitcoin / Development & Technical Discussion / Why not use fixed time instead of median for time in the past for new blocks? on: October 18, 2021, 07:06:40 AM
New blocks that are more than 2 hours ahead of the local time are rejected. For backwards time blocks cannot be less than than the median time of the last eleven blocks. Why not use a fixed time going backwards like the forwards time? The longer we go without a block the larger the backwards time range becomes, a fixed time provides a fixed range from past to future blocks.
4  Alternate cryptocurrencies / Altcoin Discussion / Re: (HELP) creating ALT-COIN on: February 21, 2021, 08:48:16 AM
You are missing an include, fix is in Bitcoin.
5  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Feathercoin [FTC] on: August 15, 2020, 07:36:24 PM

I would like to report the following. At the moment, everyone who holds the coin is being scammed by the team behind feathercoin and the exchanges where the coin is sold. To explain the above approach: I own feathercoin that I keep on I cannot access my funds while it is my property. I have indicated to litebit that I want to transfer the coin to my wallet, but I get the following feedback. Litebit indicates that the coin's creator Peter Bushnell has sent requests to all exchanges where feathercoin is traded, such as, to block people's funds from withdrawing. This is so strange to me, while I have given my money and the currency is my possession, the exchanges can decide, together with the maker of the currency, to refuse withdrawal. If this is true, my question is, why did Peter Bushnell send such an absurd request to the exchanges to block people's funds from withdrawing. There is some weird behind this and all I think is the cash out scam acts. Litebit and the other exchanges are going to sell the funds of people holding it on the exchange when people are blocked from withdrawing their own assets. a big spike will surely come and they will take action. Or the spike to 20 satoshis is now being laundered through people's funds.

Peter Bushnell here. All exchanges have been asked to restore deposits again. I asked exchanges to disable deposits while they upgrade all upgrade their wallets to the latest version and we upgrade the 51% attack protection to a new version. There was a period where the protection was disabled and we did not want exchanges to be attacked during that period.

Apologies for the inconvenience.
6  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [MOON] Mooncoin 🌙 built in 2013 with future in mind on: March 04, 2020, 05:38:51 AM
I think these question was about the .18 build to the people that built and maintain the .18 version nothing to do with .17 or .13. The people that built the .17 and .13 versions can answer questions about those versions.

why was this consensus value changed to 3 months from a default of 24 hours and was not dependant on the "fork" block height?
(validation.h: static const int64_t DEFAULT_MAX_TIP_AGE = 90 * 24 * 60 * 60;)

why was this consensus value changed to 20 blocks from a default of 3 blocks and was not dependant on the "fork" block height?
(net_processing.cpp: return g_last_tip_update < GetTime() - consensusParams.nPowTargetSpacing * 20 && mapBlocksInFlight.empty() )

Thought my work was complete on Moon but I keep being pulled back in!

int64_t DEFAULT_MAX_TIP_AGE = 90 * 24 * 60 * 60;

This was set in the 0.13 client, seemed very old to me but I set it verbatim as I did not consider it my place to judge at that point. Should have revisited this after discovering that 0.13 also hacked out large portions of block validation. This plays a part in IsInitialBlockDownload, once block sync is 90 days old from the current time it will no longer be considered the "initial block download". This can be changed to 24 hours or whatever people consider suitable for Moon.

(net_processing.cpp: return g_last_tip_update < GetTime() - consensusParams.nPowTargetSpacing * 20 && mapBlocksInFlight.empty() )

If this was left at 3 then 0.18 would have considered nodes as stale after 4.5 minutes. Bitcoin's setting of 3 is 3 * 10 minutes, so it takes 30 minutes of no blocks being sent for a node to be considered "stale". 20 is then the same for Moon, 20 * 1.5 = 30, so tips are considered "stale" after 30 minutes same as Bitcoin.
7  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [MOON] Mooncoin 🌙 built in 2013 with future in mind on: February 21, 2020, 01:02:56 PM
I think that there's been a lot of misunderstanding all around.

If 0.13 follows the 0.18 chain after the validation restoration then I've offered to issue a patch for 0.17 to get it on the same chain as 0.13 and 0.18. Then everyone can be on the same chain again. What is not wanted to a split in the network and the community, it will only ultimately be damaging for all involved.
8  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [MOON] Mooncoin 🌙 built in 2013 with future in mind on: February 21, 2020, 09:58:59 AM
Hi everybody,

I'm the developer who was commissioned to create the 0.18 client by Chekaz.

I've put my suggestions on the Telegram channel. We want a single chain after all the dust has settled, 0.17 has already broken consensus with 0.13, which is why you do not restore consensus breaking validation without doing so at a set height so everyone can upgrade in good time.

My suggestion is to update 0.17 to follow the 0.13 chain and release it after the validation restoration height in 0.18, then 0.17 and 0.18 will exist on the same chain and as long as the majority of miners are on 0.17 and 0.18 then 0.13 will follow it. The only concern is if someone tries to spend the 62B stolen coins, moving these funds on 0.18 is now blocked on a consensus level, 0.13 only protected the mempool which is why they moved and 0.17 has no protection against this at all. A new 0.17 version should also block spending of those stolen funds on a consensus level, I can send create the pull request on their 0.17 repo to add this feature.

I've also recommended to to Chekaz that historical validation be restored in the 0.18 release once validation has been restored, then 0.18 will be a fully validating release as it should be, this could not be done from the outset or consensus would break at some point as demonstrated by 0.17.

Side note, all this talk of a 51% attack is incorrect and there's a lot of other misinformation going round. This sort of thing is counterproductive, this is a purely technical issue that can be resolved by dialog.

9  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Feathercoin [FTC] on: January 21, 2020, 07:12:30 AM
All my wallets stopped syncing and are showing
2020-01-20T19:00:34Z ERROR: AcceptBlock: rejected by synchronized checkpoint
2020-01-20T19:00:34Z ERROR: ProcessNewBlock: AcceptBlock FAILED ( (code 0))

Please update your client to 0.18.2 or pull the latest source from GitHub and compile. Some clients got stuck yesterday and an updated client has now been released and source updated to resolve the problem.
10  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ►►►[XBC] BitcoinPlus Bitcoin Plus 2.7.0 RC1 released►Official Thread◄官方公告◄◄◄ on: July 21, 2019, 10:31:28 AM
BitcoinPlus is not a fork of Bitcoin like the ones outlined below, they are hard forks or airdrops on the Bitcoin blockchain. BitcoinPlus are an entirely separate chain with our own genesis block and do not include any subset of the Bitcoin UTXO set.
11  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ►►►[XBC] BitcoinPlus Bitcoin Plus 2.7.0 RC1 released►Official Thread◄官方公告◄◄◄ on: February 08, 2019, 08:31:35 AM
What happened here, does not anyone talk anymore?
 Thevalue of XBC will be based on our efforts.
 We try to make some small donations, being listed on more exchanges is our advantage.
Bushstar is waiting for our small donations.

I paid for the FatBTC and Graviex listing, not keen to do the same for Crex24 so will turn down their offer. There's some news that Cryptopia will return to trading during this month so the requirement for some more backup exchanges may well be moot.

Cryptopia might reopen in February NZ police says
12  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ►►►[XBC] BitcoinPlus Bitcoin Plus 2.7.0 RC1 released►Official Thread◄官方公告◄◄◄ on: February 03, 2019, 11:37:14 AM
Crex24 have replied with the following.

Our current standard listing fee is 0.5 BTC. Integration + BTC market.
Each additional market + 0.1 BTC fee.
Available markets: BTC/ETH/FIAT markets (USD,EUR,RUB,CNY,JPY)

I'm going through the listing process of setting up an account and topping up the balance to 0.5 BTC, also considering a USD listing. If anyone is interested in contributing please PM me.
13  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ►►►[XBC] BitcoinPlus Bitcoin Plus 2.7.0 RC1 released►Official Thread◄官方公告◄◄◄ on: January 31, 2019, 02:10:38 PM
Mercatox are asking for 3.4 Bitcoin which is too much. I've made another application to Crex24 offering 0.4 Bitcoin this time.
14  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ►►►[XBC] BitcoinPlus Bitcoin Plus 2.7.0 RC1 released►Official Thread◄官方公告◄◄◄ on: January 26, 2019, 05:01:27 PM
BitcoinPlus is now listed at Graviex.
15  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ►►►[XBC] BitcoinPlus Bitcoin Plus 2.7.0 RC1 released►Official Thread◄官方公告◄◄◄ on: January 26, 2019, 08:35:32 AM
but will I ever recover them?

I've replied to your PM with instructions on how to restore your balance with the zapwallettxes option.

It would be awesome if we get listed on graviex and crex24. I can surely help you out with crex24. Once it's done, we can find few more people to contribute for the listing on Mercatox (1.4 btc) or Stex (1.1 btc).

Graviex has been paid for, currently waiting to hear back from Crex24. Emailed Mercatox and will find out how much they want.
16  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ►►►[XBC] BitcoinPlus Bitcoin Plus 2.7.0 RC1 released►Official Thread◄官方公告◄◄◄ on: January 25, 2019, 02:20:58 PM
I tried barterdex but couldn't understand how to use it, nor I saw any sign of XBC there. I am ready to pay 50% of the listing fees for crex24. I've tried this exchange personally and its good. Don't look at the volume because they're atleast not faking their volume similar to fatbtc. THe total listing fees is 0.25 btc. I can handle upto 0.12 btc. Let me know if anyone is ready to pay the other half to get xbc listed on crex24.

I'll take you up on that offer and will pursue Crex24 to get a quote, in this depressed market you can often strike a better deal. I've spoken to Graviex and am getting us listed there, we could do with some back up exchanges after our run of bad luck.

We've finished the BTCPay integration but have had to leave it disabled due to Cryptopia going down, a fair amount of time has been lost, I'm hoping they will come back up but after reading the external analysis from Elementus it seems unlikely.
17  Alternate cryptocurrencies / Speculation (Altcoins) / Re: When is the best time to buy Altcoin? on: January 05, 2019, 08:37:51 AM
Jeez, the responses on the first page of this thread are mostly "buy when ICO" with the same level of bad grammar. There's analysis to show that the ICO boom took billions of dollars straight out of crypto into fiat, the whole ICO rush undermined the wider crypto market.

Let's leave ICOs in 2018.

As to when is the right time to buy no one can say with total confidence, so only get into a coin if you can stand to lose what you invested.
18  Alternate cryptocurrencies / Announcements (Altcoins) / BitcoinPlus Soft Forks - Decentralised Exchange on: November 03, 2018, 04:43:25 PM
There's several soft forks happening on BitcoinPlus, the first one will allow atomic swaps and participation on Decentralised Exchanges. Once the feature is active and locked in then BitcoinPlus will join a DEX (Decentralised Exchange).

Upgrade to 2.7, available from the link below, to start staking and help BIP65 activate.

Soft fork tracker

You can follow the soft fork status on the web page below, the new feature becomes active when 75% of the network has upgraded, the feature locked in completely once 95% of the network has upgraded.
19  Alternate cryptocurrencies / Announcements (Altcoins) / Re: CannabisCoin [CANN][X11][Official] Developments & Discussions on: July 18, 2018, 10:19:50 AM
Here's the coinbase transaction created in the hard fork on block 3,030,000 which has two additional outputs to create an additional 631,842 CANN. The inflation model has been changed to not go over the total coins to be mined of 420 million.

451,896 CANN minted to reimburse Bittrex for the coins lost in a 51% attack. Automatic Checkpointing has been enabled on the network to prevent future 51% attacks. Once Bittrex has been reimbursed the CANN/BTC pair will be re-opened.

179,946 CANN minted to pay for two bits of work, the first to create this hard fork for the Core/Android wallet and fix the sync issues on Android at the same time and the second part to update CANN to the 0.13 codebase and implement all the latest Bitcoin soft forks currently missing from CANN which are BIP66, CLTV, CSV and SegWit.

CANN is currently on the 0.8 codebase which is very slow to sync and hard to work with in general compared to newer Bitcoin codebases. For example it can take weeks to sync where it should only take a few hours.
20  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Feathercoin [FTC] on: February 19, 2018, 12:02:03 PM
Feathercoin has been released. It is a mandatory update for anyone on a version prior to as on block 2,120,000 it will start minting Version Bit blocks which will be rejected by old version of Feathercoin. Please make sure you have updated to 0.13 before block 2,120,000 which will be minted roughly in 17 days on the 8th March.

Download the Feathercoin 0.13 from the first page of this thread, the homepage of the official website or from the GitHub release page.



Major changes in 0.13.

- BIP9 Version Bits which starts on block 2120000
- Segregated Witness BIP9 Soft Fork
  - Elimination of unwanted transaction malleability
  - Capacity increase
  - Weighting data based on how it affects node performance
  - Signature covers value
  - Linear scaling of sighash operations
  - Increased security for multisig
  - More efficient almost-full-node security
  - Script versioning
- Faster synchronization
- Compact Block support
- Hierarchical Deterministic Key Generation
- Dynamic transaction fee
- RPC Access Control Changes
  - `-rpcallowip=192.168.1.*` becomes `-rpcallowip=`
  - `-rpcallowip=*` becomes `-rpcallowip=::/0`
- REST interface with `-rest` flag
- Watch-only wallet support
- Block file pruning
- Memory usage optimization
- Reduce upload traffic
- Direct headers announcement
- Notifications through ZMQ
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!