Bitcoin Wallet Out Of Sync - Neue Aktienstrategien Erfahrungen
Bitcoin Wallet Out Of Sync - Neue Aktienstrategien Erfahrungen
How To Fix Bitcoin Wallet Not Synchronizing With Network ...
Wallet won't sync - Beginners Guide to Bitcoin, Blockchain ...
Bitcoin Full Validation Sync Performance - Casa Blog
Why is my Bitcoin wallet always out of sync?
Day 1180 - Barter is still useless
What is a "good offer" on the market?
It's cheaper than fair price
Why would anyone make a good offer on the market?
To sell fast and free up slots to sell other stuff
What happens when you make a cheap barter offer?
Nobody notices so it doesn't sell fast
Therefore, there's no reason to make a cheap barter offer
Actually, there's no reason to put a barter at all. You gain nothing from doing it as a barter when you can simply buy it from the flea market after selling yours in rubles. You can only buy barter offers with FiR items, and the items you get is the same as when selling as rubles. Even if the "asking value" displayed for barter is properly synced with the market, it won't matter because it will always be noticed slower by players and you gain nothing as a seller, and buyers usually gain nothing as a buyer.
As a result, only bad(expensive) offers are made.
Nikita himself knows barter is usually a scam & nobody uses it, so he actually made "remove barter offers" filter as a default option.
We need to incentivize players to use the barter function, otherwise it'll just be another feature that 99.9% of players don't use. Don't worry - even with incentives, your normal ruble based market won't see any visible impact. Don't worry - RMT issues aren't related to barter. RMT sellers buy the expensive ruble based offers/drop bitcoins in raid/do a labs raid together while using cheats/give gearsets inraid. Barter trades don't have any possibilities of being used nefariously, ESPECIALLY since item being sold as barter and item being asked in exchange BOTH have to be FIR.
Remove/drastically lower fees for barter trades - barter is already painful for sellers and buyers. Fee removal will lead to potentially cheaper barter offers, which makes the market experience more dynamic.
Make barter offers take up a separate sales slot - barter will always take longer to sell due to less visibility, less convenience for buyers, and not many will have the exact items you require ready to pay as FiR. So, having a barter offer take up a different slot so that you can still sell other items for rubles would be a nice QoL change.
Make the estimated total value of the asking item shown for barters accurate to the current flea average prices, to make actual cheaper offers obvious.
Fix the regression bug that removed item name previews on the flea list. Since couple months ago, we can no longer see what items are required for the barter unless we mouse over the "?" icon. We used to see the item names without having to mouseover it.
I feel that barter is much more "personal" and interactive than a plain ruble based transaction 24/7. I'd like to see it get expanded more as a game feature rather than some annoyance that we have to block out using "remove barter offers" from the filter every time.
https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/126.96.36.199 Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that. Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap. We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout. Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.
Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now. Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date. The transition height is also when the team requirement will be relaxed for the network.
Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.
The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use. There are so many goodies here it is hard to summarize them all. I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures. The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!
Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.
Network magnitude unit pinned to a static value of 0.25
Max research reward allowed per block raised to 16384 GRC (from 12750 GRC)
New CPIDs begin accruing research rewards from the first superblock that contains the CPID instead of from the time of the beacon advertisement
500 GRC research reward limit for a CPID's first stake
6-month expiration for unclaimed rewards
10-block spacing requirement between research reward claims
Rolling 5-day payment-per-day limit
Legacy tolerances for floating-point error and time drift
The need to include a valid copy of a CPID's magnitude in a claim
10-block emission adjustment interval for the magnitude unit
One-time beacon activation requires that participants temporarily change their usernames to a verification code at one whitelisted BOINC project
Verification codes of pending beacons expire after 3 days
Self-service beacon removal
Burn fee for beacon advertisement increased from 0.00001 GRC to 0.5 GRC
Rain addresses derived from beacon keys instead of a default wallet address
Beacon expiration determined as of the current block instead of the previous block
The ability for developers to remove beacons
The ability to sign research reward claims with non-current but unexpired beacons
As a reminder:
Beacons expire after 6 months pass (180 days)
Beacons can be renewed after 5 months pass (150 days)
Renewed beacons must be signed with the same key as the original beacon
Magnitudes less than 1 include two fractional places
Magnitudes greater than or equal to 1 but less than 10 include one fractional place
A valid superblock must match a scraper convergence
Superblock popularity election mechanics
Yes/no/abstain and single-choice response types (no user-facing support yet)
To create a poll, a maximum of 250 UTXOs for a single address must add up to 100000 GRC. These are selected from the largest downwards.
Burn fee for creating polls scaled by the number of UTXOs claimed
50 GRC for a poll contract
0.001 GRC per claimed UTXO
Burn fee for casting votes scaled by the number of UTXOs claimed
0.01 GRC for a vote contract
0.01 GRC to claim magnitude
0.01 GRC per claimed address
0.001 GRC per claimed UTXO
Maximum length of a poll title: 80 characters
Maximum length of a poll question: 100 characters
Maximum length of a poll discussion website URL: 100 characters
Maximum number of poll choices: 20
Maximum length of a poll choice label: 100 characters
Magnitude, CPID count, and participant count poll weight types
The ability for developers to remove polls and votes
[188.8.131.52] 2020-09-03, mandatory, "Fern"
Backport newer uint256 types from Bitcoin #1570 (@cyrossignol)
Implement project level rain for rainbymagnitude #1580 (@jamescowens)
Upgrade utilities (Update checker and snapshot downloadeapplication) #1576 (@iFoggz)
Provide fees collected in the block by the miner #1601 (@iFoggz)
Add support for generating legacy superblocks from scraper stats #1603 (@cyrossignol)
Port of the Bitcoin Logger to Gridcoin #1600 (@jamescowens)
Implement zapwallettxes #1605 (@jamescowens)
Implements a global event filter to suppress help question mark #1609 (@jamescowens)
Add next target difficulty to RPC output #1615 (@cyrossignol)
Add caching for block hashes to CBlock #1624 (@cyrossignol)
Make toolbars and tray icon red for testnet #1637 (@jamescowens)
Add an rpc call convergencereport #1643 (@jamescowens)
Implement newline filter on config file read in #1645 (@jamescowens)
Implement beacon status icon/button #1646 (@jamescowens)
Add gridcointestnet.png #1649 (@caraka)
Add precision to support magnitudes less than 1 #1651 (@cyrossignol)
Replace research accrual calculations with superblock snapshots #1657 (@cyrossignol)
Publish example gridcoinresearch.conf as a md document to the doc directory #1662 (@jamescowens)
Add options checkbox to disable transaction notifications #1666 (@jamescowens)
Add support for self-service beacon deletion #1695 (@cyrossignol)
Add support for type-specific contract fee amounts #1698 (@cyrossignol)
Add verifiedbeaconreport and pendingbeaconreport #1696 (@jamescowens)
Add preliminary testing option for block v11 height on testnet #1706 (@cyrossignol)
Add verified beacons manifest part to superblock validator #1711 (@cyrossignol)
Implement beacon, vote, and superblock display categories/icons in UI transaction model #1717 (@jamescowens)
Disclaimer: This is sort of my own arbitrary editing, so there could be some misunderstandings. I root for the spread of good spirits and transparency of IF. 📷 Hans Moog [IF]어제 오후 2:45 So why don't we just copy Avalanche? Well that's pretty simple ... 📷 Hans Moog [IF]어제 오후 2:47 1. It doesn't scale very well with the amount of nodes in the network that have no say in the consensus process but are merely consensus consuming nodes(i.e. sensors, edge devices and so on). If you assume that the network will never have more than a few thousand nodes then thats fine butif you want to build a DLT that can cope with millions of devices then it wont work because of the message complexity. 2. If somebody starts spamming conflicts, then the whole network will stop to confirm any transactions and will grind to a halt until the conflict spamming stops.Avalanche thinks that this is not a huge problem because an attacker would have to spend fees for spamming conflicts which means that he couldn't do this forever and would at some point run out of funds. IOTA tries to build a feeless protocol and a consensus that stops to function if somebody spams conflicts is really not an option for us. 3. If a medium sized validator goes offline due to whatever reason, then the whole network will again stop to confirm any transactionsbecause whenever a query for a nodes opinion can not be answered they reset the counter for consecutive successful voting rounds which will prevent confirmations. Since nodes need to open some ports to be available for queries it is super easy to DDOS validators and again bring the network confirmations to 0. 📷 Hans Moog [IF]어제 오후 3:05 4. Avalanche still processes transactions in "chunks/blocks"by only applying them after they have gone through some consensus process (gathered enough successfull voting rounds),which means that the nodes will waste a significant amount of time where they "wait" for the next chunk to be finished before the transactions are applied to the ledger state. IOTA tries to streamline this process by decoupling consensus and the booking of transactions by using the "parallel reality based ledger state" which means that nodes in IOTA will never waste any time "waiting" for decisions to be made. This will give us much higher throughput numbers. 📷 Hans Moog [IF]어제 오후 3:11 5. Avalanche has some really severe game theoretic problems where nodes are incentivized to attach their transactions to the already decided parts of the DAG because then things like conflict spam won't affect these transactions as badly as the transactions issued by honest nodes.If however every node would follow this "better and selfish" tip selection mechanism then the network will stop to work at all. Overall the "being able to stop consensus" might not be too bad since you can't really do anything really bad (i.e. double spend) which is why we might not see these kind of attacks in the immediate future but just wait until a few DeFi apps are running on their platform where smart contracts are actually relying on more or less real time execution of the contracts. Then there might be some actual financial gains to be made if the contract halts and we might see alot of these things appear (including selfish tip selection). Avalanche is barely a top 100 project and nobody attacks these kind of low value networks unless there is something to be gained from such an attack. Saying that the fact that its live on mainnet and hasn't been attacked in 3 weeks is a proof for its security is completely wrong. Especially considering that 95% of all stake are controlled by avalanche itself If you control > 50% of the voting power then you essentially control the whole network and attacks can mostly be ignored I guess there is a reason for avalanche only selling 10% of the token supply to the public because then some of the named problems are less likely to appear 📷 Navin Ramachandran [IF]어제 오후 3:21 I have to say that wtf's suggestion is pretty condescending to all our researchers. It seems heavy on the troll aspect to suggest that we should ditch all our work because iota is only good at industrial adoption. Does wtf actually expect a response to this? Or is this grand standing? 📷 Hans Moog [IF]어제 오후 3:22 The whole argument of "why don't you just use X instead of trying to build a better version" is also a completely idiotic argument. Why did ETH write their own protocol if Bitcoin was already around? Well because they saw problems in Bitcoins approach and tried to improve it. 📷 Hans Moog [IF]어제 오후 3:27 u/NavinRamachandran [IF] Its like most of his arguments ... remember when he said we should implement colored coins in 2nd layer smart contracts instead of the base layer because they would be more expressive (i.e. turing complete) completely discarding that 2nd layer smart contracts only really work if you have a consensus on data and therefore state for which you need the "traceability" of funds to create these kind of mini blockchains in the tangle? Colored coins "enable" smart contracts and it wouldnt work the other way round - unless you have a platform that works exactly like ETH where all the nodes validate a single shared execution platform of the smart contracts which is not really scalable and is exactly what we are trying to solve with our approach. 📷 Navin Ramachandran [IF]어제 오후 3:28 Always easier to criticise than build something yourself. But yet he keeps posting these inflammatory posts. At this point is there any doubt if he is making these comments constructively? 📷 Hans Moog [IF]어제 오후 3:43 If he at least would try to understand IOTAs vision ... then maybe he wouldn't have to ask things like "Why don't you just copy a tech that only works with fees" 📷 Hans Moog [IF]어제 오후 4:35 u/Shaar
I thought this would only be used to 'override' finality, eg if there were network splits. But not in normal consensus
That is not correct. Every single transaction gets booked on arrival using the parallel reality based ledger state. If there are conflicts then we create a "branch" (container in the ledger state) that represents the perception that this particular double spend would be accepted by consensus. After consensus is reached, the container is simply marked as "accepted" and all transactions that are associated with this branch are immediately confirmed as well. This allows us to make the node use all of its computing ressources 24/7 without having to wait for any kind of decision to be made and allows us to scale the throughput to its physical limits. That's the whole idea of the "parallel reality based ledger state" instead of designing a data structure that models the ledger state "after consensus" like everybody else is doing it is tailored to model the ledger state "before consensus" and then you just flip a flag to persist your decision. The "resync mechanism" also uses the branches to measure the amount of approval a certain perception of the ledger state receives. So if my own opinion is not in line with what the rest of the network has accepted (i.e. because I was eclipsed or because there was a network split), then I can use the weight of these branches to detect this "being out of sync" and can do another larger query to re-evaluate my decision.(수정됨)
Also what happens in IOTA if DRNG notes would fall out, does the network continue if no new RNGs appear for a while? Or will new nodes be added sufficiently fast to the DRNG committee that no one notices?
Its a comittee and not just a single DRNG provider. If a few nodes fail then it will still produce random numbers. And even if the whole comittee fails there are fallback RNG's that would be used instead 📷 Hans Moog [IF]어제 오후 4:58 And multiverse doesn't use FPC but only the weight of these branches in the same way as blockchain uses the longest chain wins consensus to choose between conflicts. So nodes simply attach their transactions to the transactions that they have seen first and if there are conflicts then you simply monitor which version received more approval and adjust your opinion accordingly. 📷 Hans Moog [IF]어제 오후 5:07 We started integrating some of the non-controversial concepts (like the approval reset switch) into FPC and are currently refactoring goshimmer to support this We are also planning to make the big mana holders publish their opinion in the tangle as a public statement, which allows us to measure the rate of approval in a similar way as multiverse would do it So its starting to converge a bit but we are still using FPC as a metastability breaking mechanism Once the changes are implemented it should be pretty easy to simulate and test both approaches in parallel 📷 Serguei Popov [IF]어제 오후 5:53
So the ask is that we ditch all our work and fork Avalanche because it has not been attacked in the month or so it has been up?
u/NavinRamachandran [IF] yeah, that's hilarious. Avalanche consensus (at least their WP version) is clearly scientifically unsound. 📷 Hans Moog [IF]어제 오후 9:43 u/wtfmaybe you should research avalanche before proposing such a stupid idea and you will see that what I wrote is actually true 📷 Hans Moog [IF]어제 오후 9:44 paying fees is what "protects" them atm and simply the fact that nobody uses the network for anything of value yet we cant rely on fees making attack vectors "inattractive" 📷 Serguei Popov [IF]어제 오후 10:17
well (1.) very obviously the metastability problems are not a problem in practice,
putting "very obviously" before questionable statements very obviously shows that you are seeking a constructive dialogue📷(to make metastability work, the adversary needs to more-or-less know the current opinion vectors of most of the honest participants; I don't see why a sufficiently well-connected adversary cannot query enough honest nodes frequently enough to achieve that)
(2.) .... you'd need an unpredictable number every few tens/hundreds milliseconds, but your DRNG can only produce one every O(seconds).
the above assumption (about "every few tens/hundreds milliseconds") is wrong
We've had this discussion before, where you argued that the assumptions in the FPC-BI paper (incl. "all nodes must be known") are not to be taken 100% strictly, and that the results are to be seen more of an indication of overall performance.
Aham, I see. So, unfortunately, all that time that I invested into explaining that stuff during our last conversation was for nothing. Again, very briefly. The contents of the FPC-BI paper is not "an indication of overall performance". It rather shows (to someone who actually read and understood the paper) why the approach is sound and robust, as it makes one understand what is the mechanism that causes the consensus phenomenon occur.
Yet you don't allow for that same argument to be valid for the "metastability" problem in avalanche,
Incorrect. It's not "that same argument". FPC-BI is a decent academic paper that has precisely formulated results and proofs. The Ava WP (the probabilistic part of it), on the other hand, doesnotcontain proofs of what they call results. More importantly, they don't even show a clear path to those proofs. That's why their system is scientifically unsound.
even when there's a live network that shows that it doesn't matter.
No, it doesn't show that it doesn't matter. It only shows that it works when not properly attacked. Their WP doesn't contain any insight on why those attacks would be difficult/impossible. 📷 Hans Moog [IF]어제 오후 10:56 That proposal was so stupid - Avalanche does several things completely different and we are putting quite a bit og effort into our solution to pretty much fix all of Avalanches shortcomings If we just wanted to have a working product and dont care about security or performance then we could have just forked a blockchaib I am pretty confident that once we are done - its going to be extremely close to the besttheoretical thresholds that DLTs will ever be able to achieve for an unsharded baselayer ------------------------------------------------------------------------------------------------------------- 📷 Bas어제 오전 2:43 Yesterday I was asked how a reasonably big company no one has heard of could best move forward implementing Access for thousands of locations worldwide. (Sorry for the vagueness, it’s all confidential.) They read the article and want to implement it because it seems to fit a problem they’re currently trying to solve. Such moves will vastly increase the utility of protocols like IOTA, and is what the speculation is built on. I do not think you can overestimate what impact Access is going to have. It’s cutting out the middleman for simple things; no server or service needed. That’s huge. So yes, I think this space will continue to growu/Coinnave -------------------------------------------------------------------------------------------------------------- 📷 Angelo Capossele [IF]2020.10.02. In short: we are planning a new v0.3.0 release that should happen very soon. This version will bring fundamental changes to the structure of the entire codebase (but without additional features) so that progressing with the development will be easier and more consistent. We have also obtained outstanding results with the dRNG committee managed by the GoShimmer X-Team, so that will also be integral part of v0.3.0. After that, we will merge the Value Tangle with the Message Tangle, so to have only one Tangle and make the TSA and the orphanage easier to manage. And we are also progressing really well with Mana, that will be the focus after the merge. More or less this is what is going to happen this month. We will release further details with the upcoming Research Status Update📷
Taproot! Everybody wants to have it, somebody wants to make it, nobody knows how to get it! (If you are asking why everybody wants it, see: Technical: Taproot: Why Activate?) (Pedants: I mostly elide over lockin times) Briefly, Taproot is that neat new thing that gets us:
Multisignatures (n-of-n, k-of-n) that are just 1 signature (1-of-1) in length!! (MuSig/Schnorr)
Better privacy!! If all contract participants can agree, just use a multisignature. If there is a dispute, show the contract publicly and have the Bitcoin network resolve it (Taproot/MAST).
Activation lets devs work get back to work on the even newer stuff like!!!
Cross-input signature aggregation!! (transaction with multiple inputs can have a single signature for all inputs) --- needs Schnorr, but some more work needed to ensure that the interactions with SCRIPT are okay.
Block validation - Schnorr signatures for all taproot spends in a block can be validated in a single operation instead of for each transaction!! Speed up validation and maybe we can actually afford to increase block sizes (maybe)!!
SIGHASH_ANYPREVOUT - you know, for Decker-Russell-Osuntokun ("eltoo") magic!!!
OP_CHECKTEMPLATEVERIFY - vaulty vaults without requiring storing signatures, just transaction details!!
So yes, let's activate taproot!
The SegWit Wars
The biggest problem with activating Taproot is PTSD from the previous softfork, SegWit. Pieter Wuille, one of the authors of the current Taproot proposal, has consistently held the position that he will not discuss activation, and will accept whatever activation process is imposed on Taproot. Other developers have expressed similar opinions. So what happened with SegWit activation that was so traumatic? SegWit used the BIP9 activation method. Let's dive into BIP9!
bit - A field in the block header, the nVersion, has a number of bits. By setting a particular bit, the miner making the block indicates that it has upgraded its software to support a particular soft fork. The bit parameter for a BIP9 activation is which bit in this nVersion is used to indicate that the miner has upgraded software for a particular soft fork.
timeout - a time limit, expressed as an end date. If this timeout is reached without sufficient number of miners signaling that they upgraded, then the activation fails and Bitcoin Core goes back to the drawing board.
Now there are other parameters (name, starttime) but they are not anywhere near as important as the above two. A number that is not a parameter, is 95%. Basically, activation of a BIP9 softfork is considered as actually succeeding if at least 95% of blocks in the last 2 weeks had the specified bit in the nVersion set. If less than 95% had this bit set before the timeout, then the upgrade fails and never goes into the network. This is not a parameter: it is a constant defined by BIP9, and developers using BIP9 activation cannot change this. So, first some simple questions and their answers:
Why not just set a day when everyone starts imposing the new rules of the softfork?
This was done classically (in the days when Satoshi was still among us). But this might argued to put too much power to developers, since there would be no way to reject an upgrade without possible bad consequences. For example, developers might package an upgrade that the users do not want, together with vital security bugfixes. Either you live without vital security bugfixes and hire some other developers to fix it for you (which can be difficult, presumably the best developers are already the ones working on the codebase) or you get the vital security bugfixes and implicitly support the upgrade you might not want.
Sure, you could fork the code yourself (the ultimate threat in the FOSS world) and hire another set of developers who aren't assholes to do the dreary maintenance work of fixing security bugs, but Bitcoin needs strong bug-for-bug compatibility so everyone should really congregate around a single codebase.
Basically: even the devs do not want this power, because they fear being coerced into putting "upgrades" that are detrimental to users. Satoshi got a pass because nobody knew who he was and how to coerce him.
Suppose the threshold were lower, like 51%. If so, after activation, somebody can disrupt the Bitcoin network by creating a transaction that is valid under the pre-softfork rules, but are invalid under the post-softfork rules. Upgraded nodes would reject it, but 49% of miners would accept it and include it in a block (which makes the block invalid) And then the same 49% would accept the invalid block and build on top of that, possibly creating a short chain of doomed invalid blocks that confirm an invalid spend. This can confuse SPV wallets, who might see multiple confirmations of a transaction and accept the funds, but later find that in fact it is invalid under the now-activated softfork rules.
Thus, a very high threshold was imposed. 95% is considered safe. 50% is definitely not safe. Due to variance in the mining process, 80% could also be potentially unsafe (i.e. 80% of blocks signaling might have a good chance of coming from only 60% of miners), so a threshold of 95% was considered "safe enough for Bitcoin work".
Why have a timeout that disables the upgrade?
Before BIP9, what was used was either flag day or BIP34. BIP34 had no flag day of activation or a bit, instead, it was just a 95% threshold to signal an nVersion value greater than a specific value. Actually, it was two thresholds: at 75%, blocks with the new nVersion would have the new softfork rules imposed, but at 95% blocks with the old nVersion would be rejected (and only the new blocks, with the new softfork rules, were accepted). For one, between 75% and 95%, there was a situation where the softfork was only "partially imposed", only blocks signaling the new rules would actually have those rules, but blocks with the old rules were still valid. This was fine for BIP34, which only added rules for miners with negligible use for non-miners.
The reasons miners signalled support was because they felt they were being pressured to signal support. So they signalled support, with plans to actually upgrade later, but because of the widespread signalling, the new BIP66 version locked in before upgrade plans were finished. Thus, the timeout that disables the upgrade was added in BIP9 to allow miners an escape hatch.
The Great Battles of the SegWit Wars
SegWit not only fixed transaction malleability, it also created a practical softforkable blocksize increase that also rebalanced weights so that the cost of spending a UTXO is about the same as the cost of creating UTXOs (and spending UTXOs is "better" since it limits the size of the UTXO set that every fullnode has to maintain). So SegWit was written, the activation was decided to be BIP9, and then.... miner signalling stalled at below 75%. Thus were the Great SegWit Wars started.
BIP9 Feature Hostage
If you are a miner with at least 5% global hashpower, you can hold a BIP9-activated softfork hostage. You might even secretly want the softfork to actually push through. But you might want to extract concession from the users and the developers. Like removing the halvening. Or raising or even removing the block size caps (which helps larger miners more than smaller miners, making it easier to become a bigger fish that eats all the smaller fishes). Or whatever. With BIP9, you can hold the softfork hostage. You just hold out and refuse to signal. You tell everyone you will signal, if and only if certain concessions are given to you. This ability by miners to hold a feature hostage was enabled because of the miner-exit allowed by the timeout on BIP9. Prior to that, miners were considered little more than expendable security guards, paid for the risk they take to secure the network, but not special in the grand scheme of Bitcoin.
ASICBoost was a novel way of optimizing SHA256 mining, by taking advantage of the structure of the 80-byte header that is hashed in order to perform proof-of-work. The details of ASICBoost are out-of-scope here but you can read about it elsewhere Here is a short summary of the two types of ASICBoost, relevant to the activation discussion.
Overt ASICBoost - Manipulates the unused bits in nVersion to reduce power consumption in mining.
Covert ASICBoost - Manipulates the order of transactions in the block to reduce power consumption in mining.
Now, "overt" means "obvious", while "covert" means hidden. Overt ASICBoost is obvious because nVersion bits that are not currently in use for BIP9 activations are usually 0 by default, so setting those bits to 1 makes it obvious that you are doing something weird (namely, Overt ASICBoost). Covert ASICBoost is non-obvious because the order of transactions in a block are up to the miner anyway, so the miner rearranging the transactions in order to get lower power consumption is not going to be detected. Unfortunately, while Overt ASICBoost was compatible with SegWit, Covert ASICBoost was not. This is because, pre-SegWit, only the block header Merkle tree committed to the transaction ordering. However, with SegWit, another Merkle tree exists, which commits to transaction ordering as well. Covert ASICBoost would require more computation to manipulate two Merkle trees, obviating the power benefits of Covert ASICBoost anyway. Now, miners want to use ASICBoost (indeed, about 60->70% of current miners probably use the Overt ASICBoost nowadays; if you have a Bitcoin fullnode running you will see the logs with lots of "60 of last 100 blocks had unexpected versions" which is exactly what you would see with the nVersion manipulation that Overt ASICBoost does). But remember: ASICBoost was, at around the time, a novel improvement. Not all miners had ASICBoost hardware. Those who did, did not want it known that they had ASICBoost hardware, and wanted to do Covert ASICBoost! But Covert ASICBoost is incompatible with SegWit, because SegWit actually has two Merkle trees of transaction data, and Covert ASICBoost works by fudging around with transaction ordering in a block, and recomputing two Merkle Trees is more expensive than recomputing just one (and loses the ASICBoost advantage). Of course, those miners that wanted Covert ASICBoost did not want to openly admit that they had ASICBoost hardware, they wanted to keep their advantage secret because miners are strongly competitive in a very tight market. And doing ASICBoost Covertly was just the ticket, but they could not work post-SegWit. Fortunately, due to the BIP9 activation process, they could hold SegWit hostage while covertly taking advantage of Covert ASICBoost!
UASF: BIP148 and BIP8
When the incompatibility between Covert ASICBoost and SegWit was realized, still, activation of SegWit stalled, and miners were still not openly claiming that ASICBoost was related to non-activation of SegWit. Eventually, a new proposal was created: BIP148. With this rule, 3 months before the end of the SegWit timeout, nodes would reject blocks that did not signal SegWit. Thus, 3 months before SegWit timeout, BIP148 would force activation of SegWit. This proposal was not accepted by Bitcoin Core, due to the shortening of the timeout (it effectively times out 3 months before the initial SegWit timeout). Instead, a fork of Bitcoin Core was created which added the patch to comply with BIP148. This was claimed as a User Activated Soft Fork, UASF, since users could freely download the alternate fork rather than sticking with the developers of Bitcoin Core. Now, BIP148 effectively is just a BIP9 activation, except at its (earlier) timeout, the new rules would be activated anyway (instead of the BIP9-mandated behavior that the upgrade is cancelled at the end of the timeout). BIP148 was actually inspired by the BIP8 proposal (the link here is a historical version; BIP8 has been updated recently, precisely in preparation for Taproot activation). BIP8 is basically BIP9, but at the end of timeout, the softfork is activated anyway rather than cancelled. This removed the ability of miners to hold the softfork hostage. At best, they can delay the activation, but not stop it entirely by holding out as in BIP9. Of course, this implies risk that not all miners have upgraded before activation, leading to possible losses for SPV users, as well as again re-pressuring miners to signal activation, possibly without the miners actually upgrading their software to properly impose the new softfork rules.
BIP91, SegWit2X, and The Aftermath
BIP148 inspired countermeasures, possibly from the Covert ASiCBoost miners, possibly from concerned users who wanted to offer concessions to miners. To this day, the common name for BIP148 - UASF - remains an emotionally-charged rallying cry for parts of the Bitcoin community. One of these was SegWit2X. This was brokered in a deal between some Bitcoin personalities at a conference in New York, and thus part of the so-called "New York Agreement" or NYA, another emotionally-charged acronym. The text of the NYA was basically:
Set up a new activation threshold at 80% signalled at bit 4 (vs bit 1 for SegWit).
When this 80% signalling was reached, miners would require that bit 1 for SegWit be signalled to achive the 95% activation needed for SegWit.
If the bit 4 signalling reached 80%, increase the block weight limit from the SegWit 4000000 to the SegWit2X 8000000, 6 months after bit 1 activation.
The first item above was coded in BIP91. Unfortunately, if you read the BIP91, independently of NYA, you might come to the conclusion that BIP91 was only about lowering the threshold to 80%. In particular, BIP91 never mentions anything about the second point above, it never mentions that bit 4 80% threshold would also signal for a later hardfork increase in weight limit. Because of this, even though there are claims that NYA (SegWit2X) reached 80% dominance, a close reading of BIP91 shows that the 80% dominance was only for SegWit activation, without necessarily a later 2x capacity hardfork (SegWit2X). This ambiguity of bit 4 (NYA says it includes a 2x capacity hardfork, BIP91 says it does not) has continued to be a thorn in blocksize debates later. Economically speaking, Bitcoin futures between SegWit and SegWit2X showed strong economic dominance in favor of SegWit (SegWit2X futures were traded at a fraction in value of SegWit futures: I personally made a tidy but small amount of money betting against SegWit2X in the futures market), so suggesting that NYA achieved 80% dominance even in mining is laughable, but the NYA text that ties bit 4 to SegWit2X still exists. Historically, BIP91 triggered which caused SegWit to activate before the BIP148 shorter timeout. BIP148 proponents continue to hold this day that it was the BIP148 shorter timeout and no-compromises-activate-on-August-1 that made miners flock to BIP91 as a face-saving tactic that actually removed the second clause of NYA. NYA supporters keep pointing to the bit 4 text in the NYA and the historical activation of BIP91 as a failed promise by Bitcoin developers.
We have discussed BIP8: roughly, it has bit and timeout, if 95% of miners signal bit it activates, at the end of timeout it activates. (EDIT: BIP8 has had recent updates: at the end of timeout it can now activate or fail. For the most part, in the below text "BIP8", means BIP8-and-activate-at-timeout, and "BIP9" means BIP8-and-fail-at-timeout) So let's take a look at Modern Softfork Activation!
Modern Softfork Activation
This is a more complex activation method, composed of BIP9 and BIP8 as supcomponents.
First have a 12-month BIP9 (fail at timeout).
If the above fails to activate, have a 6-month discussion period during which users and developers and miners discuss whether to continue to step 3.
Have a 24-month BIP8 (activate at timeout).
The total above is 42 months, if you are counting: 3.5 years worst-case activation. The logic here is that if there are no problems, BIP9 will work just fine anyway. And if there are problems, the 6-month period should weed it out. Finally, miners cannot hold the feature hostage since the 24-month BIP8 period will exist anyway.
PSA: Being Resilient to Upgrades
Software is very birttle. Anyone who has been using software for a long time has experienced something like this:
You hear a new version of your favorite software has a nice new feature.
Excited, you install the new version.
You find that the new version has subtle incompatibilities with your current workflow.
You are sad and downgrade to the older version.
You find out that the new version has changed your files in incompatible ways that the old version cannot work with anymore.
You tearfully reinstall the newer version and figure out how to get your lost productivity now that you have to adapt to a new workflow
If you are a technically-competent user, you might codify your workflow into a bunch of programs. And then you upgrade one of the external pieces of software you are using, and find that it has a subtle incompatibility with your current workflow which is based on a bunch of simple programs you wrote yourself. And if those simple programs are used as the basis of some important production system, you hve just screwed up because you upgraded software on an important production system. And well, one of the issues with new softfork activation is that if not enough people (users and miners) upgrade to the newest Bitcoin software, the security of the new softfork rules are at risk. Upgrading software of any kind is always a risk, and the more software you build on top of the software-being-upgraded, the greater you risk your tower of software collapsing while you change its foundations. So if you have some complex Bitcoin-manipulating system with Bitcoin somewhere at the foundations, consider running two Bitcoin nodes:
One is a "stable-version" Bitcoin node. Once it has synced, set it up to connect=x.x.x.x to the second node below (so that your ISP bandwidth is only spent on the second node). Use this node to run all your software: it's a stable version that you don't change for long periods of time. Enable txiindex, disable pruning, whatever your software needs.
The other is an "always-up-to-date" Bitcoin Node. Keep its stoarge down with pruning (initially sync it off the "stable-version" node). You can't use blocksonly if your "stable-version" node needs to send transactions, but otherwise this "always-up-to-date" Bitcoin node can be kept as a low-resource node, so you can run both nodes in the same machine.
When a new Bitcoin version comes up, you just upgrade the "always-up-to-date" Bitcoin node. This protects you if a future softfork activates, you will only receive valid Bitcoin blocks and transactions. Since this node has nothing running on top of it, it is just a special peer of the "stable-version" node, any software incompatibilities with your system software do not exist. Your "stable-version" Bitcoin node remains the same version until you are ready to actually upgrade this node and are prepared to rewrite most of the software you have running on top of it due to version compatibility problems. When upgrading the "always-up-to-date", you can bring it down safely and then start it later. Your "stable-version" wil keep running, disconnected from the network, but otherwise still available for whatever queries. You do need some system to stop the "always-up-to-date" node if for any reason the "stable-version" goes down (otherwisee if the "always-up-to-date" advances its pruning window past what your "stable-version" has, the "stable-version" cannot sync afterwards), but if you are technically competent enough that you need to do this, you are technically competent enough to write such a trivial monitor program (EDIT: gmax notes you can adjust the pruning window by RPC commands to help with this as well). This recommendation is from gmaxwell on IRC, by the way.
[RESOLVED] On Unconfirmed History/Balance Inconsistencies
You may have noticed some issues with unconfirmed transactions lately and things have only been resolving after confirmations. First of all: Welcome to Bitcoin :) I went to the bottom of the issues and it turned out there was a bug in the full node software we were using to broadcast transactions: Bitcoin Knots 0.19. I upgraded the backend yesterday with Bitcoin Knots 0.20, which has already fixed the bug. However things will take a few days to fully resolve (probably 99% of issues have already resolved though) as the backend's mempool have to get in sync with the mempools of other nodes on the network.
About the bug
It turns out when you broadcast transactions to Knots .19 through RPC, it allowed double spending (without RBF.) So, if it's fixed why does it take a few days to fully resolve? Consider the following event:
Yesterday, after I upgraded the backend with the proper full node I participated in the first coinjoin. It happened and even my own personal Bitcoin full node accepted it. But when I looked at it in various block explorers it turned out they were not aware of it. What's going on here?
I traced back that one of the input has participated in another coinjoin that neither the backend, nor my local full node knew about. So everything worked properly based on what the Wasabi software knew about the network.
However this first coinjoin had to confirm in order for my local full node and for the backend's full node to be aware of it and realize it's the tx that actually happened. But why weren't the full nodes aware of it in the first place?
My local full node was not turned on at the time when that first coinjoin happened. This is how Bitcoin Core works, when it's restarted it doesn't start asking for full mempools, but it rather works with what it has.
The backend's full node did know about the first coinjoin tx, but because of the double spend bug, it threw that out. However with the correct full node version the correct mempool did still not instantly came back, but right now it's working correctly with the wrong mempool and in a few days as transactions are confirming everything will be back to normal, if not already.
If you are still experiencing this issue 3 days after my post, try to turn Wasabi off, then turn it on again. Update: We discussed the issue with Luke, the maintainer of Knots and it turns out I mistested Knots .20 as the bug isn't fixed there. But it turns out the issue wasn't a Knots bug, but a Knots feature that we were not aware of and adding adding mempoolreplacement=fee,optin bitcoin.conf option finally resolved the issues. As a summary: the exact same recommendations apply what I noted above, it's just the reason isn't what I originally thought it is.
✴Bitcoin Customer Service +▶𝟏⥂𝟪𝟦𝟦⥂𝟗𝟭𝟎⥂2𝟑𝟎𝟭 Phone Number Customer Care Number ✴USA CANADA $#[email protected]#@",>>✴
Bitcoin is Customer Password chief and all specialized Support needs effective Bitcoin Customer Service has a Phone number For all Kind of client care for Bitcoin establishment mistake uphold telephone number Bitcoin is astounding assistance programming that is widely utilized by a huge number of clients. the most effective method to secret key not working. Bitcoin uphold telephone number will fix issues of Antiviruss specialized focus will assist you with client support care for moment ink It blesses effortlessly of access and flexibility to its clients. Bitcoin webmail guarantees top of the line security by utilizing secure encryption strategy for correspondence and information sharing by means of messages. Street Runner proffers plentiful scope of web mail administrations, prompt responsiveness and direct arrangements, strong group of experts, 24 X 7 constant backings, solid management and specialized or non specialized help over a call by means of helpline numbers. Bitcoin CUSTOMER SERVICE NUMBER Bitcoin is remarkable webmail administration programming that is generally utilized by a great many clients. It blesses without any difficulty and adaptability to its clients and thus Road Runner has picked up notoriety among its rivals whether expert or private. Bitcoin webmail gives high email security by utilizing secure encryption for messages. Security, Confidentiality and Ease of access are the engaged zones that make Road Runner not quite the same as different contenders. An uncommon alternative of "Permit and Block" is given by the webmail on the off chance that you are getting irritated by email from a particular mail id. Bitcoin Customer Care Number New clients may confront challenges in managing not many of its development includes yet once they get the necessary comprehension of executing it essentially to their everyday schedule they will acknowledge how keen work helps in this serious world. KEY FEATURES OF ROAD RUNNER EMAIL: Huge location book: Huge location space is given to store every one of your contacts at one advantageous and secure spot that can be gotten to whenever, anyplace. Primary Email with 5 Sub email accounts: An essential email account with 5 sub email accounts are permitted with discrete capacity limit exclusively. Secure messaging: Bitcoin gives very good quality security to the protected stockpiling of your information alongside the start to finish scrambled security for the sends sent and got. Parental controls: This alternative gives you a simplicity of psyche since utilizing this component you don't need to stress over the children interfering with your stuff No-limit stockpiling: Bitcoin offers huge extra room for each email account. You will have sufficient of extra room that you don't need to stress over the size of your records. Comprehensive spam insurance: Automatic spam security is given to every one of its clients. BEING A HIGHLY SECURED EMAIL Bitcoin SECURITY FEATURES INCLUDE: Complete sweep for infections. Highly created security choices Complete spam control Automatic dispose of for tainted messages Automatic erase for garbage/spam messages Despite of these you can really send the hefty documents in a single mail by taking up the alternative of a paid part. Being a perpetual and paid part at financially savvy and pocket inviting costs lets you remembered from the problem of packing the documents for the sends and trading off with the quality. SETTING UP A Bitcoin EMAIL: Creating a Bitcoin email account is a straightforward and inconvenience free errand. All you need is to choose onto making one and for that its highlights are sufficient that pulls in you towards making an email id for using the favorable circumstances gave by Road Runner Email. Simply follow the couple of steps and you are good to go to exploit site. STEPS TO CREATE RR EMAIL: Go to range net authority page. Click on Create account/Create Username to begin with making another one. Enter the subtleties requested enrollment. Complete the enlistment and confirm the record to sign in to the record. Log in to the record by entering sign in id and secret word. Go to menu and snap on oversee account alternative Select web and snap on make email address choice You will see a brief and will get your email subtleties Click on make letter box and enter the secret key. in the event that you overlooked the secret word of the email you can at present access your record by experiencing a basic methodology for resetting it and you can get to a similar record whose secret word you couldn't recollect. Go to the Spectrum Webmail page. Click on Forgot Password? Select I don't have the foggiest idea about my email secret key. Enter your Email Address. Select the "I'm not a robot" check box, and Submit. Enter your link modem ID (MAC address) Enter the Answer to a security confirmation question. Select Reset Password. Generate another secret phrase. Setting up your record is simple however alongside these settings is a significant point that you have to underscore on. You won't have the option to exploit Road sprinter's administrations if the settings are not accurately done by you. Your programmed settings are unique and on the off chance that you physically set up your settings than you will have the option to oversee everything pleasantly and freely. Bitcoin POP SETTINGS: A steady and solid web association is everything you require to start RR webmail account and enter POP settings: Open the Bitcoin email on your gadget Click on the settings Opt for manual worker settings and snap on the POP settings. Construct the record type as POP or POP3 Modify the approaching worker mail to twc.com Modify the approaching worker port to 110 Mark security type as none for the port Modify the active worker to twc.com Modify the active worker port to 587 Mark the security type as None Enter the Bitcoin email address Enter the secret key Click on the done and you are finished with POP settings Bitcoin IMAP SETTINGS Open the Bitcoin email on your gadget Provide the login accreditations Click on the manual set up choice and un-tick the programmed design SELECT THE IMAP SETTINGS AND MAKE THE CONFIGURATIONS AS FOLLOWS: Mark the record type as IMAP Modify the approaching worker to:twc.com Modify the approaching mail worker port to 143 Mark the security type as SSL/TLS and security type as None Modify the active worker to: twc.com Modify the active port to 587 Modify the security type to none and imprint the unreliable port as none Enter the email id and secret word Deselect the alternative of the safe worker Deselect the choice of the confirmed endorsement After the confirmation by the SMTP worker, you will be made to the following stride Enter the qualifications again Click Next Enter the record name to be shown and you are finished. The benefits of Bitcoin messages are everlasting. You simply need to find out increasingly more about it to get its best utilization. If there should arise an occurrence of any sort of specialized or non specialized issue experienced you can straightforwardly take the help from the client assistance administration to get moving. For what reason to sit around fathoming an experienced issue when you can really get it settled by the specialized help group inside only couple of moments. REASONS FOR ENCOUNTERING ISSUES: Issues with the worker Incorrect login accreditations Inappropriate arrangement of the workers Incorrect IMAP or POP settings Network issues COMMON PROBLEM SOLVING TIPS: on the off chance that you are getting issue in accepting mail that may because of organization issue or settings issue, attempt to change the settings as referenced previously. Inactive records get secured so case you have to choose TWC login email to initiate the record once more. Test mail can be utilized to check the issue of sending sends. Encountered email gives that may be tended to by email setup. FEW ISSUES THAT MIGHT FORCE YOU TO CONTACT CUSTOMER SERVICE: Issues in Signing in or Signing up. Blocked mail account. Issue with sending or accepting email. Road Runner not working. Not ready to dispose of spam. Could not synchronize sub clients with email. Bitcoin email account bolted. Too much time utilization for sending and accepting messages. Issues with respect to the SMTP worker. Errors in singing in your record. Syncing issues with respect to the contact of Bitcoin email. Inbox the board of your Bitcoin email account. Problem in resetting your secret phrase. Road Runner Email administration ensures the issue settling in only couple of moments with the assistance of gifted and experienced client support chiefs. Tending to the clients concerns is the principle intention of Road Runner group. Keeping in the brain that any sort of issue looked in the middle of the work with respect to email is an excessive amount of disappointing and makes the temperament excessively low if not figure everything out on schedule, an accomplished group is only a summon and you will get the issue tended to inside couple of moments and you are simply in the groove again taking focal points of this astonishing help. HOW TO REACH Bitcoin TECHNICAL SUPPORT? You are only a summon from settling your experienced issues and the helpline contact numbers are accessible on the site from where you can connect with the client assistance heads to get moving. Our client support chiefs are accessible 24 X 7 and are only a summon. WHY TO CHOOSE Bitcoin CUSTOMER SUPPORT? Bitcoin client assistance administration group is included very much prepared and expert people with wanted capability and experience under a similar field. All the people are prepared and tested well for delivering the finest customer service to its customers. 24 X 7 non-stop supports. Immediate and straightforward solutions.A sturdy team of professionals. A sturdy team of professionals. Reliable supervision and support. One stop for all issues. Efficient and time saving. User-friendly. How much time is required to get a response? Your call will be connected instantaneously with the customer service executive and they will provide you the finest solutions in minimal time.
Attempt at an unbiased summary of the IOTA attack by a non-bag holder
On February 12th the IOTA Foundation (IF) posted a status update:
February 12th 2020 - 08:55 After receiving several reports of fund theft that looked out of the ordinary in a short timeframe we decided to warn about this in Discord and on Twitter. As a precaution we ask you to keep your Trinity wallet closed for now.
25 minutes later they decide to shut down the "coordinator", blocking all "value" transactions.
February 12th 2020 - 09:20 After initial investigation we decided to turn off the Coordinator to make sure no further theft can occur until we find out the root cause of these thefts. Further investigation taking place from here on.
They then spend 5 days investigating the theft. After about 24 hours, only about 10 people reported that they had been stolen from/were identified.
February 13th 2020 - 07:45 We've shifted the complete focus of all relevant resources of the IOTA Foundation to this investigation last night and we have been working in teams to investigate impact and cause together with the identified victims. The conclusions so far are: - Most evidence is pointing towards seed theft, cause still unknown and under investigation - Victims (around 10 that identified with the IOTA Foundation so far) all seem to have recently used Trinity
However, it seems by examining at the transactions that they knew were associated with the theft and were able to identify some new thefts.
February 14th 2020 - 05:45 ... The investigation has yielded absolutely no indication that there has been a core protocol breach of any kind. Rather, all evidence so far points to a problem with a dependency of the Trinity wallet. The attack pattern analysis showed that the halt of the coordinator interrupted the attacker's attempts to liquidate funds on exchanges. The stolen funds have been purposely and repeatedly merged and split to obfuscate the investigation, and with the current token exchange rate as well as exchanges' KYC limits in mind. We received additional feedback from more exchanges (not all yet), confirming that none of the identified transactions has been received or liquidated. Our current assumption is that the perpetrator targeted high value accounts first, before moving on to smaller accounts and then being interrupted early by the halt of the coordinator. (Again: Hardware wallet users are not affected.)
To me, the details sound like the perpetrator was experienced and knew how to convert the tokens to a less-centralized cryptocurency without KYC/AML. It wasn't simply a crime of opportunity, but rather there was some planning. There was a lot of speculation over whether or not the hacker was "sophisticated". Of course, he did manage to pwn IOTA's official wallet. However, the "Chairman of the Board" of IOTA wrote "Let's just say theres a lot of traces. The attacker does not seem to have been tоо sophisticated", on discord. Screenshot On February 16th, IF released a new version of their wallet.
Trinity Desktop 1.4.1 is out. ... - Update: Remove exchange support (#2565) - Update: Adjust update alerts and disable auto update (#2566) - Fix: Allow wallet entry when nodes are not in sync (#2563) - Update: New Crowdin translations (#2553) - Fix: Endless loading cycle (#2568)
Two interesting changes are they removed exchange support and they disabled auto updates. IF had recently integrated "Moonpay"in their wallet, which allows users to buy IOTA with their credit cards for a 4.5% fee. Moonpay appears to be affiliated with Roger Ver and Bitcoin.com but I didn't look into this too much. Purely speculation, but it seems that Moonpay may be involved in the key theft. Quite a few users in Discord were reporting that they had trouble with the new version. About 12 hours later they released a new desktop version (1.4.2) with
- Fix: Incorrect alert on password change for some users (#2570)
Fast forward to today, IF released their remediation plan. Basically, if you used their official wallet since December 17th, 2019 then your seed might be compromised. However, they say that the attack didn't really start until January 25th, so the Dec 17th date is out of an abundance of caution. (Note: I'm pretty sure December 17th is when Moonpay integration occurred.) Here's the IF remediation plan from status.iota.org:
February 17th 2020 - 05:47 Here is a short overview of the attack remediation plan and the next steps going forward. Essentially the remediation plan involves three steps: STEP 1: INSTALL UPDATED VERSION OF TRINITY As announced yesterday, we have released an updated version of Trinity which allows you to check your balance and transactions. Please download this newest version of Trinity here and install it over your old version: https://github.com/iotaledgetrinity-wallet/releases/tag/desktop-1.4.1 When you download the new version, MAKE SURE TO CHANGE YOUR PASSWORD AND STORE IT IN A PASSWORD MANAGER. If you have used the same password also for other services or websites, we strongly recommend you change it there, too, as a precaution. By upgrading to this new version of Trinity, you will remove the vulnerability from your wallet and render the hacker incapable of accessing your wallet if s/he has not already done so. STEP 2: MIGRATE YOUR TOKENS TO SAFE SEEDS In the upcoming days, we will release a seed migration tool that will allow users to transfer their tokens to a safe seed. We strongly recommend that ALL users who have opened any version of Trinity (Desktop or Mobile) since the 17th of December 2019 utilize the tool and migrate their tokens to a new, safe seed during the soon-to-be-announced migration period BEFORE the coordinator is re-started. More information on the tool and how to use it will be provided when the tool is published. By migrating your tokens to new, safe seeds prior to the re-start of the coordinator, you will render the attacker incapable of making unauthorized transfers of your tokens if s/he has not already done so. *Note: our current information indicates that the hack started on or around 25 January 2020 and that only Trinity Desktop users’ seeds were potentially compromised. However, out of an abundance of caution, we are nevertheless recommending that ALL users (not only desktop users) who are concerned about possible token loss should migrate their tokens to a new seed. *Note: Ledger Nano users do not need to use the migration tool but a password change is still strongly recommended. STEP 3: RECLAIM YOUR STOLEN TOKENS IF NECESSARY Our current information indicates that only a limited number of bundles were successfully transferred by the attacker out of the true owners’ wallets. We have notified all exchanges of all compromised bundles we are aware of so as to prevent any further movement of any stolen tokens. We therefore anticipate that in the majority of cases, Steps 1 and 2 will be sufficient to protect most users’ tokens. To address the minority of cases in which unauthorized token transfers were made out of users’ wallets, a third step is needed. We will perform a global snapshot of the network that will, pending community validation, enable us to bring stolen tokens back to the affected users. More information on the process as well as the consequences for all affected users will be provided soon. Assuming the snapshot is successfully validated by the IOTA community (node operators), we will implement a KYC procedure involving a third party that will enable all users who had their tokens stolen to reclaim them. The same procedure will also be required for certain cases in which the migration tool is used fraudulently or incorrectly. More information on this process will follow shortly. After the migration process, we will restart the coordinator and resume normal operations on the network. An update on the timeline will be released in the upcoming days. We will publish detailed instructions on the steps users should take as soon as the remediation tools and processes are ready. For now, please make sure to download the new Trinity version to change your password and check your balance. We would also like to ask any affected users from the United States to come forward and DM our team, as your cooperation could assist us with ongoing law enforcement investigations. Thank you all for your patience. We will continue to update you on all important steps along the way and will do our best to make the transition as easy and smooth as possible.
So yea, if you got your tokens stolen, they will return them to you after you submit KYC/AML to the IOTA Foundation, assuming that "node operators" agree to roll back the theft. Hopefully users didn't reuse the same seed for another cryptocurrency because they won't be able to roll those back. It sounds like they're working with the FBI (or US law enforcement) on this which is a bit surprising. I'm skeptical that they have really identified the perpetrator -- a common attack is to steal developer Github credentials which could be what happened here. But again, that's purely speculation. Please don't repost this on your for-profit crypto news site without attributing to me ;) edit: formatting
I know lots of people are going to jump on and downvote me and say thaiphoon is safe. and to be honest, I'm not 100% sure that thaiphoon is what caused this, but the timing between the events make it hard to think it was just a coincidence. So please please hear me out first: I was talked into syncing my memories because my BF5 stuttering "must be a memory syncing issue", and multiple people both referred me to this video "https://www.youtube.com/watch?time_continue=376&v=KOqhyVNPhaM&feature=emb_logo". Which askes users to download thaiphoon burner and the DRAM calculator developed by a guy in Ukraine. When I try to execute the programs, windows warned me against it since it was trying to make changes to my system, so I hesitated and looked around online, and most people say that thaiphoon burner is known to be safe and will trigger most antivirus as false positive, so I went against my guts and ran it. I am usually a very very careful person but I was desperate to try to fix my stuttering issues, and the fact that everyone is using it and it's recommended by a youtube with 400k subscribers, what could go wrong right? So I let that program run. The next morning when I was trying to do a virus scan (which I should have before I ran it) I found all my antivirus programs, avira, windows defenders, ALL DELETED, without a trace, vanished, windows won't update, system got corrupted, windows defender is blank screen, all gone, antivirus, firewall? Gone. And running that program was absolutely the only thing that could possibly have caused this, the only thing else I did yesterday was watched some youtube videos , absolutely no other changes to my system what so ever, de nada. And even the night before my avira and windows defender were both still running. When I tried to update my windows it would give me an error code and would not allow me to update to fix me security issues, and when I reinstsalled avira clicking on "security scan" does absolutely nothing. I honestly have no idea what could have caused this besides having ran thaiphoon burner, it's just too big of a coincidence. Oh, and 2 days after that, I got a blackmail email (looks auto generated) with my old windows password telling me they got lots of my other passwords too and if I don't want to have embarrassing videos/photos of me distributed to my friends on "that social media site you use"(no seriously, those were their exact words, lol), I was to give 2000 dollar worth of bitcoin to them. All this just seems... way too convenient to be a coincidence. I waited 2 weeks to talk about this, because I thought that the only reply I will get is people telling me how thaiphoon couldn't have done that and I must have done something else to cause the malware/virus. But look, I really am generally a very careful person (due to my paranoia), I keep my av and malwarebytes up to date and scan regularly and I am careful with what links I click on and such. I am generally very careful and this was the only mistake I know I could have made. I still decided to post about this because A. If there's anyone who can help / give me an ease of mind, I think you guys would be it. B. If this really IS a security issue, I would like to let you guys know. I can't remember the version of thaiphoon burnedram calculator I downloaded, but it was whatever it was about 2 weeks ago. I have already formatted my SSD and reinstalled windows, but I can never know if this really fixed the issue, I can never know if other devices on my wifi also got virus, if it's still lingering in my network, I have a backup folder that I don't even dare opening because I'm worried it would spread the virus back to my new system, and who knows what personal info has already been stolen from me, if I could go back 2 weeks ago, I would not buy the lottery or make money off of stocks, I would tell myself not to download or run thaiphoon burner so that I can focus on studying instead of stressing over this for 2 weeks. TL:DR: Ran thaiphoon burner and DRAM calculator 2 weeks ago, next morning when I check my antivirus programs they were all uninstalled. Update: I found this older thread on this sub: https://www.reddit.com/overclocking/comments/c0xutx/trojan_in_thaiphoon_burne It seems like they indeed had some security concerns on their website regarding its certificate and actually having some malicious executable, I wonder if it is still the case?
NOOBS GUIDE - How not to get your bitcoin stolen on Empire Market and verify any empire site
Hi guys and gals, I have made this guide because as some of you have probably experienced before there are tons of phishing sites that are mimicking empire market. Lots of them are very credible but steal your bitcoins. The most convincing phishing sites use a 'man in the middle' attack where it directs traffic to the original empire market site, but changes the bitcoin deposit address. People fall for this because the nature of the attack means that the users individual personal phrase is displayed correctly and everything seems to be normal but when you deposit, the coins disappear. This has led many users to falsely blame empire market and assume they are conducting an exit scam which is not true. Firstly I would like to say to avoid this you must have a critical mindset of every empire market onion url you visit. Even if it has worked several times before. I will detail in this guide how to stop getting your money stolen and this is for educational purposes only. I do not take responsibility for anything you buy on the site. Please let me know if there is anything you would like added to the guide and I will aim to do so. I would also appreciate if everyone could upvote this and if the mods could sticky this so we can get maximum views to stop people getting scammed. With that out of the way, I am assuming you know how to use PGP. if you don't please research how to do this before you continue, the following links may help you (if there is enough demand I will eventually make a separate tutorial on this): http://www.bitcoinnotbombs.com/beginners-guide-to-pgp/ https://www.reddit.com/SilkRoad/comments/1qh266/guide_pgp_4_n00bz/ The critical requirements you must have before continuing:
you must have some sort of PGP program, i use GPG4WIN and the GPA tool inside it
you must have a PGP public key and PGP private key
you must have Empire Markets official PGP public key imported into your chosen PGP program (i detail how to do this below).
The reason why most people get scammed is because they don't verify their links, and when they have, they use the wrong empire market public PGP key located on the phishing sites. The attackers have set this up to work with their own phishing empire market site. The real empire market PGP key has always been located on dreadditevelidot.onion:
Copy dreadditevelidot.onion into Tor
on the right hand side of the page you will see a link saying '/d/EmpireMarket' click on it
towards the top of the page underneath where it says 'Dread' you should see a button called 'PGP' click on it.
Copy the PGP public key into notepad and save it as a .txt or .asc file and import it into your chosen PGP program (i tend to use GPA as part of the GPG4WIN toolkit but others prefer to use kleopatra, each to their own it does the same job)
Once you have this key imported name it something like empire market or whatever you wish, this will be the real key that will tell you if any site you are on is genuine or not. It is published only by the creator of empire market. NEVER and I repeat NEVER use the empire market PGP public key located on any empire market url as this can be faked. Only use the one on dreadditevelidot.onion, I hope that is crystal clear. Now in general, what you want to do next is:
take a link from dark.fail e.g. dkndfkn9gfnf.onion(not real) and add '/safe' to the end of it, or alternatively click on 'verify mirror' once you land on the site.
follow the prompts until you see a PGP message displayed for you, copy this into GPA or other program and click 'verify', if all is good you should see a popup saying 'valid signature' and maybe some text highlighted in green. It looks like this:
Now, once you are certain the site is real, you still don't want to trust it 100%. What you want to do is go to the bitcoin deposit page and click 'generate a bitcoin deposit address'. Once that is done, underneath you will see a link saying 'Get PGP signed proof of ownership', click that and go through the prompts (as similar to before on /safe) you will see a PGP and you want to verify that also to make sure the signature is valid. Once you have successful signatures for the previous steps you pretty much have the green light to deposit your bitcoin to that address. However if you are planning on depositing an amount you can't afford to lose, what I would suggest is depositing a small amount first. And if it is successful then you can deposit again later as the site will be confirmed to be genuine. This is an almost fool proof way of ensuring you don't lose your bitcoin if you follow the steps I have mentioned. HOWEVER IT MUST BE STATED THAT EVERY TIME YOU DEPOSIT TO A BITCOIN ADDRESS, YOU HAVE TO GENERATE A NEW BITCOIN ADDRESS AS ANY NEW COINS YOU SEND TO A PREVIOUS ADDRESS WILL BE LOST. To prevent any further losses to your account you can go into your profile and enable 2FA authentication. This essentially ensures that no one can access your account unless they have your private PGP key and also if the .onion you see in the decrypted message doesn't match the url one you are on, it is a phishing site. If you would like a tutorial on how to do this please request it enough times and I will try to find time to write a tutorial up. I am writing this from a position of frustration after losing a large amount of money to scammers and hope that my information can help you. Please take the time to follow all the steps meticulously and feel free to comment if you are having trouble. I work full time so I will try to get back to people when I am free. Please excuse any grammar errors as I wrote this in a rush and plan on editing it based on feedback. Happy Shopping Mods please sticky this, spread the word and lets eliminate the scammers. EDIT: I have had alot of requests from people who still can't successfully verify the mirror. Please make sure when you solve the captcha on the 'verify mirror' link that you copy the whole txt including the signature and the pgp code before you verify. If you are usingdark.failand it still isn't working then retry the captcha a few times becuase there may be a sync issue on the empire market server. For all the other users who still can't get it to work, for these people I think only a video tutorial would help. Also probably better not to login to any site until you have a firm grip of PGP, how it works and how to use it. As you can understand this would take time and i plan on releasing one on the weekend so please stay patient until i have edited and uploaded one on youtube. To make life easier for people I also plan on uploading empire markets PGP key to a download website, but I am hesitant to do this because I don't want anyone to half follow the instructions and then blame me if they lose their bitcoin. EDIT [8 JULY 2019]: i apologise again for my delays, i live a very busy life. However please read the following information for those of you who are still having trouble verifying your links. I have ascertained the reason why some people are still get invalid signatures (note this is different to a 'bad signature'). The reason why is because kleopatra doesnt recognise where this key is coming from as its not part of the pgp network (not 100% accurate explanation but as noob friendly of an explanation i can give). To fix this what you need to do is certify the key in kleopatra:
Open kleopatra, you should see a collection of public and private pgp keys including your own.
Look for the empire market key and right click on it, then click certify
Follow the prompts and certify it against your own pgp key. (You may need to enter your password)
Once its all done you should see somewhere on the final dialog box where it says certification successful. (If not try it again)
Now when you go through this tutorial again if the key is valid you should definitely see 'good signature' displayed in GPA.
Smile and enjoy your hard work and patience of going through the tutorial.
Disclaimer: This is my editing. So there could be some misunderstandings. Even ifu/longfldposted similar screenshots already(thanks to him/her), I'd like to share this summary again, 'cause it has some more contents. Sometimes, we need more enjoyable stuff to read on this rough, dynamic ride to a new world. 2/18 *** Here's to the crazy ones. The misfits. The rebels. The troublemakers. The round pegs in the square holes. The ones who see things differently. They're not fond of rules. And they have no respect for the status quo. You can quote them, disagree with them, glorify or vilify them. About the only thing you can't do is ignore them. Because they change things. They push the human race forward. And while some may see them as the crazy ones, we see genius. Because the one who are crazy enough to think they can change the world are the ones who do. *** from 'think different' ad campaign TCP/IP TCP/IP, or the Transmission Control Protocol/Internet Protocol, is a suite of communication protocols used to interconnect network devices on the internet. TCP/IP specifies how data is exchanged over the internet by providing end-to-end communications that identify how it should be broken into packets, addressed, transmitted, routed and received at the destination. DAPP DApp is an abbreviated form for decentralized application. A DApp has its backend code running on a decentralized peer-to-peer network. Contrast this with an app where the backend code is running on centralized servers. Ontology a set of concepts and categories in a subject area or domain that shows their properties and the relations between them. Hans Moog [IF]어제 오후9:00 [about the release of GoShimmer v0.2.0?] Originally we wanted to release the new version end of next week but due to the hack this might be a bit delayed but yeah we have a pretty concrete plan the next version will be pretty interesting as it will introduce the changes that will turn IOTA into a general purpose DLT platform that can run pretty much anythingthat is even remotely related to DLT on it I will write a bit more about that when there is time (maybe even do a video) Hans Moog [IF]어제 오후9:02 value transfers will essentially be the first DAPP that runs on the tangle so we need that before we can integrate the ledger Hans Moog [IF]어제 오후9:04 [are you talking about the atomic transaction layout?] not just that also a different layered architecture which we call "the ontologies concept" but its one of the building blocks yeah tangle will essentially be like the decentralized version of TCP/IP a general purpose protocol once value transfers are implemented I have already a few interesting ideas for additional DAPPS Coordicide is pretty "complex" as it requires a lot of different protocols - being able to completely separate the building blocks makes it much easier to get them "secure" Hans Moog [IF]어제 오후9:08 the decentralized randomness required for FPC will for example be an app running on the tangle DRAND App Hans Moog [IF]어제 오후9:14 [about the new ontologies concept] It's not really layed out in a public forum post yet butwe discussed and finalized the specs on the last research summit last week Hans Moog [IF]어제 오후9:19 [isn't this new ontology almost like part of multiverse consensus?] yes a lot of the idea that were part of the original multiverse concepts are useful also for the current coordicide we will for example be able to separate the fate of data transactions and value transactions,which means that you can send data txs without having to be worried that they are rejected, because they attach to a double spend, which is a requirement for a general purpose protocol anyway Hans Moog [IF]어제 오후9:20 [that sounds awesome!! To have a "base" tangle, and on this base tangle different "subtangles" for different applications - value transfers, DRAND, messaging, ...] Archiving, DRAND, chat, MAM, DID, ... you could even have phone calls on the tangle Hans Moog [IF]어제 오후9:21 but i guess for these kind of things it makes more sense to have a 1:1 connection its extremely simple the point is that it makes the code much simpler Hans Moog [IF]어제 오후9:22 you can even have different consensus mechanisms next to each other for different apps some apps like decentralized chats for example don't even need consensus or if you want to build a decentralized version of facebook Hans Moog [IF]어제 오후9:22 you don't need consensus here andit not going to be "separate tangles" that have nothing to do with each other everything runs in the same main tangle Hans Moog [IF]어제 오후9:30 it's not very complex - that's the beautiful thing in fact it makes stuff much easier Hans Moog [IF]어제 오후9:31 Maybe I can do a video about it in the coming days writing a network application if you can use TCP/IP is much easier than if you would have to implement the networking from scatchand communicate with the wires in your pc Hans Moog [IF]어제 오후9:39 **[**Is the "base decentralized TCP/IP layer" already spec out and ready to be implemented?As this will become the "heart" of the tangle.] yep its coded already we started merging the code Hans Moog [IF]어제 오후9:44 [Doesn't "DRNG via committee" still make the network somewhat centralized?] Not really. 1. The committee members do not "control" consensus. 2. If committee members get taken offline by for example government intervention, then the next highest mana holder just joins the committee. So you still maintain all the benefits of a decentralized network. resilience against outside actors, no single actor controls the system Hans Moog [IF]어제 오후9:46 [How does commitee get chosen, by who, which parameters?] as the first version of goshimmer we will most probably have a fixed committee of some IF nodes + selected community members, but in the final protocol, the highest mana nodes will just issue a randomness beacon according to the protocol so the committee is dynamic Hans Moog [IF]어제 오후9:47 [Does commitee agree on the same number and then broadcast it or...?] If I am informed correctly, then its based on threshold signatures But I didn't work on that part, so I am not 100% sure how exactly it works its a bit hard to keep track of everything and also code at the same time Hans Moog [IF]어제 오후9:47 we have a few teams in the research department where every team specs one of the building blocks for engineering Hans Moog [IF]어제 오후9:49 [You know perhaps if this drand stuff has been coded already as well?] yeah,but don't ask me in which branch Hans Moog [IF]어제 오후9:49 and it will be adjusted to the new ontologies concepts Hans Moog [IF]어제 오후9:50 [isn't this approach with DAPPs similar to ICT and IXIs?] in a way, yes butits a bit more powerfulnow, as the DAPPS are completely isolated and "rejecting" transactions in one app does not cause all of the transactions that approve it to be rejected in IXI and ICT a chat message would disappear if it approved a double spend Hans Moog [IF]어제 오후9:56 [if Jaguar would implement a new DAPP with a "new coin" on the tangle with a custom DAPP consensus mechanism?] yeah you could create new coins on top of the tangle with their custom consensus mechanism butevery one of these new coins would need to be able to also understand IOTA transfers and the nodes would ultimately have to have mana to be able to take part in the network so if somebody would for example implement bitcoin on top of the tangle, then the bitcoin miners would need to buy IOTA to be able to send messages in the network We will most probably see a lot of companies also build proprietary stuff on the tangle you can even have "private" apps on the tangle that are encrypted so you can have stuff that would require a "private inhouse blockchain" to use the global infrastructure of the tangle its extremely powerful Hans Moog [IF]어제 오후9:59 [making a "new coin" that is private like monero on the basis of the tangle - using a private DAPP? Crazy powerful!] yeah you can have a "privacy coin" on top of the tangle that is maybe not as fast and scalable as IOTA itself and might even have fees Hans Moog [IF]어제 오후9:59 but if people are willing to pay for this extra service then you can have private transactions without having to "leave" the ecosystem and without having to give up scalability for the IOTA base layer Hans Moog [IF]어제 오후10:05 [Crazy powerful! and everything would need IOTAs... Qubic and Oracles would also be a base DAPP on this tangle ...] exactly Hans Moog [IF]어제 오후10:08 [So if i understand correct,other coins on the Tangle would not have a negative impact on the value of the IOTA. Even the other way around.****] IOTA would always be the native coin which would be the fastest and most secure one, yeah if there would ever be a coin that would be faster and more secure, then it would make sense to implement that in IOTA core Hans Moog [IF]어제 오후10:10 [so no transaction will be rejected anymore from the base tangle layer? In the worst case - if in every DAPP consense mechanism this transaction would be rejected, because of double spend or not useful for this DAPP - it is just seen as data transaction?!] yeah more or less you might still have to reattach a value transfer rare edge cases (if your node is out of sync or sth) but you will never have to reattach a "non-value-transfer" or well ... if you attach sth to a part of the tangle that is really old and everybody has snapshotted that already then you would still have to reattach but a tx does not "depend" on other apps anymore so if 1 app says its bad and we want to orphan it, then this happens on another layer Hans Moog [IF]어제 오후10:16 [So weaker nodes may work without ledger, like just a hub?] nah you always need to support iota value transfers for the rate control Hans Moog [IF]어제 오후10:16 [because of the mana?!] but a node that is not interested in the decentralized facebook and only wants to process MAM messages can do so yeah mana is the thing that ties everything together and to know the mana you need to know IOTA value transfers I mean ... you could rely on a centralized service that provides you the mana balances, so even very hardware-constraint nodes could theoretically take part in the network but then you might process a few txs that others drop if this centralized service would give you the wrong balances but the whole point of IOTA is to be shardable and lightweight so you wont need much for the value transfer layer anyway Hans Moog [IF]어제 오후10:21 [Have you ever thought about how much storage (permanode) you need if IOTA becomes the new TCP/IP ?] but if you want to only "issue" transactions and receive your mana by people assigning it to you (i.e. a company remotely loading up their sensors with mana), then you can essentially do that. one of the first applications I will implement is an "archiving APP" that records the activity in the tangle and allows you to "prove" that a certain tx was part of the tangle at some point in the past. recording 100 years of activity in the tangle (independently of the TPS) will require less than 1 GB much less actually the magic of merkle trees Hans Moog [IF]어제 오후10:23 [of all transactions of every DAPP?] yes everything that ever happened in the tangle Hans Moog [IF]어제 오후10:25 [Is the sharding the ontology concept ] nah its not related or well everything is somehow related but these APPS are not the "shards" Hans Moog [IF]어제 오후10:33 its an essential part of coordicide - this is the next step before integrating the value transfers so next major version of goshimmer 2-3 weeks max Hans Moog [IF]어제 오후10:36 [Nice, so value transfers will probably be implemented till the end of march] that's the plan, yeah might be like 1-2 weeks late now due to the hack but we will see we try our best to catch up after this is sorted out Hans Moog [IF]오늘 오전2:24 [so next goshimmer version will be binary too!!!] yes, I think the next (major) goshimmer version will bring a few of the most fundamental changes in how we perceive the protocol as a whole not just binary <-> tinary but also regarding its "expressiveness" and it's really funny because it is essentially just a slight shift of perception regarding the already established principles, that interestingly directly converts into better architecture and simpler code
Bitcoin likely wasn't supposed to come out until sometime in the 2030's to 2040's...
I think a renegade time traveler brought the Bitcoin idea from the future to the past. I think there's an alternate version of reality where the central bankers were let run amuck, and they ended up, fucking shit up so bad for generations forward, something drastic had to be done. Think about the genesis block. Bitcoin, in its entirety, had to be complete, and ready to go, on said auspicious date. January 3rd, 2009 is probably some horrible banking holiday in this alternate timeline. Bitcoin probably fixed the economic woes the bankers had imposed upon the world as soon as it was introduced, but quickly centralized, and bought up by the technocratic elite who were much smarter, and intelligent than the general population at the time in said future. This alternate timeline Bitcoin from the 2030-2040 future, was probably cooler, and more fleshed out than what WE got, however, it was also written in computer languages that might not exist yet, with different syntaxes/rules, and maybe even a diffent mining algo. So this time traveler had one mission, travel to the past, have a copy of alternate timeline Bitcoin as a reference. Rewrite the codebase in a few months in C++. The originator of Bitcoin likely was Japanese, because they figured it out, that the antidote to excess money printing was creating something with a limited supply, and a predictable monetary cycle. 4 years is just enough time to make economic decisions. It's also kinda synced up with the American election cycle. The CIA probably know about time-traveling technologies, so the moment Satoshi got wind that Bitcoin was on their radar, they were out. Satoshi has likely exiled himself here to this timeline, and the time-police are after him. The best thing we could do is name all our children Satoshi Nakamoto, and make their job harder.
What is EPIC CASH? Epic Cash is the final point in the journey toward true P2P internet cash, the cornerstone of a private financial system. The Epic currency aims to become the world’s most effective privacy-protecting form of digital money. In order to fulfill that goal, it satisfies the three principal functions of money: 1. Store of Value — can be saved, retrieved, and exchanged at a later time, and of predictable value when retrieved; 2. Medium of Exchange — anything accepted as representing a standard of value and exchangeable for goods or services; 3. Unit of Account — the unit by which the value of a thing is accounted for and compared. Website: http://epic.tech Whitepapers: http://epic.tech/whitepaper Epic Cash Community: https://t.me/EpicCash Miner Chat: https://t.me/EpicMiners Gitlab: gitlab.com/epiccash Twitter: twitter.com/EpicCashTech Social Media: http://epic.tech/social-media Exchanges: https://epic.tech/service-list Oleg✌🏻 Hello community! Our AMA with EPIC begins🚀 We are very happy to have you here, on our joint AMA👌 So, lets start! The very first question for you. Can you introduce yourself? Max Freeman | Epic Cash | Mimblewimble I’m Max Freeman, which stands for “Maximum Freedom for Mankind” — we believe that the existing fiat money system enslaves people by unfairly confiscating their wealth through inflation. By using an honest money system such as Epic, we can improve the quality of life for billions of people worldwide. Yoga Dude Hello, I am Yoga Dude 🙂 I handle Marketing and PR, in crypto since 2011 started as Bitcoin miner, and in 2014 in Monero, and in 2015 in Ethereum, oh and briefly in DOGE for fun and unexpected profit. Heard about Epic Cash while learning about the Mimblewimble algo and joined the team last year. JLong I am John, Doing the general engineering and managerial work Max Freeman | Epic Cash | Mimblewimble I have been involved in early stage cryptos for the past 3 years, after building a global trading business for the past 20 years. Oleg✌🏻 nice to meet you🙂 Max Freeman | Epic Cash | Mimblewimble Epic is a decentralized community project like Bitcoin or Monero, there is no central authority or corporation involved. We had no ICO and no premine, we had a fair launch at 0 supply last September. Yoga Dude Great to meet everyone :) Oleg✌🏻 Here we go the 1st question for you ~ 1. What is Epic Cash about? Yoga Dude Epic Cash is designed to fulfill Satoshi’s original vision of P2P electronic cash, adjusting for what we learned from Bitcoin, a medium of exchange that is fast, free, open to all, while being private and fungible. We launched in September 2019 as a Proof of Work mineable crypto, without an ICO or a premine. Oleg✌🏻 Look like a real Bitcoin🙂 Yoga Dude with privacy and fungibility 😄 Oleg✌🏻 Sounds cool! move on to the next question… 2. What makes Epic Cash better than Monero or other privacy coins? Max Freeman | Epic Cash | Mimblewimble First off, we have a lot of respect for Monero and other privacy coins, we learned a lot from what they did right and what they did wrong, Our blockchain is much lighter than Monero or Bitcoin, our transaction engine is faster than Monero or ZCash. We use a three mining algo approach to allow more users the ability to obtain Epic Cash. We are a new, highly undervalued, coin and we look great not only for future use but for today's investment. Our blockchain is 90+% smaller than Monero or Bitcoin. Coins such as Zcash have optional privacy. Epic makes all transactions private, and it is impossible to trace movements of coins by watching wallet addresses. Oleg✌🏻 Young and hot😋 security and privacy level is very important now but… 3. Why copy the same supply economics as Bitcoin? Yoga Dude It is hard to compete with the success of Bitcoin today, part of the elegance and the appeal of Bitcoin is the responsible emission rate, terminating at 21million highly sub dividable coins. Like the Bitcoin supply curve, Epic Cash encourages early adopters, and with subsequent halvenings maintains a gradually diminishing flow of additional currency while preserving the overall value. Max Freeman | Epic Cash | Mimblewimble In 2028, the supply of Epic matches that of Bitcoin and they stay in sync until the final coin is mined in 2140. We have 4 halvenings between now and then, which is demonstrated in Bitcoin to drive the value over market cycles. Epic is a chance for people who were late to Bitcoin to ride the wave and not miss their opportunity this time. Oleg✌🏻 Interesting! 4. Why Choose Epic Cash over Grin and Beam? Max Freeman | Epic Cash | Mimblewimble First of all, we have tremendous respect for all Mimblewimble currencies and their talented teams, they all taught us a lot and we are thankful for that. Without sounding too contentious, the choice seems obvious. We offer the same core tech, but with a much more responsible emission curve — Grin is an endless fountain of emission and inflation (60 per second forever), and Beam is even more frontloaded outpacing even Grin’s aggressive emission schedule for the next several years… We respect Grin and Beam, we learned from them, and we believe we are the next evolutionary step. Additionally, as we mentioned earlier, we offer more ways to mine Epic Cash, both with GPU and CPU and ASICs, this gives us more potential users and miners, vs Grin and Beam that are only mineable with GPUs. Yoga Dude Yes, all that ☝️😄 Oleg✌🏻 I hope the miners read it all carefully 👌 Next question 5. Why have a development fund tax and what will it be used for? Yoga Dude Dev fund tax today is at a reasonable 7.77% dropping by 1.11% every year until it hits zero. As Epic Cash grows in value these funds will become increasingly more relevant in additional technical, marketing, and fintech partnerships developments. Oleg✌🏻 Very smart! 6. What is the advantage of 3 mining algorithms? Max Freeman | Epic Cash | Mimblewimble By having multiple mining algorithms we are able to attract CPU, GPU, and ASIC miners simultaneously. Currently all other Mimblewimble currencies are mineable with GPU only ignoring a large segment of CPU miners. Monero made a splash migrating to the RandomX CPU mining algo. Epic Cash from the beginning embraces all mining communities. Many miners are successfully using older hardware such as Xeon processors to help secure the network. We use RandomX for CPU, ProgPow for GPU, and Cuckoo for ASIC. Longer term, our flexible architecture means we can have many algorithms, not just 3. Our roadmap includes an allocation for SHA3 Keccak, which will help further decentralize the network and keep it unstoppable. Yoga Dude We love miners 🙂 and Epic Cash can be mined with laptops and gaming rigs 🙂 Oleg✌🏻 A wide selection of mining methods is a great way to create a stable, decentralized and large network👌 Let’s talk about persons… 7. Who are the people developing Epic Cash? Yoga Dude We are blessed with a very talented team of skilled developers with diverse backgrounds, many of them are volunteers who believe in what Epic Cash stands for and contribute with product and usability innovation. Our teams main focus is to make Epic Cash the best, most secure, most user friendly and usable product on the market, without making it unnecessarily techie, with as much mainstream user appeal as possible. This is a serious challenge but we are up for it 😄 Max Freeman | Epic Cash | Mimblewimble It is also important to note that we are a truly open ecosystem that anyone can participate in. Our community has developed wallets, mining pools, educational content, and much else besides. We are not limited by the funding generated during an ICO or VC investment, our users are an essential element of our team. Oleg✌🏻 Sounds very attractive. 8. What do you think is currently lack in today’s crypto? Max Freeman | Epic Cash | Mimblewimble We believe there is not enough privacy, anonymity and fungibility, although there is a growing awareness in the community as to why these are necessary. People are waking up to the fact that privacy is a right for everyone but today it is being exploited and violated by corporations, governments and unscrupulous individuals. Privacy does not mean that you have something to hide. We have doors on our houses, curtains on our windows, we wear clothes, and we have security on our bank accounts and businesses, not because we are criminals. Fungibility (the property of not being able to distinguish one unit of currency from another) also has become a hot issue as people have started to get in trouble because of someone else’s misdeeds. Tainted money (coins that are blacklisted or restricted) is a problem for Bitcoin and Ethereum, the top two cryptos today. Mimblewimble eliminates the risk of tainted coins making them indistinguishable from each other. With traceable coins, you always have to worry if the coins you are getting were involved in a hack, or perhaps the darknet. Oleg✌🏻 It’s good to see strong and safe coin in our time Let’s talk about your future… 9. What does the Epic Cash roadmap look like going forward? Yoga Dude First and foremost, we are focused on security and usability. We are working on a new, improved GUI wallet to incorporate the community feedback on ways to improve it. We are in the process of completing final testing phases for the next iteration of Epic Cash which will make it more secure and stable. Once that is done, we will be rolling out Android and iOS support to make Epic Cash usable on leading smartphones and smartwatches. Beyond that without going into too much detail we are focused on continuous evolution of privacy, ease of mining, and overall speed and usability. And of course we are constantly looking to add more exchanges both with and without KYC. Oleg✌🏻 Are you working on Android and IOS wallet ? What will your application be? Max Freeman | Epic Cash | Mimblewimble Yes, we will release a mobile wallet this year. It will bring us one step closer to people being able to actually use cryptocurrency as money in daily life. Yoga Dude The idea is to be able to access Epic Cash from any platform and device Max Freeman | Epic Cash | Mimblewimble Epic is very lightweight, which means that low-end devices such as smartwatches can participate. Oleg✌🏻 Ok, got it. Thanks for clarification! 10. What else can you tell us about Epic Cash? Max Freeman | Epic Cash | Mimblewimble Well one thing I really want to mention is our great Epic Cash community. We’ve been building a decentralized community organically, without the talk of price pumps, pressure to HODL and other BS crypto-gimmicks. Our community is truly global and consists of developers, volunteers, miners, and other Epic enthusiasts spreading the word about Epic Cash, helping us reach millions of people around the world to improve their quality of life through social media and directly. Everyone is an evangelist, everyone is an influencer, everyone has the power to make the world a better place to live in. As we continue to grow — the future looks Epic 😊 Yoga Dude Definitely the community! We got a talented crowd of very cool and motivated people from all over the world! Oleg✌🏻 Thank you guys, for such informative answers 🙂 Now we proceed to Section 3, where a Community can ask their questions to the EPIC team Now I’ll open chat for the quite some time … Oleg✌🏻 Thank you all, dear community! EPIC team, please choose the 10 best questions you want to answer. AngeI Everyone likes Privacy & Epic Cash provides their Best Privacy to users But, Which Technologies are being used by Epic Cash to make Blockchain very Private and Completely untrackable ? Max Freeman | Epic Cash | Mimblewimble From the wallet to the node, Epic uses Dandelion++ to bounce transactions around the world before they go into the mempool for mining. Within the blockchain itself, Cut-Through merges all transactions in a block together, with CoinJoin automatically mixing all coins. Beyond that, there are no addresses, so it’s impossible to watch someone’s wallet. Arnold Even litecoin is implementing mimblewimble, Don’t you think it’s a significant threat for Epic if they implement it, then why would anyone use a less popular and a new cryptocurrency. Max Freeman | Epic Cash | Mimblewimble LTC is implementing mw as an “extension block”, meaning that it is optional and not all transactions will use it. This is very different than the core protocol leveraging mw to make all transactions private and all coins fungible. Aluta Why Epic cash so much focus on fungibility? Does fungibility matters that much? Max Freeman | Epic Cash | Mimblewimble Fungibility is going to be one of the key issues within the cryptocurrency space in the coming years. Today, if you accept traceable coins from a seller, you are liable if they have ever been used in any illegal activity. This has led to a two tier market where freshly minted coins sell for more than circulated coins. When coins are fungible, like Epic, you don’t have to worry that you will run into a problem when an exchange or merchant blocks your transaction. Joxes It is a pleasure. When I first researched EpicCash, google showed me a youtube video that talked about how to mine with EpicCash. It made me ask: is this mining activity profitable so far? We are in the early stages of development I guess, what adoption strategies are you taking to have sustained growth? is it feasible to reach N ° 500 rank in coinmarketcap in the medium term? Yoga Dude When I got into crypto, it was by mining Bitcoin back in 2011 when you could still solve blocks on a single computer, but Bitcoin at the time was anything but profitable 😄 Today Epic Cash is still new, still young, and still undervalued. I believe it is mining-worthy because of its potential, not because of today’s price. By allowing Epic Cash to be mined with GPU and CPU on gaming rigs, servers, and even laptops we offer maximum public participation in our project. More people involved in the project, the more evangelists there are. We empower people to mine Epic Cash and to promote it. S.P.A.D.E What new features of Epic Cash provide that Grin or Beam does not offer. Why do we need Epic Cash? Max Freeman | Epic Cash | Mimblewimble They are great coins, but there are some ways in which Epic improves. Epic has better tokenomics than Grin and a more sustainable model than Beam, that has a company behind it that needs to repay investors via its high dev tax. this article explains in more detail https://medium.com/@frodofreeman/overview-of-mimblewimble-cryptocurrencies-7c70be146f50 Sahil What’s the Minimum Hardware / setup Required for Mining of EPIC Cash coins? Is Mining Profitable and Can we Mine EPIC Cash coins at Home? Max Freeman | Epic Cash | Mimblewimble It is possible to mine on an ordinary laptop or desktop from the last 5 years, sometimes older. Epic is open to everyone, and our friendly community is standing by to help you get started at t.me/epicminers Erven James Sato “TOKEN BURN” is BENEFECIAL for any projects, in able to CONTROL THE NUMBER OF TOKEN CIRCULATION and TO PROVIDE GREATER INCENTIVES TO INVESTORS. Does your GREAT PROJECT have plan about TOKEN BURN? Xenolink For deflating projects It is beneficial to drive the demand / scarcity / and price up in a faster pace. Epic Cash is here for the organic long run not the short run. However when it comes to long term economics elastic supplies whether inflating or deflating will not be a solid long term economic model. This has been heavily discussed already with Bitcoins inelastic Fixed 21 million supply in the past. Having a fixed model demonstrates good long term economics without worrying about balancing a deflating/inflating model. Bitcoin is a perfect example of a 21 million inelastic fixed supply model that has been proving itself till today. Which is why we are also using the same fixed 21 million supply model. Epic Cash plans to have a solid organic long term future to bring free private fungible money and make this world a better place. Red Z🔥🤙 No one predicted the COVID-19 pandemic while developing their business model. But the crisis and recession of the global economy is our present with you and it affects all sectors, including blockchain. Will you make or have already made changes to the project roadmap, tokenomics? Do you have a plan in case the situation does not improve in the coming months and will affect the crypto industry even more? Yoga Dude One thing we have seen as the result of the COVID-19 is more governments are talking about moving to digital cash — digital dollar in USA, digital Lira in Turkey, etc… If in the past the idea of digital money was not graspable by some people, today its the governments that are educating the people for us about the value of digital currency… What is ironic, the governments, by printing money to solve the economic consequences of COVID-19 also educating the consumer about the true “value” of fiat… What we offer is a touch free, borderless, private, anonymous, fungible currency that can not be printed beyond the initial defined algo. We are more responsible than the printing presses of the governments 🤔 kunlefighter How does the Dandelion++ Protocol, Confidential Transactions (CT) and CoinJoin assist in protecting the privacy of individuals and their transactions on Epic Cash Blockchain? Max Freeman | Epic Cash | Mimblewimble Dandelion++ bounces transactions around before committing them to the blockchain, making it impossible to determine where they originated from. Confidential Transactions means that all tx are private, you can’t tell anything about where the coins have been or who they belonged to. CoinJoin in essence melts down and re-mints each coin every time it is used, making it impossible to track their ownership or usage history. Epic provides comprehensive privacy to everyone, without the compromises that other pre-mimblewimble coins have. Dr Mönica Hello sir @maxfreeman4@Johnsstec@Yogadude Thanks for the ama I notice that Epic Cash has 2 type of new algorithm, progPoW version 0.15.0 and randomX version 1.0.3 NOW , CAN you tell me why you choose these 2 algorithm??? Yoga Dude We went with RandomX because it is a solid and very popular CPU centric algo used by several coins — most recently Monero. Most miners today heavily favor ASICs or GPUs, leaving a lot of solid high end users in the dust unable to mine emerging cryptos. As far as ProgPow, again its an established algo for GPU miners, and thanks to many cryptos starting with Bitcoin/Monero/Ethe etc there is no shortage of GPU rigs out there :) plus again the casual user with a video gaming caliber card can get in on the action. Oleg✌🏻Perfect!It was a great AMA, but it is coming to an end, thanks to everyone who was with us. Thanks EPIC team for taking the time👏. I hope our projects will be able to collaborate even more closely in the future and achieve new successes. Cheers!🎉
The wallet will always say out of sync the first time you open it, as it has to download the blockchain. This process can take up to 4 hours or so depending on your internet speed and number of connections to our network, so please be patient. Bitcoin clients with the exception of SPV clients like Multibit need to download the entire blockchain history before consolidating the wallet. Currently the blockchain size is around 22 Gb and increasing. The time it takes for your client to sync will depend on your internet connection. Also if you do not keep your client connected, the next ... The first Parity Bitcoin sync attempt didn’t go well. After Parity fixed the consensus bug I tried again. Recompiled Parity Bitcoin with the SegWit bug fix. Full validation sync with 24GB dbcache and "verification edge" set to block 1 took 38 hours, 17 minutes, was disk I/O bound most of the time. — Jameson Lopp (@lopp) November 12, 2018 Bitcoin wallet can synchronize all your useful data on your system through network. The wallet will always say out of sync the first time you open it, as it has to download the blockchain. The whole process can take up to few hours or so depending on your internet speed and number of connections to our network, and the size of data. One of the most common issue users of core wallet face is “Wallet Out of Sync”. Either the wallet synchronization process will be slower or it gets stuck at certain block and it won’t sync at all. So why your wallet won’t sync or is slow and what to do if it is not syncing / processing the blockchain? Wallet synchronization. Bitcoin, Dash, Litecoin and every Altcoins has its own core ...
How to fix Sync Problem With Bitradio.io Pc wallet
Find out why Close. Bitcoin out of sync with fundamentals? / Bubble burst is approaching? CryptoPortfolio ... Understanding Shoulder Pain and How To Fix It - Duration: 13:48. Precision Wellbeing ... mooncoin wallet sync fix Donate Bitcoins on this addres 1He4sTpbxT4AgbtuwRu7JbHirG8zWLWU4G. How to Recover Missing Bitcoins / Not Showing Up While Wallet Syncing - Duration: 7 ... Quick Fix Bitconnect QT Wallet Out of Sync 🖥️ Mac OSX - Duration: 5:30. Nad Daniels 2,325 views. 5:30 ... How to Secure & Backup Your Bitcoin or Other Crypto Wallets - Duration: 11 ... PRO Wallet Out Of Sync - Another Solution To Fix - Duration: 9:31. Cryptocurrency Group 4,759 views. 9:31. Bitrad.io ... Quick Fix Bitconnect QT Wallet Out of Sync 🖥️ Mac OSX - Duration: 5:30. Nad Daniels 2,327 views. 5:30. Fixing The PRO Wallet Out Of Sync Message - Duration: 24:09. Cryptocurrency Group ...