What I currently use for privacy (after almost 2 years of long investing into it)
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.
The next XVG? Microcap 100x potential actually supported by fundamentals!
What’s up team? I have a hot one for you. XVG returned 12 million percent in 2017 and this one reminds me a lot of it. Here’s why: Mimblewimble is like Blu-Ray compared to CD-ROM in terms of its ability to compress data on a blockchain. The current BTC chain is 277gb and its capacity is limited because every time you spend a coin, each node needs to validate its history back to when it was mined (this is how double spending is prevented). Mimblewimble is different - all transactions in a block are aggregated and netted out in one giant CoinJoin, and only the current spending needs to be verified. This means that dramatically more transactions can fit into a smaller space, increasing throughput and lowering fees while still retaining the full proof of work game theory of Bitcoin. These blockchains are small enough to run a full node on a cheap smartphone, which enhances the decentralization and censorship resistance of the network. The biggest benefit, though, is that all transactions are private - the blockchain doesn’t reveal amounts or addresses except to the actual wallet owner. Unlike earlier decoy-based approaches that bloat the chain and can still be data mined (XMR), Mimblewimble leaves no trace in the blockchain, instead storing only the present state of coin ownership. The first two Mimblewimble coins, Grin and Beam, launched to great fanfare in 2019, quickly reaching over $100m in market cap (since settled down to $22m and $26m respectively). They are good projects but grin has infinite supply and huge never-decreasing emission, and Beam is a corporate moneygrab whose founding investors are counting on you buying for their ROI. ZEC is valued at $568m today, despite the facts that only 1% of transactions are actually shielded, it has a trusted setup, and generating a confidential transaction takes ~60 seconds on a powerful PC. XMR is a great project but it’s valued at $1.2b (so no 100x) and it uses CryptoNote, which is 2014 tech that relies on a decoy-based approach that could be vulnerable to more powerful computers in the future. Mimblewimble is just a better way to approach privacy because there is simply no data recorded in the blockchain for companies to surveil. Privacy is not just for darknet markets, porn, money launderers and terrorists. In many countries it’s dangerous to be wealthy, and there are all kinds of problems with having your spending data be out there publicly and permanently for all to see. Namely, companies like Amazon are patenting approaches to identify people with their crypto addresses, “for law enforcement” but also so that, just like credit cards, your spending data can be used to target ads. (A) Coinbase is selling user data to the DEA, IRS, FBI, Secret Service, and who knows who else? (B) What about insurance companies raising your premiums or canceling your policy because they see you buying (legal) cannabis? If your business operates using transparent cryptocurrency, competitors can data mine your customer and supply chain data, and employees can see how much everyone else gets paid. I could go on, but the idea of “I have nothing to hide, so what do I care about privacy?” will increasingly ring hollow as people realize that this money printing will have to be paid by massive tax increases AND that those taxes will be directly debited from their “Central Bank Digital Currency” wallets. 100% privacy for all transactions also eliminates one HUGE problem that people aren’t aware of yet, but they will be: fungibility. Fungibility means that each coin is indistinguishable from any other, just like paper cash. Why is this important? Because of the ever-expanding reach of AML/KYC/KYT (Anti-Money Laundering / Know Your Customer / Know Your Transaction) as regulators cramp down on crypto and banks take over, increasingly coins become “tainted” in various ways. For example, if you withdraw coins to a mixing service like Wasabi or Samourai, you may find your account blocked. (C) The next obvious step is that if you receive coins that these chainalysis services don’t like for whatever reason, you will be completely innocent yet forced to prove that you didn’t know that the coins you bought were up to no good in a past life. 3 days ago, $100k of USDC was frozen. (D) Even smaller coins like LTC now have this problem, because “Chinese Drug Kingpins” used them. (E) I believe that censorable money that can be blocked/frozen isn’t really “your money”. Epic Cash is a 100% volunteer community project (like XVG and XMR) that had a fair launch in September last year with no ICO and no premine. There are very few projects like this, and it’s a key ingredient in Verge’s success (still at $110m market cap today despite being down 97% since the bubble peak) and why it’s still around. It has a small but super passionate community of “Freemen” who are united by a belief in the sound money economics of Bitcoin Standard emission (21m supply limit and ever-decreasing inflation) and the importance of privacy. I am super bullish on this coin for the following reasons:
Only $400k market cap
Supply started at zero, so there are no VC’s and team to dump on you into the pumps - all coins are mined into existence, just like Bitcoin.
It just had its first halving, reducing emission from 16 to 8 per block. Between now and 2028 there are FOUR (!) more halvings, from 4 to 2 to 1 and then finally 0.15 (I guess that would be an 85%-ing :p) and at this point the supply is the same as BTC and stays in sync forever until the last coin is mined in 2140. This simple supply curve is already accepted by the market as a winner, so why mess with success? (I)
Meets Andreas Antonopolous’ 5 pillars of open blockchains test: Public, Open, Borderless, Neutral, and Censorship Resistant. (How many coins can say this?)
Unlike Bitcoin, Epic created a multi-algorithm approach that enables people to mine on ordinary computers - 60% for CPU on RandomX, 38% for GPU on ProgPow, and 2% for ASIC’s on Cuckoo31+. The algorithms don’t compete with one another. This is essential for leveling the playing field and preventing massive farms from dominating. These percentages can change over time and new algorithms can be easily dropped in. You can mine today using an old laptop and in 5 years you will still be able to. Incidentally, there is nothing standing in the way of adding mobile phone-based mining, which ETN showed there’s a huge demand for.
Based off the excellent Grin codebase, which means they continue to pull in ongoing core code enhancements and focus on ease of use and market penetration instead. (Smart!)
Litecoin’s Charlie Lee is out there daily talking about their move to Mimblewimble, which provides free publicity. What people don’t realize is that you can’t just bolt on Mimblewimble to a legacy blockchain, that’s like putting a Ferrari engine into a school bus - it’s still a school bus, not a race car! LTC is doing it as an optional soft fork via “extension blocks” which will not be supported by all wallets and exchanges. Also, anyone using “optional” privacy features is declaring themselves to be suspicious, which kind of defeats the point for people who care about privacy.
The community is friendly and welcoming to new people coming in, with lots of helpful (independently created) tutorials and guides. (F)
It’s already a global phenomenon, with the whitepaper in 20+ languages (G) and (not bot-infested) active local-language communities on not only Telegram but also Wechat, LINE, QQ and other messenger platforms.
It’s only on two random little exchanges currently, Citex and Vitex. Vitex is actually a pretty good DEX with no KYC and a great mobile wallet.
They are very creative - since centralized exchanges want huge money to list, they created a non-inflationary ERC20 tracker token that’s exchangeable 1:1 for coins so that Uniswap trading is possible (H)
Because it doesn’t have a huge marketing budget in a sea of VC-funded shitcoins, it is as-yet undiscovered, which is why it’s so cheap. There are only 4 Mimblewimble-based currencies on the market: MWC at $162m, BEAM at $26m, GRIN at $22m, and EPIC at $0.4m. This is not financial advice and as always, do your own research, but I’ve been buying this gem for months and will continue to. This one ticks all the boxes for me, the only real problem is that it’s hard to buy much without causing a huge green candle. Alt season is coming, and coins like this are how your neighbor Chad got his Lambo back in 2017. For 2021, McLaren is a better choice and be sure to pay cash so that it doesn’t get repossessed like Chad!
Ready to CashShuffle and CashFusion Your Coins On-The-Go?
As many of you may already know, i’ve been working these past few months on a web-wallet called Nito Cash. The motivation is for greater Bitcoin adoption, by providing the simplest starting point for users to experience cryptocurrency. Notably, there are no seed phrases required to get started and you can easily sync across devices with the use of qr codes. Perhaps overly ambition, Nito (as in Incognito) is meant to encourage use of the Bitcoin privacy protocols CashShuffle and CashFusion. 5 months later, I’m still working things out due to the challenges of bringing CashFusion to the web browser. However, I’m happy to say that CashShuffle is now available at https://app.nitojs.org.
NitoJS is an upcoming Bitcoin Cash Library and Software Development Kit (SDK) for helping developers bring their “unstoppable” dreams to reality. NitoJS will be a mobile-first library with compatibility on the server. The goal is to smooth out a path for developers to create fully decentralized (unstoppable) web-apps by leveraging the combination of the Bitcoin Cash blockchain and IPFS.
Won’t oversell anything as this is just a teaser, but I’ve been LIVE testing a CashFusion solution for the last few weeks and I’m expecting to have a public demo soonish'. Initially, I’ll offer a hosted solution, as that’s nearly complete (backend already done, frontend being worked on), followed by a self-hosted solution that you can run from your own pc. Both will enable the ability to CashShuffle and CashFusion your coins from ANY desktop or mobile web browsers (meaning it’s compatible with ANY and ALL wallets). You can CashShuffle your coins on https://app.nitojs.org today. It’s buggy! You may have to reload a bit and there’s a RE-SYNC button on the settings page that you may have to use after depositing. Also, "RE-BUILD MY PURSE" WILL DELETE YOUR PRIVATE KEYS, so make sure your wallet is empty first. Otherwise, it’s all good! Once I’ve cleaned up the code and UI a bit, I’ll make formal announcement on read.cash. Cheers! 🍾🤣
TL;DR: Wrote blockchain.com support on an issue, got a fraudulent email from blockchainexchange.vip asking for my 12 word seed. Today I was trying to send some bitcoin out of my blockchain app, and I got a notice saying I had too many unspent transactions, so the fee was going to be higher. I read that moving all funds to a new wallet will solve this, but when I attempted to do so, only half of my balance was available to be spent, which is very strange, since I have no pending transactions. So I went to blockchain.com support site, and wrote an email asking for a solution. I got an email a couple hours later from [[email protected]](mailto:[email protected]), but when I looked closer, it was actually [[email protected]](mailto:[email protected]) . That raised some suspicions. When looking at the support ticket, it was a completely different number. What came after is even worse. David from support goes on to write that I the wallet out of sync with their database, causing balances not to show correctly. He goes on to instruct me to backup my wallet, and asks me to send the 12 word seed, and once I did that, my wallet would be synchronized again. What I don't understand is how this is possible? I was on their site, looked for answers on Wallet consolidation, and clicked on submit a request. And I still dont have an answer on why my spendable value is less than half of my wallet value
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 wish I didn't do this mistake but I did, and even though nobody will blame anyone but me... (I know I do for the most part, but I also partly blame Google) You see I've been using tronlink in chrome for about a year now and I made around $130 from 20 dollars worth of bitcoin I got from coinbase earn program. AND I LOVE IT! The only thing is the mnemonic keys that I struggle with, I used to store them on a USB, this wallet was no exception, recently I lost this USB due to becoming homeless for awhile and as stupid as I am I carried the USB in my jeans during a rainy winter. (My grandmother, mom and dad all offered me a place to stay so no worries guys) still had my old PC drive at my dad's house from selling it when I was tryna make some bank so I installed it a couple days ago and got back to grinding TRX, bought some BNKR daily+ and so on.. Anyways my girl was using my computer today for finding a part time since we both lost our jobs this year... and signed in on her Gmail which made her gmail the standard gmail for the CHROME PROFILE(Note this!! Its the little circle next to the extensions in the chrome browser) So I googled how to change this, I thought I would backup my private key once I was done, should've done it days ago but didn't think of it until today when she was messing around in my browser (Yes I got really nervous since she isn't very computer friendly 😂) So I stumbled on Google's support tickets and a top answer told me to just delete the chrome profile and setup a new one since history and bookmarks would come back once I signed in... (They didn't btw, you need sync activated for that, however when you remove the profile it doesn't say that, it just says that you can log on again and it comes back) But here's where the warning comes in: IT ALSO REMOVES ALL EXTENSIONS! and it says itself that if you dont have your key you won't be getting your wallet back. Some steps you can take to avoid this situation:
Saving your key somewhere you can access it remotely, like in an email to yourself or in a private document on the cloud.
If you're on windows backup the chrome "Users" folder in the appdata directory (a quick Google search will show you how)
Turn on autobackup on your PC so you can revert the users folder if necessary.
Write your key on a piece of paper and store it somewhere it won't move or be damaged, like a safe or with your mom like I did (she studied to be a lawyer so she's amazing with documents)
Store your trx on binance so you can login using email and recover password if you lose your wallet.
Thanks for reading guys, if you wanna make my day you can donate anything to: TPYLfp4Xv38Ji61uS2Cg9bV8p9fj1Wb1j8 TL;DR If you remove your chrome profile on chrome and dont have a backup of anything you will lose your wallet! Your chrome profile is the circle next to the extensions in the chrome browser. (To be extra clear: its to the left of the three dots in the top right corner where you go to settings, history and stuff like that) Thank you all for letting me be a part of this community and I promise I have 3 backups and stored my key in like 5 places so this won't happen again. I even made a backup of this post if I would accidentally close it 😂 Much love, peace! ❤ Edit: so I found the mnemonic phrases! Turns out I had them on my second drive aswell, but all it shows is 5 empty wallets, I've only had 3 wallets and I have 3 mnemonic phrases... what. The. ⁉️⁉️
How To Withdraw LBC Coin On Lbry.Tv & Exchange To Native Currency
We have already posted about the introduction of the LBRY blockchain and the concept of this decentralized content freedom platform. We have also discussed early joining earning opportunities for you and you can grab as an early user of this platform. If you don’t yet familiar with this evolving project in the blockchain world then it’s suggestive from us that read our previously posted articles on those topics which are the followup of this post to learn, In this quick instructing post. About How to withdraw or send, transfer your lbry coins if you have earned or receive through their reward program how you can convert them to your native currency and enjoy to spend them easily. Join LBRY.tv and Earn LBC Coins Nav Posted Content
📷 As you know that lbry.tv has provided you a blockchain synced wallet where you receive your earnings and you send as well as transfer your funds in terms of LBC coins using LBRY blockchain. You can backup your wallet and also can restore your wallet independently which help you to secure your funds you want to again access your wallet funds you can access the platform and log in there through your email if your wallet is already synced with lbry server then you can see and access your funds directly if syncing is off then you need to restore wallet shortly.
You can backup your wallet by just accessing your lbry.tv platform on either desktop application or through an android or IOS platform to turn to sync on or off based on your choices. The requirement of backup up your wallet on the desktop by just going to help section and scroll down then click on create backup option and then you will have saved your zip file of backup you can use it for your fund’s security and other restoration processes. 📷 If you want to use their same lbry account different platforms then you can sync option for your own convenience.
LBRY Wallets Other Than LBRY App
So it is just easy that you can store your earnings so far until you need to convert them into the local currency you can store and safe them into lbry simply app and access them simply from desktop to Android and other supportive platforms also perhaps if you want to store more separately or want an alternative to lbry apps simple wallet then the options are available you can use the following wallets other then lbry apps.
If you want further detailed information regarding these wallets that how to use them and how you can transact in them you can ask us or suggest us to post guide blog on a thing so that we can consider it on your request.
How to Withdraw Your LBC LBRY Credits Coins From lbry.tv?
The coins you earned on lbry.tv which are actually LBC lbry credits which is a coin and native currency value of lbry platform and blockchain to transfer value and for other use cases. The lbry.tv platform offer you complete freedom of choice and doesn’t hold your funds in their wallet or servers the coins credits you can transfer directly and instantly to the wallet and you can transfer it immediately to any address of supportive LBC exchange or any other LBC blockchain wallet address. So, therefore, there is no option of withdrawing because there is no minimum or selective day of withdrawing requirement compare to other centralized platforms. So furthermore now we need to consider how we can spend these earned coins because we cannot directly pay them to anyone and can exchange it with services and goods of value that’s why we need to exchange LBC to USD or your own region native fiat currency.
How to Exchange/Convert LBC to USD or Fiat Currency?
The standard process of exchanging any currency to your native currency in the cryptocurrency market is to exchange any crypto to USD through supportive legitimate reputable well-known volume holding Cryptocurrencies either they are centralized or decentralize DEXs.
Current LBC Reputable Markets
We recommend You consider Bittrex in first Priority and if you are in a region where Bittrex unsupported their services or ban by country jurisdiction then you can consider CoinEx Exchange to exchange into USDT and Then You can Convert them into a local currency where via crypto to local fiat channels. In this article, we are also looking forward to the way to exchange LBC to USD or any other crypto through CoinEX exchange so let’s read below continue. Current Value Of LBC Against USD LBRY Credits (LBC) 0.023857 USD (-6.49%)📷RANK 390MARKET CAP $10.40 M USD VOLUME $704.74 K USDPowered by CoinMarketCap You have two pairs of support on CoinEx exchange with LBC/BTC and LBC/USDT you can further convert it into Ethereum or any other crypto which you feel comfortable getting into fiat easily where local exchangers support is available.
Follow The Following Steps To Exchange Your LBC to USD or BTC at CoinEx
After Successfully Logging in to your CoinEx Account.
Goto Upper right NAV bar to Assets Option Click and Open it.
Find the LBC Under in the Spot Account Search Box LBC Asset wallet Will Appear Shortly.
Click on the Deposit Option and Copy the LBC Receiving Address.
Then Goto to Your LBRY.tv Account LBC Balance click on it and Click Send Option On the Page.
Past the Address thoroughly and enter the desired balance then click send.
After 20 Network Confirmations, you will receive your coins in the CoinEx Account.
You can Exchange it to USDT or BTC By just Clicking on Markets Option from Nav Bar.
You will be redirected to trading markets available instruments on the exchange.
You can Select now BTC Pairs or USD Markets Depending on Your Choices.
You can either search LBC or find it manually by scrolling your self.
Let’s say you want to exchange LBC/USDT By selecting the USD Markets.
The LBC/USDT trading panel will appear to select the amount you want to exchange or sell.
Enter Amount of balance you want to exchange and Hit Sell Option Currently Min 50 LBC/USD is Allowed.
Now you can withdraw Your USDT or Convert it accordingly to any other crypto to get converting convenience. You can Convert your BTC, ETH, and Other Top coins to PERFECT MONEY SKRILL NETELLER and other fiat channels in Asia and Other regions or get Fiat Withdraw To Your local wallets through following local trusted exchangers.
Many other sites are available but above three are recommended and also done used by personal experiences are much positive regarding (LOCAL BITCOINS, BESTCHANGE) So you can free to use these mediums fees are higher than usual and minimum criteria are also very much tightened because crypto to fiat and fiat to crypto is difficult so far due to Govt. Regulations and centralize control other than that the real-world problem-solving idea come and solve this fees consuming and time hurdle problem solve by some great developers and GOVT could flexible the control on MONEY which so far seems like Very difficult what you think to tell us BELOW. If you have Skrill or Neteller Verified Account or Want to Create Your account then you can convert BTC, BCH, and Ethereum Directly Through BitPay support inside Skrill and cash out to your native wallet. If you have any questions regarding LBRY.tv LBC coin or regarding any the blockchain of lbry or having any issue regarding the exchanging platform channel transfer issue or want the easy way of exchanging LBC to your native fiat currency easily then you can comment below we can assist you as much we can We highly appreciate your time to spend on curexmy.com hope this will valuable for you.
RChain’s mission is to create a blockchain that can support global coordination for solving global problems including climate change. Seattle, WA. May 11, 2020 – RChain Cooperative launched its mainnet blockchain on February 25, 2020. Since then, our community has developed wallets and the impressive Dappy Framework has been released. Additionally, RChain REV has been listed on MXC and HotBit exchanges. This ground swell of engagement and support comes from the fact that the RChain community understands that as RChain matures it will be able to scale in a near linear fashion, so that instead of slowing down as more resources are added, it will scale up. Over the next few months RChain will support the ability for nodes to join, not by going all the way back to the genesis block, but by going only to the last finalized state. This will enable nodes to sync up to the blockchain quickly, and continually compact the storage they maintain. But to really get inside what makes the RChain technology different it is important to understand that it is built as a next generation database, first and foremost. Rholang offers many advanced language features, yet it is at the end of the day a query language for a decentralized, global storage and compute platform. To learn more, check out this video, (What sets RChain apart from Ethereum...). Technology is not the only thing that sets RChain apart. The RChain Cooperative is also a community of people who understand the gravity of the situation we face in climate change and understand that we cannot wait for government or industry. We must find a way to coordinate our response to climate change now. The RChain technology provides the basis for that coordination and response. To learn more, check out our Climate and Coordination podcasts. RChain is led by Greg Meredith, one of the foremost visionaries in the blockchain space. Behind his leadership, and years of building and developing in the “decentralized” platform world, RChain is creating a platform that will transform blockchain technology and empower its users. “Greg Meredith is a logician and mathematician with an astounding grasp of concurrency, formal verification, language design, and computer science. His knowledge is not compartmentalized, but rather reflects his holistic understanding of the fundamentals of theoretical computer science,” said Vlad Zamfir, founding member of Ethereum. Current blockchains (e.g. Bitcoin and Ethereum) are struggling with scale, speed and security as well as being limited and only capable of processing approximately 10-20 transactions per second. RChain anticipates managing approximately 40,000 transactions per second (matching Visa’s processing capabilities). The RChain platform’s smart contracts and the transactions represented therein are concurrent and formally verified by a compiler – so they’re fast, versatile, and secure all the while being easy for developers to adopt and utilize. At present, no other blockchain technology addresses these fundamental needs of the community. Co-founder Greg Meredith said, “Because the RChain platform enables more trust on the Internet, it’s evolutionary.” He went on to say, “It enables innovators worldwide to create fast, scalable and decentralized solutions that are far less resource intensive, which is a significant improvement from existing blockchain solutions”. Among the many possible applications of RChain’s technology; tamper-proof financial platforms, social networks, environmental agencies, and endless other options. These are solutions that enable every individual to finally control their own identity, reputation and data. For more information go to https://rchain.coop. About RChain CooperativeThe Co-op is owned and controlled by its members, each member receives one vote, regardless of how many tokens are owned. The membership fee is purposefully affordable ($20) to allow people from all over the world to drive the vision of the Co-op. The Co-op owns and is responsible for the development and maintenance of the RChain platform.
Hey shibes, I see a lot of posts about mining lately and questions about the core wallet and how to mine with it, so here are some facts! Feel free to add information to that thread or correct me if I did any mistake.
You downloaded the core wallet
Great! After a decade it probably synced and now you are wondering how to get coins? Bad news: You don't get coins by running your wallet, even running it as a full node. Check what a full node is here. Maybe you thought so, because you saw a very old screenshot of a wallet, like this (Version 1.2). This version had a "Dig" tab where you can enter your mining configuration. The current version doesn't have this anymore, probably because it doesn't make sense anymore.
You downloaded a GPU/CPU miner
Nice! You did it, even your antivirus system probably went postal and you started covering all your webcams... But here is the bad news again: Since people are using ASIC miners, you just can't compete with your CPU hardware anymore. Even with your more advanced GPU you will have a hard time. The hashrate is too high for a desktop PC to compete with them. The blocks should be mined every 1 minute (or so) and that's causing the difficulty to go up - and we are out... So definitly check what is your hashrate while you are mining, you would need about 1.5 MH/s to make 1 Doge in 24 hours!
Let us start with a quote:
"Dogecoin Core 1.8 introduces AuxPoW from block 371,337. AuxPoW is a technology which enables miners to submit work done while mining other coins, as work on the Dogecoin block chain." - langerhans
What does this mean? You could waste your hashrate only on the Dogecoin chain, probably find never a block, but when, you only receive about 10.000 Dogecoins, currently worth about $25. Or you could apply your hashrate to LTC and Doge (and probably even more) at the same time. Your change of solving the block (finding the nonce) is your hashrate divided by the hashrat in sum - and this is about the same for Doge and LTC. This means you will always want to submit your work to all chains available!
Mining solo versus pool
So let's face it - mining solo won't get you anywhere, so let's mine on a pool! If you have a really bad Hashrate, please consider that: Often you need about $1 or $2 worth of crypto to receive a payout (without fees). This means, you have to get there. With 100 MH/s on prohashing, it takes about 6 days, running 24/7 to get to that threshold. Now you can do the math... 1 MH/s = 1000 KH/s, if you are below 1 MH/s, you probably won't have fun.
Buying an ASIC
You found an old BTC USB-miner with 24 GH/s (1 GH/s = 1000 MH/s) for $80 bucks - next stop lambo!? Sorry, bad news again, this hashrate is for SHA-256! If you want to mine LTC/Doge you will need a miner using scrypt with quite lower numbers on the hashrate per second, so don't fall for that. Often when you have a big miner (= also loud), you get more Hashrate per $ spent on the miner, but most will still run on a operational loss, because the electricity is too expensive and the miners will be outdated soon again. Leading me to my next point...
You won't make money running your miner. Just do the math: What if you would have bougth a miner 1 year ago? Substract costs for electricity and then compare to: What if you just have bought coins. In most cases you would have a greater profit by just buying coins, maybe even with a "stable" coin like Doges.
Okay, this was a lot of text and you are still on the hook? Maybe you are desperated enough to invest in some cloud mining contract... But this isn't a good idea either, because most of such contracts are scams based on a ponzi scheme. You often can spot them easy, because they guarantee way to high profits, or they fake payouts that never happened, etc. Just a thought: If someone in a subway says to you: Give me $1 and lets meet in one year, right here and I give you $54,211,841, you wouldn't trust him and if some mining contract says they will give you 5% a day it is basically the same. Also rember the merged mining part. Nobody would offer you to mine Doges, they would offer you to buy a hashrate for scrypt that will apply on multiple chains.
Maybe try to mine a coin where you don't have ASICs yet, like Monero and exchange them to Doge. If somebody already tried this - feel free to add your thoughts!
Folding at Home (Doge)
Some people say folding at home (FAH - https://www.dogecoinfah.com/) still the best. I just installed the tool and it says I would make 69.852 points a day, running on medium power what equates to 8 Doges. It is easy, it was fun, but it isn't much. Thanks for reading _nformant
Let’s start with the most important thing — the blockchain works on the principles of P2P networks, when there is no central server and each device is both a server and a client, such an organization allows you to maintain the network performance with any number and any combination of available nodes. For example, there are 12 machines in the network, and anyone can contact anyone. As a client (resource consumer), each of these machines can send requests for the provision of some resources to other machines within this network and receive them. As a server, each machine must process requests from other machines in the network, send what was requested, and perform some auxiliary and administrative functions. With traditional client-server systems, we can get a completely disabled social network, messenger, or another service, given that we rely on a centralized infrastructure — we have a very specific number of points of failure. If the main data center is damaged due to an earthquake or any other event, access to information will be slowed down or completely disabled. With a P2P solution, the failure of one network member does not affect the network operation in any way. P2P networks can easily switch to offline mode when the channel is broken — in which it will exist completely independently and without any interaction. Instead of storing information in a single central point, as traditional recording methods do, multiple copies of the same data are stored in different locations and on different devices on the network, such as computers or mobile devices. https://i.redd.it/2c4sv7rnrtx41.gif This means that even if one storage point is damaged or lost, multiple copies remain secure in other locations. Similarly, if one part of the information is changed without the consent of the rightful owners, there are many other copies where the information is correct, which makes the false record invalid. The information recorded in the blockchain can take any form, whether it is a transfer of money, ownership, transaction, someone’s identity, an agreement between two parties, or even how much electricity a light bulb used. However, this requires confirmation from multiple devices, such as nodes in the network. Once an agreement, otherwise known as consensus, is reached between these devices to store something on the blockchain — it can’t be challenged, deleted, or changed. The technology also allows you to perform a truly huge amount of computing in a relatively short time, which even on supercomputers would require, depending on the complexity of the task, many years or even centuries of work. This performance is achieved because a certain global task is divided into a large number of blocks, which are simultaneously performed by hundreds of thousands of devices participating in the project.
P2P messaging and syncing in TkeySpace
TkeySpace is a node of the TKEY network and other supported networks. when you launch the app, your mobile node connects to an extensive network of supported blockchains, syncs with full nodes to validate transactions and incoming information between nodes, so the nodes organize a graph of connections between them.
You can always check the node information in the TkeySpace app in the ⚙Settings—Contact and peer info—App Status;
https://preview.redd.it/co1k25kqrtx41.png?width=619&format=png&auto=webp&s=e443a436b11d797b475b00a467cd9609cac66b83 TkeySpace creates initiating connections to servers registered in the blockchain Protocol as the main ones, from these servers it gets the addresses of nodes to which it can join, in turn, the nodes to which the connection occurred share information about other nodes. https://i.redd.it/m21pw88srtx41.gif TkeySpace sends network messages to nodes from supported blockchains in the app to get up-to-date data from the network. The Protocol uses data structures for communication between nodes, such as block propagation over the network, so before network messages are read, nodes check the “magic number”, check the first bytes, and determine the type of data structure. In the blockchain, the “magic number” is the network ID used to filter messages and block traffic from other p2p networks.
Magic numbersare used in computer science, both for files and protocols. They identify the type of file/data structure. A program that receives such a file/data structure can check the magic number and immediately find out the intended type of this file/data structure.
After exchanging messages, the block information is loaded and transactions are uploaded to your node. To avoid storing tons of information and optimize hard disk space and data processing speed, we use RDBMS — PostgreSQL in full nodes (local computer wallet). In the TkeySpace mobile app, we use SQLite, and validation takes place by uploading block headers through the Merkle Tree, using the bloom filter — this allows you to optimize the storage of your mobile device as much as possible. The block header includes its hash, the hash of the previous block, transaction hashes, and additional service information. Block headers in the Tkeycoin network=84 bytes due to the extension of parameters to support nChains, which will soon be launched in “combat” mode. The titles of the Bitcoin block, Dash, Litecoin=80 bytes. https://preview.redd.it/uvv3qz7wrtx41.png?width=1230&format=png&auto=webp&s=5cf0cd8b6d099268f3d941aac322af05e781193c And so, let’s continue — application nodes receive information from the blockchain by uploading block headers, all data is synchronized using the Merkle Tree, or rather your node receives and validates information from the Merkle root.
The hash tree was developed in 1979 by Ralph Merkle and named in his honor. The structure of the system has received this name also because it resembles a tree.
The Merkle tree is a complete binary tree with leaf vertexes containing hashes from data blocks, and inner vertexes containing hashes from adding values in child vertexes. The root node of the tree contains a hash from the entire data set, meaning the hash tree is a unidirectional hash function. The Merkle tree is used for the efficient storage of transactions in the cryptocurrency blockchain. It allows you to get a “fingerprint” of all transactions in the block, as well as effectively verify transactions. https://preview.redd.it/3hmbthpxrtx41.png?width=677&format=png&auto=webp&s=cca3d54c585747e0431c6c4de6eec7ff7e3b2f4d Hash trees have an advantage over hash chains or hash functions. When using hash trees, it is much less expensive to prove that a certain block of data belongs to a set. Since different blocks are often independent data, such as transactions or parts of files, we are interested in being able to check only one block without recalculating the hashes for the other nodes in the tree. https://i.redd.it/f7o3dh7zrtx41.gif The Merkle Tree scheme allows you to check whether the hash value of a particular transaction is included in Merkle Root, without having all the other transactions in the block. So by having the transaction, block header, and Merkle Branch for that transaction requested from the full node, the digital wallet can make sure that the transaction was confirmed in a specific block. https://i.redd.it/88sz13w0stx41.gif The Merkle tree, which is used to prove that a transaction is included in a block, is also very well scaled. Because each new “layer” added to the tree doubles the total number of “leaves” it can represent. You don’t need a deep tree to compactly prove transaction inclusion, even among blocks with millions of transactions.
Statistical constants and nChains
To support the Tkeycoin cryptocurrency, the TkeySpace application uses additional statistical constants to prevent serialization of Merkle tree hashes, which provides an additional layer of security. Also, for Tkeycoin, support for multi-chains (nChains) is already included in the TkeySpace app, which will allow you to use the app in the future with most of the features of the TKEY Protocol, including instant transactions.
The multi-currency wallet TkeySpace is based on HD (or hierarchical determinism), a privacy-oriented method for generating and managing addresses. Each wallet address is generated from an xPub wallet (or extended public key). The app is completely anonymous — and individual address is generated for each transaction to accept a particular cryptocurrency. Even for low-level programming, using the same address is negative for the system, not to mention your privacy. We recommend that you always use a new address for transactions to ensure the necessary level of privacy and security. The EXT_PUBLIC_KEY and EXT_SECRET_KEY values for DASH, Bitcoin, and Litecoin are completely identical. Tkeycoin uses its values, as well as other methods for storing transactions and blocks (RDBMS), and of course — nChains.
A private key is a special combination of characters that provides access to cryptocurrencies stored on the account. Only a person who knows the key can move and spend digital assets.
TkeySpace — stores the encrypted key only on the user’s device and in encrypted form. The encrypted key is displayed as a mnemonic phrase (backup phrase), which is very convenient for users. Unlike complex cryptographic ciphers, the phrase is easy to save or write. A backup keyword provides the maximum level of security.
A mnemonic phrase is 12 or 24 words that are generated using random number entropy. If a phrase consists of 12 words, then the number of possible combinations is 204⁸¹² or 21¹³² — the phrase will have 132 security bits. To restore the wallet, you must enter the mnemonic phrase in strict order, as it was presented after generation.
Now we understand that your application TkeySpace is a node of the blockchain that communicates with other nodes using p2p messages, stores block headers and validate information using the Merkle Tree, verifies transactions, filters information using the bloom filter, and operates completely in a decentralized model. The application code contains all the necessary blockchain settings for communicating with the network, the so-called chain parameters. TkeySpace is a new generation mobile app. A completely new level of security, easy user-friendly interfaces and all the necessary features that are required to work with cryptocurrency.
Using the Internet to Donate to Andrew Yang - Cryptocurrency, BAT, and the Brave Browser
Set up tipping to give earned BAT to content creators on Reddit, YouTube, or Twitter. (Another great mission of Brave/BAT.)
Convert to another currency and spend/withdraw.
Donate to Andrew Yang!
Here's how to earn BAT using Brave to support Andrew:
Download Brave browser. Note: There is a referral program for browser downloads. By using a referral link, the referrer will earn $7.50 after ~30 days of use by the downloader. I know that many of us here will happily pass this along to to Yang campaign! ☺️ Work together to utilize this benefit. In order to generate a referral link, you must sign up to be a Brave creator at https://creators.brave.com/. As Reddit users, all of you are capable of signing up to be a creator!
Set up your account at Uphold. You must verify your identity using a driver's license, passport, etc. There are regulations in the US related to knowing your client that Uphold must follow. Initiate this process by clicking the Brave Rewards button > "Verify Wallet" to the right of the address bar. (It's an orange/pink/purple triangle.) This should bring you to uphold.com where they will guide you through creating an account.
After your account is verified on Uphold, ensure that your Brave wallet is synced with Uphold. The "Verify Wallet" text should update to say "Wallet Verified". Your earned BAT will now sync to Uphold.
Once you have BAT in your Uphold wallet, there are a couple of options to get this money to Andrew:
Withdraw to your bank account. You will then use the standard method for donating to Andrew Yang at yang2020.com/donate. Note that there will be a bit of a delay between withdrawal and funds arriving in your account. Uphold also has a 1.95% withdrawal fee.
Waltonchain adds GNU General Public License details to code - BUT does the code contain this?
Dear Crypto community, Yesterday we saw Waltonchain release their Open Source code which resulted in huge criticism regarding the oversight of removing the original copyright to the original codebase, Ethereum Go, on which it is based. Following this, the team have now updated the code to show the original copyright: Image from Github Source: https://github.com/WaltonChain/WaltonChain_Gwtc_Src/blob/mastep2p/rlpx.go?utm_source=share&utm_medium=ios_app Github: https://github.com/WaltonChain?tab=repositories I'd like to say thank you to the community for having such strong opinion on this matter, and for all the subreddit admins that assisted in creating clarity toward this. As a global community we should hold every blockchain up to the same standards, and I am grateful that this was shown in regard to the GNU General Public License. Now that the issue is resolved, and since Waltonchain is currently a hot topic, I implore all the coders and devs out there to delve deep into the code to see exactly what Waltonchain have released. Not just the modification to the eth codebase, but the additional code. What does the code allow? What we've been told as a community is that the Waltonchain source code has changes that allows for:
Security - DASHX11 - Most cryptographic algorithms used in cryptocurrencies use only one hash function for calculation. There are 11 of them in X11, which provides a higher degree of protection against hackers and scams. Waltonchain has customised the DASH X11 hashing algorithm to fit their purpose.
More secure than Bitcoin. The Bitcoin algorithm is SHA-256 is based on a previous secure hash algorithm family of standards, namely SHA-2, the hash functions within the X11 algorithm all successfully made it into the second-round in search for a new, more secure standard — SHA-3. Keccak, the function which won the competition and is therefore the new standard on which SHA-3 is based on, can at the very least be considered more secure that SHA-256.
Efficiency — Waltonchain have produced ASICs with the equivalent hashing power of 200GPUs (32–40kW) whilst using only 135W, thus helping the parent chain become decentralised
PoS aspect works in tandem with PoW, in that it adds a reduced difficulty based on number of coins held and time between blocks. Effectively the longer coins are held and the longer the time between blocks, the lower the difficulty for mining blocks. This again enhances the power efficiency of the network in its entirety.
Fast cross-chain searching via Proof of Labour —PoL enables hash values or indices from sub-chains (child chains) to be synced with the parent chain in a ‘cross chain index mechanism’ to enable fast searches for data via the parent chain.
Scalibility — Unlimited scalibility due to child chains; each CC is an independent blockchain (or DAG) using its own consensus mechanism (PoS, PoA, PoW, PoeT, etc) and can store data within itself. The parent chain by nature therefore cannot become bloated.
Atomic Swaps — PoL by nature ensures a record of every inter-chain transaction is held, and allows the function of atomic swaps between currencies.
Also to note is that the code has been audited by Knownsec, the same company that audited projects like HPB and NANO. Lets have an open dialogue and talk about these features of the code - but firstly, do they exist? Hopefully people will approach this with the same enthusiasm as they did yesterday. EDIT 1st June:A user on the Waltonchain sub has done an analysis which by the looks of it, disproves the initial assessment by many of the 'blockchain experts' in cc that have said the open source code is simply a copy and paste .https://www.reddit.com/waltonchain/comments/bveqea/changeset_goethereum_v171_to_gwtc_v110/ It is interesting to see just how much people love to hate Waltonchain that they spread misinformation either intentionally, or unintentionally, and that it gets the most attention out of any announcement. For reference: Block explorer:www.Waltonchain.pro(all wallets, mining wallet, documentation etc is available via that link)
Transcript of discussion between an ASIC designer and several proof-of-work designers from #monero-pow channel on Freenode this morning
[08:07:01] lukminer contains precompiled cn/r math sequences for some blocks: https://lukminer.org/2019/03/09/oh-kay-v4r-here-we-come/ [08:07:11] try that with RandomX :P [08:09:00] tevador: are you ready for some RandomX feedback? it looks like the CNv4 is slowly stabilizing, hashrate comes down... [08:09:07] how does it even make sense to precompile it? [08:09:14] mine 1% faster for 2 minutes? [08:09:35] naturally we think the entire asic-resistance strategy is doomed to fail :) but that's a high-level thing, who knows. people may think it's great. [08:09:49] about RandomX: looks like the cache size was chosen to make it GPU-hard [08:09:56] looking forward to more docs [08:11:38] after initial skimming, I would think it's possible to make a 10x asic for RandomX. But at least for us, we will only make an ASIC if there is not a total ASIC hostility there in the first place. That's better for the secret miners then. [08:13:12] What I propose is this: we are working on an Ethash ASIC right now, and once we have that working, we would invite tevador or whoever wants to come to HK/Shenzhen and we walk you guys through how we would make a RandomX ASIC. You can then process this input in any way you like. Something like that. [08:13:49] unless asics (or other accelerators) re-emerge on XMR faster than expected, it looks like there is a little bit of time before RandomX rollout [08:14:22] 10x in what measure? $/hash or watt/hash? [08:14:46] watt/hash [08:15:19] so you can make 10 times more efficient double precisio FPU? [08:16:02] like I said let's try to be productive. You are having me here, let's work together! [08:16:15] continue with RandomX, publish more docs. that's always helpful. [08:16:37] I'm trying to understand how it's possible at all. Why AMD/Intel are so inefficient at running FP calculations? [08:18:05] midipoet ([email protected]/web/irccloud.com/x-vszshqqxwybvtsjm) has joined #monero-pow [08:18:17] hardware development works the other way round. We start with 1) math then 2) optimization priority 3) hw/sw boundary 4) IP selection 5) physical implementation [08:22:32] This still doesn't explain at which point you get 10x [08:23:07] Weren't you the ones claiming "We can accelerate ProgPoW by a factor of 3x to 8x." ? I find it hard to believe too. [08:30:20] sure [08:30:26] so my idea: first we finish our current chip [08:30:35] from simulation to silicon :) [08:30:40] we love this stuff... we do it anyway [08:30:59] now we have a communication channel, and we don't call each other names immediately anymore: big progress! [08:31:06] you know, we russians have a saying "it was smooth on paper, but they forgot about ravines" [08:31:12] So I need a bit more details [08:31:16] ha ha. good! [08:31:31] that's why I want to avoid to just make claims [08:31:34] let's work [08:31:40] RandomX comes in Sep/Oct, right? [08:31:45] Maybe [08:32:20] We need to audit it first [08:32:31] ok [08:32:59] we don't make chips to prove sw devs that their assumptions about hardware are wrong. especially not if these guys then promptly hardfork and move to the next wrong assumption :) [08:33:10] from the outside, this only means that hw & sw are devaluing each other [08:33:24] neither of us should do this [08:33:47] we are making chips that can hopefully accelerate more crypto ops in the future [08:33:52] signing, verifying, proving, etc. [08:34:02] PoW is just a feature like others [08:34:18] sech1: is it easy for you to come to Hong Kong? (visa-wise) [08:34:20] or difficult? [08:34:33] or are you there sometimes? [08:34:41] It's kind of far away [08:35:13] we are looking forward to more RandomX docs. that's the first step. [08:35:31] I want to avoid that we have some meme "Linzhi says they can accelerate XYZ by factor x" .... "ha ha ha" [08:35:37] right? we don't want that :) [08:35:39] doc is almost finished [08:35:40] What docs do you need? It's described pretty good [08:35:41] so I better say nothing now [08:35:50] we focus on our Ethash chip [08:36:05] then based on that, we are happy to walk interested people through the design and what else it can do [08:36:22] that's a better approach from my view than making claims that are laughed away (rightfully so, because no silicon...) [08:36:37] ethash ASIC is basically a glorified memory controller [08:36:39] sech1: tevador said something more is coming (he just did it again) [08:37:03] yes, some parts of RandomX are not described well [08:37:10] like dataset access logic [08:37:37] RandomX looks like progpow for CPU [08:37:54] yes [08:38:03] it is designed to reflect CPU [08:38:34] so any ASIC for it = CPU in essence [08:39:04] of course there are still some things in regular CPU that can be thrown away for RandomX [08:40:20] uncore parts are not used, but those will use very little power [08:40:37] except for memory controller [08:41:09] I'm just surprised sometimes, ok? let me ask: have you designed or taped out an asic before? isn't it risky to make assumptions about things that are largely unknown? [08:41:23] I would worry [08:41:31] that I get something wrong... [08:41:44] but I also worry like crazy that CNv4 will blow up, where you guys seem to be relaxed [08:42:06] I didn't want to bring up anything RandomX because CNv4 is such a nailbiter... :) [08:42:15] how do you guys know you don't have asics in a week or two? [08:42:38] we don't have experience with ASIC design, but RandomX is simply designed to exactly fit CPU capabilities, which is the best you can do anyways [08:43:09] similar as ProgPoW did with GPUs [08:43:14] some people say they want to do asic-resistance only until the vast majority of coins has been issued [08:43:21] that's at least reasonable [08:43:43] yeah but progpow totally will not work as advertised :) [08:44:08] yeah, I've seen that comment about progpow a few times already [08:44:11] which is no surprise if you know it's just a random sales story to sell a few more GPUs [08:44:13] RandomX is not permanent, we are expecting to switch to ASIC friendly in a few years if possible [08:44:18] yes [08:44:21] that makes sense [08:44:40] linzhi-sonia: how so? will it break or will it be asic-able with decent performance gains? [08:44:41] are you happy with CNv4 so far? [08:45:10] ah, long story. progpow is a masterpiece of deception, let's not get into it here. [08:45:21] if you know chip marketing it makes more sense [08:45:24] linzhi-sonia: So far? lol! a bit early to tell, don't you think? [08:45:35] the diff is coming down [08:45:41] first few hours looked scary [08:45:43] I remain skeptical: I only see ASICs being reasonable if they are already as ubiquitous as smartphones [08:45:46] yes, so far so good [08:46:01] we kbew the diff would not come down ubtil affter block 75 [08:46:10] yes [08:46:22] but first few hours it looks like only 5% hashrate left [08:46:27] looked [08:46:29] now it's better [08:46:51] the next worry is: when will "unexplainable" hashrate come back? [08:47:00] you hope 2-3 months? more? [08:47:05] so give it another couple of days. will probably overshoot to the downside, and then rise a bit as miners get updated and return [08:47:22] 3 months minimum turnaround, yes [08:47:28] nah [08:47:36] don't underestimate asicmakers :) [08:47:54] you guys don't get #1 priority on chip fabs [08:47:56] 3 months = 90 days. do you know what is happening in those 90 days exactly? I'm pretty sure you don't. same thing as before. [08:48:13] we don't do any secret chips btw [08:48:21] 3 months assumes they had a complete design ready to go, and added the last minute change in 1 day [08:48:24] do you know who is behind the hashrate that is now bricked? [08:48:27] innosilicon? [08:48:34] hyc: no no, and no. :) [08:48:44] hyc: have you designed or taped out a chip before? [08:48:51] yes, many years ago [08:49:10] then you should know that 90 days is not a fixed number [08:49:35] sure, but like I said, other makers have greater demand [08:49:35] especially not if you can prepare, if you just have to modify something, or you have more programmability in the chip than some people assume [08:50:07] we are chipmakers, we would never dare to do what you guys are doing with CNv4 :) but maybe that just means you are cooler! [08:50:07] and yes, programmability makes some aspect of turnaround easier [08:50:10] all fine [08:50:10] I hope it works! [08:50:28] do you know who is behind the hashrate that is now bricked? [08:50:29] inno? [08:50:41] we suspect so, but have no evidence [08:50:44] maybe we can try to find them, but we cannot spend too much time on this [08:50:53] it's probably not so much of a secret [08:51:01] why should it be, right? [08:51:10] devs want this cat-and-mouse game? devs get it... [08:51:35] there was one leak saying it's innosilicon [08:51:36] so you think 3 months, ok [08:51:43] inno is cool [08:51:46] good team [08:51:49] IP design house [08:51:54] in Wuhan [08:52:06] they send their people to conferences with fake biz cards :) [08:52:19] pretending to be other companies? [08:52:26] sure [08:52:28] ha ha [08:52:39] so when we see them, we look at whatever card they carry and laugh :) [08:52:52] they are perfectly suited for secret mining games [08:52:59] they made at most $6 million in 2 months of mining, so I wonder if it was worth it [08:53:10] yeah. no way to know [08:53:15] but it's good that you calculate! [08:53:24] this is all about cost/benefit [08:53:25] then you also understand - imagine the value of XMR goes up 5x, 10x [08:53:34] that whole "asic resistance" thing will come down like a house of cards [08:53:41] I would imagine they sell immediately [08:53:53] the investor may fully understand the risk [08:53:57] the buyer [08:54:13] it's not healthy, but that's another discussion [08:54:23] so mid-June [08:54:27] let's see [08:54:49] I would be susprised if CNv4 ASICs show up at all [08:54:56] surprised* [08:54:56] why? [08:55:05] is only an economic question [08:55:12] yeah should be interesting. FPGAs will be near their limits as well [08:55:16] unless XMR goes up a lot [08:55:19] no, not *only*. it's also a technology question [08:55:44] you believe CNv4 is "asic resistant"? which feature? [08:55:53] it's not [08:55:59] cnv4 = Rabdomx ? [08:56:03] no [08:56:07] cnv4=cryptinight/r [08:56:11] ah [08:56:18] CNv4 is the one we have now, I think [08:56:21] since yesterday [08:56:30] it's plenty enough resistant for current XMR price [08:56:45] that may be, yes! [08:56:55] I look at daily payouts. XMR = ca. 100k USD / day [08:57:03] it can hold until October, but it's not asic resistant [08:57:23] well, last 24h only 22,442 USD :) [08:57:32] I think 80 h/s per watt ASICs are possible for CNv4 [08:57:38] linzhi-sonia where do you produce your chips? TSMC? [08:57:44] I'm cruious how you would expect to build a randomX ASIC that outperforms ARM cores for efficiency, or Intel cores for raw speed [08:57:48] curious [08:58:01] yes, tsmc [08:58:21] Our team did the world's first bitcoin asic, Avalon [08:58:25] and upcoming 2nd gen Ryzens (64-core EPYC) will be a blast at RandomX [08:58:28] designed and manufactured [08:58:53] still being marketed? [08:59:03] linzhi-sonia: do you understand what xmr wants to achieve, community-wise? [08:59:14] Avalon? as part of Canaan Creative, yes I think so. [08:59:25] there's not much interesting oing on in SHA256 [08:59:29] Inge-: I would think so, but please speak [08:59:32] hyc: yes [09:00:28] linzhi-sonia: i am curious to hear your thoughts. I am fairly new to this space myself... [09:00:51] oh [09:00:56] we are grandpas, and grandmas [09:01:36] yet I have no problem understanding why ASICS are currently reviled. [09:01:48] xmr's main differentiators to, let's say btc, are anonymity and fungibility [09:01:58] I find the client terribly slow btw [09:02:21] and I think the asic-forking since last may is wrong, doesn't create value and doesn't help with the project objectives [09:02:25] which "the client" ? [09:02:52] Monero GUI client maybe [09:03:12] MacOS, yes [09:03:28] What exactly is slow? [09:03:30] linzhi-sonia: I run my own node, and use the CLI and Monerujo. Have not had issues. [09:03:49] staying in sync [09:03:49] linzhi-sonia: decentralization is also a key principle [09:03:56] one that Bitcoin has failed to maintain [09:04:39] hmm [09:05:00] looks fairly decentralized to me. decentralization is the result of 3 goals imo: resilient, trustless, permissionless [09:05:28] don't ask a hardware maker about physical decentralization. that's too ideological. we focus on logical decentralization. [09:06:11] physical decentralization is important. with bulk of bitnoin mining centered on Chinese hydroelectric dams [09:06:19] have you thought about including block data in the PoW? [09:06:41] yes, of course. [09:07:39] is that already in an algo? [09:08:10] hyc: about "centered on chinese hydro" - what is your source? the best paper I know is this: https://coinshares.co.uk/wp-content/uploads/2018/11/Mining-Whitepaper-Final.pdf [09:09:01] linzhi-sonia: do you mine on your ASICs before you sell them? [09:09:13] besides testing of course [09:09:45] that paper puts Chinese btc miners at 60% max [09:10:05] tevador: I think everybody learned that that is not healthy long-term! [09:10:16] because it gives the chipmaker a cost advantage over its own customers [09:10:33] and cost advantage leads to centralization (physical and logical) [09:10:51] you guys should know who finances progpow and why :) [09:11:05] but let's not get into this, ha ha. want to keep the channel civilized. right OhGodAGirl ? :) [09:11:34] tevador: so the answer is no! 100% and definitely no [09:11:54] that "self-mining" disease was one of the problems we have now with asics, and their bad reputation (rightfully so) [09:13:08] I plan to write a nice short 2-page paper or so on our chip design process. maybe it's interesting to some people here. [09:13:15] basically the 5 steps I mentioned before, from math to physical [09:13:32] linzhi-sonia: the paper you linked puts 48% of bitcoin mining in Sichuan. the total in China is much more than 60% [09:13:38] need to run it by a few people to fix bugs, will post it here when published [09:14:06] hyc: ok! I am just sharing the "best" document I know today. it definitely may be wrong and there may be a better one now. [09:14:18] hyc: if you see some reports, please share [09:14:51] hey I am really curious about this: where is a PoW algo that puts block data into the PoW? [09:15:02] the previous paper I read is from here http://hackingdistributed.com/2018/01/15/decentralization-bitcoin-ethereum/ [09:15:38] hyc: you said that already exists? (block data in PoW) [09:15:45] it would make verification harder [09:15:49] linzhi-sonia: https://the-eye.eu/public/Books/campdivision.com/PDF/Computers%20General/Privacy/bitcoin/meh/hashimoto.pdf [09:15:51] but for chips it would be interesting [09:15:52] we discussed the possibility about a year ago https://www.reddit.com/Monero/comments/8bshrx/what_we_need_to_know_about_proof_of_work_pow/ [09:16:05] oh good links! thanks! need to read... [09:16:06] I think that paper by dryja was original [09:17:53] since we have a nice flow - second question I'm very curious about: has anyone thought about in-protocol rewards for other functions? [09:18:55] we've discussed micropayments for wallets to use remote nodes [09:18:55] you know there is a lot of work in other coins about STARK provers, zero-knowledge, etc. many of those things very compute intense, or need to be outsourced to a service (zether). For chipmakers, in-protocol rewards create an economic incentive to accelerate those things. [09:19:50] whenever there is an in-protocol reward, you may get the power of ASICs doing something you actually want to happen [09:19:52] it would be nice if there was some economic reward for running a fullnode, but no one has come up with much more than that afaik [09:19:54] instead of fighting them off [09:20:29] you need to use asics, not fight them. that's an obvious thing to say for an asicmaker... [09:20:41] in-protocol rewards can be very powerful [09:20:50] like I said before - unless the ASICs are so useful they're embedded in every smartphone, I dont see them being a positive for decentralization [09:21:17] if they're a separate product, the average consumer is not going to buy them [09:21:20] now I was talking about speedup of verifying, signing, proving, etc. [09:21:23] they won't even know what they are [09:22:07] if anybody wants to talk about or design in-protocol rewards, please come talk to us [09:22:08] the average consumer also doesn't use general purpose hardware to secure blockchains either [09:22:14] not just for PoW, in fact *NOT* for PoW [09:22:32] it requires sw/hw co-design [09:23:10] we are in long-term discussions/collaboration over this with Ethereum, Bitcoin Cash. just talk right now. [09:23:16] this was recently published though suggesting more uptake though I guess https://btcmanager.com/college-students-are-the-second-biggest-miners-of-cryptocurrency/ [09:23:29] I find it pretty hard to believe their numbers [09:24:03] well [09:24:09] sorry, original article: https://www.pcmag.com/news/366952/college-kids-are-using-campus-electricity-to-mine-crypto [09:24:11] just talk, no? rumors [09:24:18] college students are already more educated than the average consumer [09:24:29] we are not seeing many such customers anymore [09:24:30] it's data from cisco monitoring network traffic