Help! Bitcoin Client Out Of Sync By 35000 Blocks ...

Proposal: The Sia Foundation

Vision Statement

A common sentiment is brewing online; a shared desire for the internet that might have been. After decades of corporate encroachment, you don't need to be a power user to realize that something has gone very wrong.
In the early days of the internet, the future was bright. In that future, when you sent an instant message, it traveled directly to the recipient. When you needed to pay a friend, you announced a transfer of value to their public key. When an app was missing a feature you wanted, you opened up the source code and implemented it. When you took a picture on your phone, it was immediately encrypted and backed up to storage that you controlled. In that future, people would laugh at the idea of having to authenticate themselves to some corporation before doing these things.
What did we get instead? Rather than a network of human-sized communities, we have a handful of enormous commons, each controlled by a faceless corporate entity. Hey user, want to send a message? You can, but we'll store a copy of it indefinitely, unencrypted, for our preference-learning algorithms to pore over; how else could we slap targeted ads on every piece of content you see? Want to pay a friend? You can—in our Monopoly money. Want a new feature? Submit a request to our Support Center and we'll totally maybe think about it. Want to backup a photo? You can—inside our walled garden, which only we (and the NSA, of course) can access. Just be careful what you share, because merely locking you out of your account and deleting all your data is far from the worst thing we could do.
You rationalize this: "MEGACORP would never do such a thing; it would be bad for business." But we all know, at some level, that this state of affairs, this inversion of power, is not merely "unfortunate" or "suboptimal" – No. It is degrading. Even if MEGACORP were purely benevolent, it is degrading that we must ask its permission to talk to our friends; that we must rely on it to safeguard our treasured memories; that our digital lives are completely beholden to those who seek only to extract value from us.
At the root of this issue is the centralization of data. MEGACORP can surveil you—because your emails and video chats flow through their servers. And MEGACORP can control you—because they hold your data hostage. But centralization is a solution to a technical problem: How can we make the user's data accessible from anywhere in the world, on any device? For a long time, no alternative solution to this problem was forthcoming.
Today, thanks to a confluence of established techniques and recent innovations, we have solved the accessibility problem without resorting to centralization. Hashing, encryption, and erasure encoding got us most of the way, but one barrier remained: incentives. How do you incentivize an anonymous stranger to store your data? Earlier protocols like BitTorrent worked around this limitation by relying on altruism, tit-for-tat requirements, or "points" – in other words, nothing you could pay your electric bill with. Finally, in 2009, a solution appeared: Bitcoin. Not long after, Sia was born.
Cryptography has unleashed the latent power of the internet by enabling interactions between mutually-distrustful parties. Sia harnesses this power to turn the cloud storage market into a proper marketplace, where buyers and sellers can transact directly, with no intermediaries, anywhere in the world. No more silos or walled gardens: your data is encrypted, so it can't be spied on, and it's stored on many servers, so no single entity can hold it hostage. Thanks to projects like Sia, the internet is being re-decentralized.
Sia began its life as a startup, which means it has always been subjected to two competing forces: the ideals of its founders, and the profit motive inherent to all businesses. Its founders have taken great pains to never compromise on the former, but this often threatened the company's financial viability. With the establishment of the Sia Foundation, this tension is resolved. The Foundation, freed of the obligation to generate profit, is a pure embodiment of the ideals from which Sia originally sprung.
The goals and responsibilities of the Foundation are numerous: to maintain core Sia protocols and consensus code; to support developers building on top of Sia and its protocols; to promote Sia and facilitate partnerships in other spheres and communities; to ensure that users can easily acquire and safely store siacoins; to develop network scalability solutions; to implement hardforks and lead the community through them; and much more. In a broader sense, its mission is to commoditize data storage, making it cheap, ubiquitous, and accessible to all, without compromising privacy or performance.
Sia is a perfect example of how we can achieve better living through cryptography. We now begin a new chapter in Sia's history. May our stewardship lead it into a bright future.
 

Overview

Today, we are proposing the creation of the Sia Foundation: a new non-profit entity that builds and supports distributed cloud storage infrastructure, with a specific focus on the Sia storage platform. What follows is an informal overview of the Sia Foundation, covering two major topics: how the Foundation will be funded, and what its funds will be used for.

Organizational Structure

The Sia Foundation will be structured as a non-profit entity incorporated in the United States, likely a 501(c)(3) organization or similar. The actions of the Foundation will be constrained by its charter, which formalizes the specific obligations and overall mission outlined in this document. The charter will be updated on an annual basis to reflect the current goals of the Sia community.
The organization will be operated by a board of directors, initially comprising Luke Champine as President and Eddie Wang as Chairman. Luke Champine will be leaving his position at Nebulous to work at the Foundation full-time, and will seek to divest his shares of Nebulous stock along with other potential conflicts of interest. Neither Luke nor Eddie personally own any siafunds or significant quantities of siacoin.

Funding

The primary source of funding for the Foundation will come from a new block subsidy. Following a hardfork, 30 KS per block will be allocated to the "Foundation Fund," continuing in perpetuity. The existing 30 KS per block miner reward is not affected. Additionally, one year's worth of block subsidies (approximately 1.57 GS) will be allocated to the Fund immediately upon activation of the hardfork.
As detailed below, the Foundation will provably burn any coins that it cannot meaningfully spend. As such, the 30 KS subsidy should be viewed as a maximum. This allows the Foundation to grow alongside Sia without requiring additional hardforks.
The Foundation will not be funded to any degree by the possession or sale of siafunds. Siafunds were originally introduced as a means of incentivizing growth, and we still believe in their effectiveness: a siafund holder wants to increase the amount of storage on Sia as much as possible. While the Foundation obviously wants Sia to succeed, its driving force should be its charter. Deriving significant revenue from siafunds would jeopardize the Foundation's impartiality and focus. Ultimately, we want the Foundation to act in the best interests of Sia, not in growing its own budget.

Responsibilities

The Foundation inherits a great number of responsibilities from Nebulous. Each quarter, the Foundation will publish the progress it has made over the past quarter, and list the responsibilities it intends to prioritize over the coming quarter. This will be accompanied by a financial report, detailing each area of expenditure over the past quarter, and forecasting expenditures for the coming quarter. Below, we summarize some of the myriad responsibilities towards which the Foundation is expected to allocate its resources.

Maintain and enhance core Sia software

Arguably, this is the most important responsibility of the Foundation. At the heart of Sia is its consensus algorithm: regardless of other differences, all Sia software must agree upon the content and rules of the blockchain. It is therefore crucial that the algorithm be stewarded by an entity that is accountable to the community, transparent in its decision-making, and has no profit motive or other conflicts of interest.
Accordingly, Sia’s consensus functionality will no longer be directly maintained by Nebulous. Instead, the Foundation will release and maintain an implementation of a "minimal Sia full node," comprising the Sia consensus algorithm and P2P networking code. The source code will be available in a public repository, and signed binaries will be published for each release.
Other parties may use this code to provide alternative full node software. For example, Nebulous may extend the minimal full node with wallet, renter, and host functionality. The source code of any such implementation may be submitted to the Foundation for review. If the code passes review, the Foundation will provide "endorsement signatures" for the commit hash used and for binaries compiled internally by the Foundation. Specifically, these signatures assert that the Foundation believes the software contains no consensus-breaking changes or other modifications to imported Foundation code. Endorsement signatures and Foundation-compiled binaries may be displayed and distributed by the receiving party, along with an appropriate disclaimer.
A minimal full node is not terribly useful on its own; the wallet, renter, host, and other extensions are what make Sia a proper developer platform. Currently, the only implementations of these extensions are maintained by Nebulous. The Foundation will contract Nebulous to ensure that these extensions continue to receive updates and enhancements. Later on, the Foundation intends to develop its own implementations of these extensions and others. As with the minimal node software, these extensions will be open source and available in public repositories for use by any Sia node software.
With the consensus code now managed by the Foundation, the task of implementing and orchestrating hardforks becomes its responsibility as well. When the Foundation determines that a hardfork is necessary (whether through internal discussion or via community petition), a formal proposal will be drafted and submitted for public review, during which arguments for and against the proposal may be submitted to a public repository. During this time, the hardfork code will be implemented, either by Foundation employees or by external contributors working closely with the Foundation. Once the implementation is finished, final arguments will be heard. The Foundation board will then vote whether to accept or reject the proposal, and announce their decision along with appropriate justification. Assuming the proposal was accepted, the Foundation will announce the block height at which the hardfork will activate, and will subsequently release source code and signed binaries that incorporate the hardfork code.
Regardless of the Foundation's decision, it is the community that ultimately determines whether a fork is accepted or rejected – nothing can change that. Foundation node software will never automatically update, so all forks must be explicitly adopted by users. Furthermore, the Foundation will provide replay and wipeout protection for its hard forks, protecting other chains from unintended or malicious reorgs. Similarly, the Foundation will ensure that any file contracts formed prior to a fork activation will continue to be honored on both chains until they expire.
Finally, the Foundation also intends to pursue scalability solutions for the Sia blockchain. In particular, work has already begun on an implementation of Utreexo, which will greatly reduce the space requirements of fully-validating nodes (allowing a full node to be run on a smartphone) while increasing throughput and decreasing initial sync time. A hardfork implementing Utreexo will be submitted to the community as per the process detailed above.
As this is the most important responsibility of the Foundation, it will receive a significant portion of the Foundation’s budget, primarily in the form of developer salaries and contracting agreements.

Support community services

We intend to allocate 25% of the Foundation Fund towards the community. This allocation will be held and disbursed in the form of siacoins, and will pay for grants, bounties, hackathons, and other community-driven endeavours.
Any community-run service, such as a Skynet portal, explorer or web wallet, may apply to have its costs covered by the Foundation. Upon approval, the Foundation will reimburse expenses incurred by the service, subject to the exact terms agreed to. The intent of these grants is not to provide a source of income, but rather to make such services "break even" for their operators, so that members of the community can enrich the Sia ecosystem without worrying about the impact on their own finances.

Ensure easy acquisition and storage of siacoins

Most users will acquire their siacoins via an exchange. The Foundation will provide support to Sia-compatible exchanges, and pursue relevant integrations at its discretion, such as Coinbase's new Rosetta standard. The Foundation may also release DEX software that enables trading cryptocurrencies without the need for a third party. (The Foundation itself will never operate as a money transmitter.)
Increasingly, users are storing their cryptocurrency on hardware wallets. The Foundation will maintain the existing Ledger Nano S integration, and pursue further integrations at its discretion.
Of course, all hardware wallets must be paired with software running on a computer or smartphone, so the Foundation will also develop and/or maintain client-side wallet software, including both full-node wallets and "lite" wallets. Community-operated wallet services, i.e. web wallets, may be funded via grants.
Like core software maintenance, this responsibility will be funded in the form of developer salaries and contracting agreements.

Protect the ecosystem

When it comes to cryptocurrency security, patching software vulnerabilities is table stakes; there are significant legal and social threats that we must be mindful of as well. As such, the Foundation will earmark a portion of its fund to defend the community from legal action. The Foundation will also safeguard the network from 51% attacks and other threats to network security by implementing softforks and/or hardforks where necessary.
The Foundation also intends to assist in the development of a new FOSS software license, and to solicit legal memos on various Sia-related matters, such as hosting in the United States and the EU.
In a broader sense, the establishment of the Foundation makes the ecosystem more robust by transferring core development to a more neutral entity. Thanks to its funding structure, the Foundation will be immune to various forms of pressure that for-profit companies are susceptible to.

Drive adoption of Sia

Although the overriding goal of the Foundation is to make Sia the best platform it can be, all that work will be in vain if no one uses the platform. There are a number of ways the Foundation can promote Sia and get it into the hands of potential users and developers.
In-person conferences are understandably far less popular now, but the Foundation can sponsor and/or participate in virtual conferences. (In-person conferences may be held in the future, permitting circumstances.) Similarly, the Foundation will provide prizes for hackathons, which may be organized by community members, Nebulous, or the Foundation itself. Lastly, partnerships with other companies in the cryptocurrency space—or the cloud storage space—are a great way to increase awareness of Sia. To handle these responsibilities, one of the early priorities of the Foundation will be to hire a marketing director.

Fund Management

The Foundation Fund will be controlled by a multisig address. Each member of the Foundation's board will control one of the signing keys, with the signature threshold to be determined once the final composition of the board is known. (This threshold may also be increased or decreased if the number of board members changes.) Additionally, one timelocked signing key will be controlled by David Vorick. This key will act as a “dead man’s switch,” to be used in the event of an emergency that prevents Foundation board members from reaching the signature threshold. The timelock ensures that this key cannot be used unless the Foundation fails to sign a transaction for several months.
On the 1st of each month, the Foundation will use its keys to transfer all siacoins in the Fund to two new addresses. The first address will be controlled by a high-security hot wallet, and will receive approximately one month's worth of Foundation expenditures. The second address, receiving the remaining siacoins, will be a modified version of the source address: specifically, it will increase the timelock on David Vorick's signing key by one month. Any other changes to the set of signing keys, such as the arrival or departure of board members, will be incorporated into this address as well.
The Foundation Fund is allocated in SC, but many of the Foundation's expenditures must be paid in USD or other fiat currency. Accordingly, the Foundation will convert, at its discretion, a portion of its monthly withdrawals to fiat currency. We expect this conversion to be primarily facilitated by private "OTC" sales to accredited investors. The Foundation currently has no plans to speculate in cryptocurrency or other assets.
Finally, it is important that the Foundation adds value to the Sia platform well in excess of the inflation introduced by the block subsidy. For this reason, the Foundation intends to provably burn, on a quarterly basis, any coins that it cannot allocate towards any justifiable expense. In other words, coins will be burned whenever doing so provides greater value to the platform than any other use. Furthermore, the Foundation will cap its SC treasury at 5% of the total supply, and will cap its USD treasury at 4 years’ worth of predicted expenses.
 
Addendum: Hardfork Timeline
We would like to see this proposal finalized and accepted by the community no later than September 30th. A new version of siad, implementing the hardfork, will be released no later than October 15th. The hardfork will activate at block 293220, which is expected to occur around 12pm EST on January 1st, 2021.
 
Addendum: Inflation specifics
The total supply of siacoins as of January 1st, 2021 will be approximately 45.243 GS. The initial subsidy of 1.57 GS thus increases the supply by 3.47%, and the total annual inflation in 2021 will be at most 10.4% (if zero coins are burned). In 2022, total annual inflation will be at most 6.28%, and will steadily decrease in subsequent years.
 

Conclusion

We see the establishment of the Foundation as an important step in the maturation of the Sia project. It provides the ecosystem with a sustainable source of funding that can be exclusively directed towards achieving Sia's ambitious goals. Compared to other projects with far deeper pockets, Sia has always punched above its weight; once we're on equal footing, there's no telling what we'll be able to achieve.
Nevertheless, we do not propose this change lightly, and have taken pains to ensure that the Foundation will act in accordance with the ideals that this community shares. It will operate transparently, keep inflation to a minimum, and respect the user's fundamental role in decentralized systems. We hope that everyone in the community will consider this proposal carefully, and look forward to a productive discussion.
submitted by lukechampine to siacoin [link] [comments]

RiB Newsletter #14 – Are We Smart (Contract) Yet?

We’re seeing a bunch of interesting Rust blockchain and crypto projects, so this month the “Interesting Things” section is loaded up with news, papers, and project links.
This month, Elrond, appeared on our radar with the launch of their mainnet. Although not written in Rust, it runs Rust smart contracts on its Arwen WASM VM, which itself is based on the Rust Wasmer VM. Along with NEAR, Nervos, and Enigma (and probably others), this continues an encouraging trend of blockchains enabling smart contracts in Rust. See the “Interesting Things” section for examples of Elrond’s Rust contracts.
Rust continues to be popular for research into zero-knowledge proofs, with Microsoft releasing Spartan, a zk-SNARK system without trusted setup.
In RiB news, we published a late one-year anniversary blog post. It has some reflection on the changes to, and growth of, RiB over the last year.
The Awesome Blockchain Rust project, which is maintained by Sun under the rust-in-blockchain GitHub org, has received a stream of updates recently, and is now published as the Awesome-RiB page on rustinblockchain.org.
It’s a pretty good resource for finding blockchain-related Rust projects, with links to many of the more prominent and mature projects noted in the RiB newsletter. It could use more eyes on it though.

Project Spotlight

Each month we like to shine a light on a notable Rust blockchain project. This month that project is…
ethers.rs
ethers.rs is an Ethereum & Celo library and wallet implementation, implemented as a port of the ethers.js library to Rust.
Ethereum client programming is usually done in JavaScript with either web3.js or ethers.js, with ethers.js being the newer of the two. These clients communicate to an Ethereum node, typically via JSON-RPC (or, when in the browser, via an “injected” client provider that follows EIP-1193, like MetaMask).
ethers.rs then provides a strongly-typed alternative for writing software that interacts with the Ethereum network.
As of now it is only suited for non-browser use cases, but if you prefer hacking in Rust to JavaScript, as some of us surely do, it is worth looking into for your next Ethereum project.
The author of ethers.rs, Georgios Konstantopoulos, accepts donations to sponsor their work.
Note that there is also a Rust alternative to web3.js, rust-web3.

Interesting Things

News

Blog Posts

Papers

Projects

Podcasts and Videos


Read more: https://rustinblockchain.org/newsletters/2020-08-05-are-we-smart-contract-yet/
submitted by Aimeedeer to rust [link] [comments]

Epic Cash Vitex Exchange AMA

What is EPIC CASH?
Epic Cash is the final point in the journey toward true P2P internet cash, the cornerstone of a private financial system. The Epic currency aims to become the world’s most effective privacy-protecting form of digital money. In order to fulfill that goal, it satisfies the three principal functions of money:
1. Store of Value — can be saved, retrieved, and exchanged at a later time, and of predictable value when retrieved;
2. Medium of Exchange — anything accepted as representing a standard of value and exchangeable for goods or services;
3. Unit of Account — the unit by which the value of a thing is accounted for and compared.
Website: http://epic.tech Whitepapers: http://epic.tech/whitepaper Epic Cash Community: https://t.me/EpicCash Miner Chat: https://t.me/EpicMiners Gitlab: gitlab.com/epiccash Twitter: twitter.com/EpicCashTech Social Media: http://epic.tech/social-media Exchanges: https://epic.tech/service-list
Oleg✌🏻
Hello community! Our AMA with EPIC begins🚀 We are very happy to have you here, on our joint AMA👌 So, lets start! The very first question for you. Can you introduce yourself?
Max Freeman | Epic Cash | Mimblewimble I’m Max Freeman, which stands for “Maximum Freedom for Mankind” — we believe that the existing fiat money system enslaves people by unfairly confiscating their wealth through inflation. By using an honest money system such as Epic, we can improve the quality of life for billions of people worldwide.
Yoga Dude Hello, I am Yoga Dude 🙂 I handle Marketing and PR, in crypto since 2011 started as Bitcoin miner, and in 2014 in Monero, and in 2015 in Ethereum, oh and briefly in DOGE for fun and unexpected profit. Heard about Epic Cash while learning about the Mimblewimble algo and joined the team last year.
JLong I am John, Doing the general engineering and managerial work
Max Freeman | Epic Cash | Mimblewimble I have been involved in early stage cryptos for the past 3 years, after building a global trading business for the past 20 years.
Oleg✌🏻 nice to meet you🙂
Max Freeman | Epic Cash | Mimblewimble Epic is a decentralized community project like Bitcoin or Monero, there is no central authority or corporation involved. We had no ICO and no premine, we had a fair launch at 0 supply last September.
Yoga Dude Great to meet everyone :)
Oleg✌🏻 Here we go the 1st question for you ~ 1. What is Epic Cash about?
Yoga Dude Epic Cash is designed to fulfill Satoshi’s original vision of P2P electronic cash, adjusting for what we learned from Bitcoin, a medium of exchange that is fast, free, open to all, while being private and fungible. We launched in September 2019 as a Proof of Work mineable crypto, without an ICO or a premine.
Oleg✌🏻 Look like a real Bitcoin🙂
Yoga Dude with privacy and fungibility 😄
Oleg✌🏻 Sounds cool! move on to the next question… 2. What makes Epic Cash better than Monero or other privacy coins?
Max Freeman | Epic Cash | Mimblewimble First off, we have a lot of respect for Monero and other privacy coins, we learned a lot from what they did right and what they did wrong, Our blockchain is much lighter than Monero or Bitcoin, our transaction engine is faster than Monero or ZCash. We use a three mining algo approach to allow more users the ability to obtain Epic Cash. We are a new, highly undervalued, coin and we look great not only for future use but for today's investment. Our blockchain is 90+% smaller than Monero or Bitcoin. Coins such as Zcash have optional privacy. Epic makes all transactions private, and it is impossible to trace movements of coins by watching wallet addresses.
Oleg✌🏻 Young and hot😋 security and privacy level is very important now but… 3. Why copy the same supply economics as Bitcoin?
Yoga Dude It is hard to compete with the success of Bitcoin today, part of the elegance and the appeal of Bitcoin is the responsible emission rate, terminating at 21million highly sub dividable coins. Like the Bitcoin supply curve, Epic Cash encourages early adopters, and with subsequent halvenings maintains a gradually diminishing flow of additional currency while preserving the overall value.
Max Freeman | Epic Cash | Mimblewimble In 2028, the supply of Epic matches that of Bitcoin and they stay in sync until the final coin is mined in 2140. We have 4 halvenings between now and then, which is demonstrated in Bitcoin to drive the value over market cycles. Epic is a chance for people who were late to Bitcoin to ride the wave and not miss their opportunity this time.
Oleg✌🏻 Interesting! 4. Why Choose Epic Cash over Grin and Beam?
Max Freeman | Epic Cash | Mimblewimble First of all, we have tremendous respect for all Mimblewimble currencies and their talented teams, they all taught us a lot and we are thankful for that. Without sounding too contentious, the choice seems obvious. We offer the same core tech, but with a much more responsible emission curve — Grin is an endless fountain of emission and inflation (60 per second forever), and Beam is even more frontloaded outpacing even Grin’s aggressive emission schedule for the next several years… We respect Grin and Beam, we learned from them, and we believe we are the next evolutionary step. Additionally, as we mentioned earlier, we offer more ways to mine Epic Cash, both with GPU and CPU and ASICs, this gives us more potential users and miners, vs Grin and Beam that are only mineable with GPUs.
Yoga Dude Yes, all that ☝️😄
Oleg✌🏻 I hope the miners read it all carefully 👌 Next question 5. Why have a development fund tax and what will it be used for?
Yoga Dude Dev fund tax today is at a reasonable 7.77% dropping by 1.11% every year until it hits zero. As Epic Cash grows in value these funds will become increasingly more relevant in additional technical, marketing, and fintech partnerships developments.
Oleg✌🏻 Very smart! 6. What is the advantage of 3 mining algorithms?
Max Freeman | Epic Cash | Mimblewimble By having multiple mining algorithms we are able to attract CPU, GPU, and ASIC miners simultaneously. Currently all other Mimblewimble currencies are mineable with GPU only ignoring a large segment of CPU miners. Monero made a splash migrating to the RandomX CPU mining algo. Epic Cash from the beginning embraces all mining communities. Many miners are successfully using older hardware such as Xeon processors to help secure the network. We use RandomX for CPU, ProgPow for GPU, and Cuckoo for ASIC.
Longer term, our flexible architecture means we can have many algorithms, not just 3. Our roadmap includes an allocation for SHA3 Keccak, which will help further decentralize the network and keep it unstoppable.
Yoga Dude We love miners 🙂 and Epic Cash can be mined with laptops and gaming rigs 🙂
Oleg✌🏻 A wide selection of mining methods is a great way to create a stable, decentralized and large network👌 Let’s talk about persons… 7. Who are the people developing Epic Cash?
Yoga Dude We are blessed with a very talented team of skilled developers with diverse backgrounds, many of them are volunteers who believe in what Epic Cash stands for and contribute with product and usability innovation. Our teams main focus is to make Epic Cash the best, most secure, most user friendly and usable product on the market, without making it unnecessarily techie, with as much mainstream user appeal as possible. This is a serious challenge but we are up for it 😄
Max Freeman | Epic Cash | Mimblewimble It is also important to note that we are a truly open ecosystem that anyone can participate in. Our community has developed wallets, mining pools, educational content, and much else besides. We are not limited by the funding generated during an ICO or VC investment, our users are an essential element of our team.
Oleg✌🏻 Sounds very attractive. 8. What do you think is currently lack in today’s crypto?
Max Freeman | Epic Cash | Mimblewimble We believe there is not enough privacy, anonymity and fungibility, although there is a growing awareness in the community as to why these are necessary. People are waking up to the fact that privacy is a right for everyone but today it is being exploited and violated by corporations, governments and unscrupulous individuals. Privacy does not mean that you have something to hide. We have doors on our houses, curtains on our windows, we wear clothes, and we have security on our bank accounts and businesses, not because we are criminals.
Fungibility (the property of not being able to distinguish one unit of currency from another) also has become a hot issue as people have started to get in trouble because of someone else’s misdeeds. Tainted money (coins that are blacklisted or restricted) is a problem for Bitcoin and Ethereum, the top two cryptos today. Mimblewimble eliminates the risk of tainted coins making them indistinguishable from each other. With traceable coins, you always have to worry if the coins you are getting were involved in a hack, or perhaps the darknet.
Oleg✌🏻 It’s good to see strong and safe coin in our time Let’s talk about your future… 9. What does the Epic Cash roadmap look like going forward?
Yoga Dude First and foremost, we are focused on security and usability.
We are working on a new, improved GUI wallet to incorporate the community feedback on ways to improve it.
We are in the process of completing final testing phases for the next iteration of Epic Cash which will make it more secure and stable. Once that is done, we will be rolling out Android and iOS support to make Epic Cash usable on leading smartphones and smartwatches. Beyond that without going into too much detail we are focused on continuous evolution of privacy, ease of mining, and overall speed and usability.
And of course we are constantly looking to add more exchanges both with and without KYC.
Oleg✌🏻 Are you working on Android and IOS wallet ? What will your application be?
Max Freeman | Epic Cash | Mimblewimble Yes, we will release a mobile wallet this year. It will bring us one step closer to people being able to actually use cryptocurrency as money in daily life.
Yoga Dude The idea is to be able to access Epic Cash from any platform and device
Max Freeman | Epic Cash | Mimblewimble Epic is very lightweight, which means that low-end devices such as smartwatches can participate.
Oleg✌🏻 Ok, got it. Thanks for clarification! 10. What else can you tell us about Epic Cash?
Max Freeman | Epic Cash | Mimblewimble Well one thing I really want to mention is our great Epic Cash community. We’ve been building a decentralized community organically, without the talk of price pumps, pressure to HODL and other BS crypto-gimmicks. Our community is truly global and consists of developers, volunteers, miners, and other Epic enthusiasts spreading the word about Epic Cash, helping us reach millions of people around the world to improve their quality of life through social media and directly. Everyone is an evangelist, everyone is an influencer, everyone has the power to make the world a better place to live in. As we continue to grow — the future looks Epic 😊
Yoga Dude Definitely the community! We got a talented crowd of very cool and motivated people from all over the world!
Oleg✌🏻 Thank you guys, for such informative answers 🙂 Now we proceed to Section 3, where a Community can ask their questions to the EPIC team Now I’ll open chat for the quite some time … Oleg✌🏻 Thank you all, dear community! EPIC team, please choose the 10 best questions you want to answer.
AngeI Everyone likes Privacy & Epic Cash provides their Best Privacy to users But, Which Technologies are being used by Epic Cash to make Blockchain very Private and Completely untrackable ?
Max Freeman | Epic Cash | Mimblewimble From the wallet to the node, Epic uses Dandelion++ to bounce transactions around the world before they go into the mempool for mining. Within the blockchain itself, Cut-Through merges all transactions in a block together, with CoinJoin automatically mixing all coins.
Beyond that, there are no addresses, so it’s impossible to watch someone’s wallet.
Arnold Even litecoin is implementing mimblewimble, Don’t you think it’s a significant threat for Epic if they implement it, then why would anyone use a less popular and a new cryptocurrency.
Max Freeman | Epic Cash | Mimblewimble LTC is implementing mw as an “extension block”, meaning that it is optional and not all transactions will use it. This is very different than the core protocol leveraging mw to make all transactions private and all coins fungible.
Aluta Why Epic cash so much focus on fungibility? Does fungibility matters that much?
Max Freeman | Epic Cash | Mimblewimble Fungibility is going to be one of the key issues within the cryptocurrency space in the coming years. Today, if you accept traceable coins from a seller, you are liable if they have ever been used in any illegal activity. This has led to a two tier market where freshly minted coins sell for more than circulated coins. When coins are fungible, like Epic, you don’t have to worry that you will run into a problem when an exchange or merchant blocks your transaction.
Joxes It is a pleasure.
When I first researched EpicCash, google showed me a youtube video that talked about how to mine with EpicCash. It made me ask: is this mining activity profitable so far?
We are in the early stages of development I guess, what adoption strategies are you taking to have sustained growth? is it feasible to reach N ° 500 rank in coinmarketcap in the medium term?
Yoga Dude When I got into crypto, it was by mining Bitcoin back in 2011 when you could still solve blocks on a single computer, but Bitcoin at the time was anything but profitable 😄 Today Epic Cash is still new, still young, and still undervalued. I believe it is mining-worthy because of its potential, not because of today’s price. By allowing Epic Cash to be mined with GPU and CPU on gaming rigs, servers, and even laptops we offer maximum public participation in our project. More people involved in the project, the more evangelists there are. We empower people to mine Epic Cash and to promote it.
S.P.A.D.E What new features of Epic Cash provide that Grin or Beam does not offer. Why do we need Epic Cash?
Max Freeman | Epic Cash | Mimblewimble They are great coins, but there are some ways in which Epic improves. Epic has better tokenomics than Grin and a more sustainable model than Beam, that has a company behind it that needs to repay investors via its high dev tax. this article explains in more detail https://medium.com/@frodofreeman/overview-of-mimblewimble-cryptocurrencies-7c70be146f50
Sahil What’s the Minimum Hardware / setup Required for Mining of EPIC Cash coins? Is Mining Profitable and Can we Mine EPIC Cash coins at Home?
Max Freeman | Epic Cash | Mimblewimble It is possible to mine on an ordinary laptop or desktop from the last 5 years, sometimes older. Epic is open to everyone, and our friendly community is standing by to help you get started at t.me/epicminers
Erven James Sato “TOKEN BURN” is BENEFECIAL for any projects, in able to CONTROL THE NUMBER OF TOKEN CIRCULATION and TO PROVIDE GREATER INCENTIVES TO INVESTORS.
Does your GREAT PROJECT have plan about TOKEN BURN?
Xenolink For deflating projects It is beneficial to drive the demand / scarcity / and price up in a faster pace. Epic Cash is here for the organic long run not the short run. However when it comes to long term economics elastic supplies whether inflating or deflating will not be a solid long term economic model. This has been heavily discussed already with Bitcoins inelastic Fixed 21 million supply in the past. Having a fixed model demonstrates good long term economics without worrying about balancing a deflating/inflating model. Bitcoin is a perfect example of a 21 million inelastic fixed supply model that has been proving itself till today. Which is why we are also using the same fixed 21 million supply model. Epic Cash plans to have a solid organic long term future to bring free private fungible money and make this world a better place.
Red Z🔥🤙 No one predicted the COVID-19 pandemic while developing their business model. But the crisis and recession of the global economy is our present with you and it affects all sectors, including blockchain. Will you make or have already made changes to the project roadmap, tokenomics? Do you have a plan in case the situation does not improve in the coming months and will affect the crypto industry even more?
Yoga Dude One thing we have seen as the result of the COVID-19 is more governments are talking about moving to digital cash — digital dollar in USA, digital Lira in Turkey, etc… If in the past the idea of digital money was not graspable by some people, today its the governments that are educating the people for us about the value of digital currency… What is ironic, the governments, by printing money to solve the economic consequences of COVID-19 also educating the consumer about the true “value” of fiat… What we offer is a touch free, borderless, private, anonymous, fungible currency that can not be printed beyond the initial defined algo. We are more responsible than the printing presses of the governments 🤔
kunlefighter How does the Dandelion++ Protocol, Confidential Transactions (CT) and CoinJoin assist in protecting the privacy of individuals and their transactions on Epic Cash Blockchain?
Max Freeman | Epic Cash | Mimblewimble Dandelion++ bounces transactions around before committing them to the blockchain, making it impossible to determine where they originated from. Confidential Transactions means that all tx are private, you can’t tell anything about where the coins have been or who they belonged to. CoinJoin in essence melts down and re-mints each coin every time it is used, making it impossible to track their ownership or usage history. Epic provides comprehensive privacy to everyone, without the compromises that other pre-mimblewimble coins have.
Dr Mönica Hello sir @maxfreeman4 @Johnsstec @Yogadude
Thanks for the ama I notice that Epic Cash has 2 type of new algorithm, progPoW version 0.15.0 and randomX version 1.0.3 NOW , CAN you tell me why you choose these 2 algorithm???
Yoga Dude We went with RandomX because it is a solid and very popular CPU centric algo used by several coins — most recently Monero. Most miners today heavily favor ASICs or GPUs, leaving a lot of solid high end users in the dust unable to mine emerging cryptos. As far as ProgPow, again its an established algo for GPU miners, and thanks to many cryptos starting with Bitcoin/Monero/Ethe etc there is no shortage of GPU rigs out there :) plus again the casual user with a video gaming caliber card can get in on the action.
Oleg✌🏻 Perfect! It was a great AMA, but it is coming to an end, thanks to everyone who was with us. Thanks EPIC team for taking the time👏. I hope our projects will be able to collaborate even more closely in the future and achieve new successes. Cheers!🎉
submitted by EpicCashFrodo to epiccash [link] [comments]

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
[09:24:33] and they're always looking for free money
[09:24:48] of course anyone with "free" electricity is inclined to do it
[09:24:57] but look at the rates, cannot make much money
[09:26:06] Ethereum is a bloated collection of bugs wrapped in a UI. I suppose they need all the help they can get
[09:26:29] Bitcoin Cash ... just another get rich quick scheme
[09:26:38] hmm :)
[09:26:51] I'll give it back to you, ok? ha ha. arrogance comes before the fall...
[09:27:17] maye we should have a little fun with CNv4 mining :)
[09:27:25] ;)
[09:27:38] come on. anyone who has watched their track record... $75M lost in ETH at DAO hack
[09:27:50] every smart contract that comes along is just waiting for another hack
[09:27:58] I just wanted to throw out the "in-protocol reward" thing, maybe someone sees the idea and wants to cowork. maybe not. maybe it's a stupid idea.
[09:29:18] linzhi-sonia: any thoughts on CN-GPU?
[09:29:55] CN-GPU has one positive aspect - it wastes chip area to implement all 18 hash algorithms
[09:30:19] you will always hear roughly the same feedback from me:
[09:30:52] "This algorithm very different, it heavy use floating point operations to hurt FPGAs and general purpose CPUs"
[09:30:56] the problem is, if it's profitable for people to buy ASIC miners and mine, it's always more profitable for the manufacturer to not sell and mine themselves
[09:31:02] "hurt"
[09:31:07] what is the point of this?
[09:31:15] it totally doesn't work
[09:31:24] you are hurting noone, just demonstrating lack of ability to think
[09:31:41] what is better: algo designed for chip, or chip designed for algo?
[09:31:43] fireice does it on daily basis, CN-GPU is a joke
[09:31:53] tevador: that's not really true, especially in a market with such large price fluctuations as cryptocurrency
[09:32:12] it's far less risky to sell miners than mine with them and pray that price doesn't crash for next six months
[09:32:14] I think it's great that crypto has a nice group of asicmakers now, hw & sw will cowork well
[09:32:36] jwinterm yes, that's why they premine them and sell after
[09:32:41] PoW is about being thermodynamically and cryptographically provable
[09:32:45] premining with them is taking on that risk
[09:32:49] not "fork when we think there are asics"
[09:32:51] business is about risk minimization
[09:32:54] that's just fear-driven
[09:33:05] Inge-: that's roughly the feedback
[09:33:24] I'm not saying it hasn't happened, but I think it's not so simple as saying "it always happens"
[09:34:00] jwinterm: it has certainly happened on BTC. and also on XMR.
[09:34:19] ironically, please think about it: these kinds of algos indeed prove the limits of the chips they were designed for. but they don't prove that you cannot implement the same algo differently! cannot!
[09:34:26] Risk minimization is not starting a business at all.
[09:34:34] proof-of-gpu-limit. proof-of-cpu-limit.
[09:34:37] imagine you have a money printing machine, would you sell it?
[09:34:39] proves nothing for an ASIC :)
[09:35:05] linzhi-sonia: thanks. I dont think anyone believes you can't make a more efficient cn-gpu asic than a gpu - but that it would not be orders of magnitude faster...
[09:35:24] ok
[09:35:44] like I say. these algos are, that's really ironic, designed to prove the limitatios of a particular chip in mind of the designer
[09:35:50] exactly the wrong way round :)
[09:36:16] like the cache size in RandomX :)
[09:36:18] beautiful
[09:36:29] someone looked at GPU designs
[09:37:31] linzhi-sonia can you elaborate? Cache size in RandomX was selected to fit CPU cache
[09:37:52] yes
[09:38:03] too large for GPU
[09:38:11] as I said, we are designing the algorithm to exactly fit CPU capabilities, I do not claim an ASIC cannot be more efficient
[09:38:16] ok!
[09:38:29] when will you do the audit?
[09:38:35] will the results be published in a document or so?
[09:38:37] I claim that single-chip ASIC is not viable, though
[09:39:06] you guys are brave, noone disputes that. 3 anti-asic hardforks now!
[09:39:18] 4th one coming
[09:39:31] 3 forks were done not only for this
[09:39:38] they had scheduled updates in the first place
[09:48:10] Monero is the #1 anti-asic fighter
[09:48:25] Monero is #1 for a lot of reasons ;)
[09:48:40] It's the coin with the most hycs.
[09:48:55] mooooo
[09:59:06] sneaky integer overflow, bug squished
[10:38:00] p0nziph0ne ([email protected]/vpn/privateinternetaccess/p0nziph0ne) has joined #monero-pow
[11:10:53] The convo here is wild
[11:12:29] it's like geo-politics at the intersection of software and hardware manufacturing for thermoeconomic value.
[11:13:05] ..and on a Sunday.
[11:15:43] midipoet: hw and sw should work together and stop silly games to devalue each other. to outsiders this is totally not attractive.
[11:16:07] I appreciate the positive energy here to try to listen, learn, understand.
[11:16:10] that's a start
[11:16:48] <-- p0nziph0ne ([email protected]/vpn/privateinternetaccess/p0nziph0ne) has quit (Quit: Leaving)
[11:16:54] we won't do silly mining against xmr "community" wishes, but not because we couldn'd do it, but because it's the wrong direction in the long run, for both sides
[11:18:57] linzhi-sonia: I agree to some extent. Though, in reality, there will always be divergence between social worlds. Not every body has the same vision of the future. Reaching societal consensus on reality tomorrow is not always easy
[11:20:25] absolutely. especially at a time when there is so much profit to be made from divisiveness.
[11:20:37] someone will want to make that profit, for sure
[11:24:32] Yes. Money distorts.
[11:24:47] Or wealth...one of the two
[11:26:35] Too much physical money will distort rays of light passing close to it indeed.
submitted by jwinterm to Monero [link] [comments]

AMA/Tutorial: Run a full node on AWS free tier with local LAN storage

AMA/Tutorial: Run a full node on AWS free tier with local LAN storage
This is a tutorial/AMA on how you can be running a full node, in the AWS cloud, for very low cost or even free.
I used to run a node on my local network but there is a problem with this; your public IP is broadcast, and then it gets associated with Bitcoin. Node owners are likely to own Bitcoin, and this raises your personal threat profile, validated against my IDS/IPS logs.
Run a VPN? Many VPNs are automatically blocked, or sketchy. Tor is also blocked on a large portion of the internet. Neither provide you with a real static IP, and that helps out the network.
There is a easy solution to this; run a node on the AWS free tier, and use an elastic IP so you have a static address. Bandwidth is free in, and low cost out, and you can control how much of that you use easily, and control your spent. The problem is that Amazon charges a LOT for online storage and even with a 1MB blocksize, the blockchain is very large and growing steadily! We mitigate this by using a VPN back to your network, where you can store the blockchain on a SMB share.
It is not complicated to do, but there are very many moving pieces to keep track of and configure. In order to fully trust your node, the best way is to build it from scratch. This is my goal in walking you through the process.
There are lots of ways to accomplish this same task; I only want to present one that works, and you can go from there. Once you have access to the blockchain in the cloud for reasonable prices, you can also look at things like the Lightning Network.
This article makes four major assumptions:

  1. That you have a OpenVPN server on your network and know how to configure it. I use pfSense and OpenVPN; others will work just as well, but you'll need to do a little work to figure out the particulars. If you don't know how, do not fret! There are loads of good tutorials for just about every platform. Or ask below. I also limited the user with access to the share at the firewall specifically to the IP hosting the share to lower the threat envelope.
  2. That you have the blockchain downloaded locally and reasonably up to date. If you don't, head on over to bitcoin.org and download it for OSX or Windows or Linux, whatever you use for your workstation. Follow the directions to set up the software and download/synchronize it to the network. This will take awhile! Once you've synchronized, copy the data directory to your SMB share you want the AWS instance to access. You could also synchronize everything directly on AWS too, but it will likely take longer and may cost a bit for the bandwidth.
  3. That you're on windows. OSX and Linux will have slightly different processes to connect to the instance via the terminal and SSH. If you need help, ask, and I am sure we can get you fixed up.
  4. That you've read the excellent bitcoin.org full node tutorial here: https://bitcoin.org/en/full-node

With that, on with the show!
First: Head on over to https://aws.amazon.com/ and make yourself an account.
Once you've set up you'll need to start the process of creating a virtual machine on AWS. Look for this graphic and click on it:

Start by launching a new machine

Follow the rabbit hole, and you'll be looking to create a plain jane Amazon AMI Linux instance. It looks like this:

Pick the basic AMI instance
Keep in mind you want to pick the x86 version, which is the default.

Continue clicking, you'll want to select the t2.micro instance that is eligible for the free tier for new accounts.

Pick the free tier. You can also upgrade to the smaller tier for more ram, but the micro works for now.
Now, you're going to need a way to connect to your soon-to-be-created node in the cloud. Amazon uses SSH keys to do this, so the next step means you're going to make some. You need to save this file, as if you lose it, you won't be able to access your node anymore. Much like your wallet private keys!

Beware losing your keys!

If you've made it this far, you're almost launched!
Now we need to convert the key to a format that we can use to connect to the instance from Windows. I recommend using Putty! https://www.putty.org/ if you don't have it already; if you're on OSX or Linux, you likely have what you need already.
Follow the guide here to get connected: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html

Next you'll need to set up a opening in the firewall if you want incoming connections. This is done by adding to the security group in the "Network and Security" section; edit it to look like this:

Change the inbound security rules for the instance to accept incoming connections on 8333.

The hard part is over!
Optional: Configuring a static IP. Amazon calls their implementation "elastic" IPs, but it's really a static IP that you can move around between instances very easily. It will ensure your public address on AWS does not change; it isn't required, but it is better if you intend on allowing outgoing connections.
Go back to the main dashboard display.
In "Network and Security", click on "Elastic IPs".
Select Allocate New Address (blue button on top) and then select it in the table. In actions, you will see "Associate Address". Select this then assign the address to the instance you have previously configured. Done!

Next up: Log into your machine, and immediately update everything. Use the IP provided by Amazon, or the Elastic IP if you assigned one to the instance in the last step.
type: "sudo yum update"

Now, let's get the VPN configured.
First step is to install OpenVPN. We need to install the extended package library to do this.
type: "sudo amazon-linux-extras install epel"
type: "sudo yum-config-manager --enable epel"
Now you can install OpenVPN.
type: "sudo yum install openvpn"
You will need your credential file from OpenVPN; it's a file you generate that will have a .ovpn extension. But you're going to need to upload it to the instance. You can do this through the scp command on OSX or Linux, but if you're on Windows, you'll need another utility. Get WinSCP here: https://winscp.net/eng/download.php
But we'll have to tell it where your key file is so you can login. Select "New Session", then use the same IP and username as you did to connect before. We'll need to tell it about the key file though! Select the "Advanced" tab then under the SSH section, click on "Authentication" and then select your private key file you generated in the tutorial above.
Connect and upload the .ovpn file that you generated when you added a user for the VPN. This step depends on your OpenVPN configuration - ask below if you have problems.
Next, let's verify we can connect to the VPN!
type: "openvpn --config my-configuration-file-made-by-openvpn.ovpn &"
You will be prompted for a password if you configured one.
Verify operation by pinging your LAN router, e.g.
type: "ping 192.168.2.1" or the address of the SMB server where you shared the information.

Allllrighty! Next up is getting connected to your blockchain. Create a directory where the data directory will be mounted.
type: "mkdir blockchain"
We need to install samba and some utilities to get things mounted.
type: "sudo yum install samba"
type: "sudo yum install cifs-utils"

Now let's mount the folder:
type: "sudo mount -t cifs //192.168.2.100/Bitcoin ./blockchain -o user=bitcoin,vers=2.0,uid=ec2-user,gid=ec2 user,file_mode=0777,dir_mode=0777"
Where " //192.168.2.100/Bitcoin" is the address of the SMB server and share where you put the data directory from your initial sync. If you didn't, and just want to sync everything from AWS, then make sure it's a folder where your user has access. In this case, I'm assuming you've made a SMB user with the name "Bitcoin". The command will prompt you for the password to access the share. The other bits ensure you can have read and write access to the share once it's mounted in AWS.

Now we're ready for some Bitcoin! Props to the tutorial here: https://hackernoon.com/a-complete-beginners-guide-to-installing-a-bitcoin-full-node-on-linux-2018-edition-cb8e384479ea
But I'll summarize for you:
Download and then re-upload with WinSCP, or download directly to your instance with wget, the most current Bitcoin core. In this case, it's bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz downloaded from https://bitcoin.org/en/bitcoin-core/.
Let's verify it hasn't been tampered with once you have it uploaded to the terminal:
type: "sha256sum bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz"
Then compare that with the hash value that's listed in the SHA256SUMS.asc file on bitcoin.org. In this case, "36ce9ffb375f6ee280df5a86e61038e3c475ab9dee34f6f89ea82b65a264183b" all matches up, so we know nobody has done anything evil or nefarious to the file.
Unzip the file:
type: "tar zxvf bitcoin-0.18.0-i686-pc-linux-gnu.tar.gz"
There is a warning about a symbolic link; everything seems to work OK regardless, but if anyone knows what or how to fix, please comment.
We'll need to get some missing libraries before we can run it; these aren't in the basic AMI instance.
type: "sudo yum install glibc.i686"
type: "yum install libgcc_s.so.1"

FINALLY! We are ready to launch the program. Go to the "bin" directory inside where you unzipped the Bitcoin Core tarball. (e.g. /home/ec2-useblockchain/bitcoin-0.18.0/bin)
./bitcoind -datadir=/home/ec2-useblockchain/data
You will see the program either start to sync and download, or start to read the existing blockchain file that you put in the share from before.

Congrats!

There are a couple extra steps to have it automatically start on reboot, but let's see if anyone gets this far first. I use the "screen" program to do this, but there's also a daemon mode, and some other functionality that is discussed in the hackernoon tutorial.
The primary cost will be outgoing bandwidth. AWS charges $0.10/GB beyond 15GB; You can limit the outgoing bandwidth easily according to your budget: https://bitcoin.org/en/full-node#reduce-traffic

Hope this encourages people to try running a free, or very low cost, cloud node, with a substantially reduced threat profile.
submitted by xtal_00 to Bitcoin [link] [comments]

Komodo's 2.0 Infographic Contest: 5,000 KMD Grand Prize!

Komodo's 2.0 Infographic Contest: 5,000 KMD Grand Prize!

https://preview.redd.it/0yq7rwnkjdq11.png?width=1500&format=png&auto=webp&s=950dd49d7e1f7f1e421f7074bd030aec064e6ac7
A total prize pool of 7,000 KMD in our infographic contest
Calling all creatives to take part in our infographic contest and compete for a prize of 7,000 KMD. The winning infographic will explain the architecture of Komodo Platform’s technology. Winners will be those who are able to communicate our architecture and tech visually. This contest will run primarily on Reddit, with the exception of resources being posted to Medium and a master twitter thread for submissions on Twitter. You'll find links at the bottom of this post.

Prizes for winning infographics.

Are you a creative designer? Here's what you can win…
  1. A grand prize of 5,000 KMD
  2. Two runner-up prizes of 500 KMD each
  3. Two third-place prizes of 250 KMD each

Prizes for sharing and giving feedback!

Not a designer? That's OK. You can still participate and win! We'll award five lucky winners 100 KMD each for sharing and promoting the contest. Winners will be picked in a raffle. If you'd like to take part click here https://gleam.io/MwMtO/komodos-20-infographic-contest-5000-kmd-grand-prize and share this post with your friends.

Your Goals

  • Create a high-quality infographic that illustrates the genesis of our platform, the working tech that has been created and how Komodo has been built differently, and deliberately, from the very beginning to ensure security, scalability and interoperability. This is why we refer to the architecture, because Komodo was designed to overcome common problems like congestion, governance and attacks that other platforms did not foresee or prevent, from the beginning. This is Komodo DNA.
  • Share your submission far and wide and encourage your friends and followers to vote for you.
  • Encourage feedback, ask questions and make your infographic the best that it can be.

Our Criteria to Judge

Please note that upvotes and shares are not the only criteria we'll use to judge winners. While useful, we will value creativity, good questions and discussion on Reddit highly. When sharing your posts you will score more highly if people comment, provide feedback and are engaged.
  • How well the infographic conveys our working tech, it's core concepts and plans to build on top of it.
  • How well the infographic illustrates our story, purpose and conveys our tech so that it's easy to understand.
  • Constructive discussion, questions and feedback on Reddit that lead to improvement.
  • Sentiment and comments generated across all our social media. This will not include vanity metrics like likes or shares.
  • Upvotes on Reddit for the author's submission post ONLY. All votes will be counted (i.e. doesn't matter which week they were made).
  • Retweets of the submission in our master thread ONLY. Include your handle and a cover image in your submission. This means if you promote yourself on Twitter you ought to promote the tweet with your work in it.

How do you win?

You may submit up to two infographics. By submitting an infographic, you understand Komodo may post and use your submissions on our digital channels during and after the contest. Each infographic must have it's own post.
  • Create a post on Komodo's subreddit using the 'infographic contest' flair.
  • Add the infographic image into the Reddit post.
  • Include your Twitter handle.
  • Include a social media friendly cover image for us to use when we tweet your submission out.
  • Post a link to your submission post here in the comments for all to see.

Contest Timeline Guide (these dates indicative and are subject to change).

  • 7th September. Announcement. If you're reading this on Reddit before the big announcement then well done! You have two extra days before this is announced on Friday.
  • 10th - 21st September. Research and Questions. We will promote the contest, invite questions and requests for resources, in the comments of this master Reddit post (because this means all information and good questions will be visible to all participants).
  • 22nd September. Draft Submissions. Creatives to submit their draft infographics on Reddit. All submissions need to have their own post and then be linked to in the comments of this master post. This is important to remember!
  • 24th - 30th September. Feedback. A period of one week will be devoted to promoting the submissions and asking the community and team to give you feedback.
  • 1st October. Final Submissions.
  • 2nd - 8th October. Voting. A week of promoting your work and at the end we'll count votes, consider feedback and pick our winners.
  • 15th October. Winners Declared. The final decision by judges. Votes and community feedback counts towards judging but do not have final say.

Resources

If you need help please post in this thread, or email [[email protected]](mailto:[email protected]) with ‘Infographic Contest’ in the subject line.
  1. A list of resources for the Komodo infographic contest including tools to create infographics.
  2. Komodo Platform: Redefining The Architecture Of Blockchain Platforms
  3. A bullet point study aid to help you understand the history of Komodo’s architecture.
  4. Logo Pack https://komodoplatform.com/wp-content/uploads/2018/03/Komodo-Logo-Pack.zip
  5. Mylo's notes on Software & Platform Architecture for Designers in the Infographic Contest
  6. Mylo's Conceptual Model of Architecture
  7. Video: A brief history of our working tech and an animated timeline of the Komodo Platform.
  8. Video: Komodo Atomic Swaps Explained.
Also please let us know if you are, or you know, a good GUI developer because we'd love to hear from them. Ask them to DM ca333#0118 or SHossain#8093 on Discord.

Entries and submissions for the infographic contest. You can click here to see them all in a scrollable thread on Twitter.

25/09/18 - First Round of Feedback

Infographics should use graphical design elements to visually represent the Komodo Architecture Story found here: https://komodoplatform.com/komodo-platform-a-brief-overview/ included in our ‘required reading’. There’s also a bullet point aid: https://medium.com/@benohanlon/bullet-point-aid-to-help-you-the-history-of-komodos-architecture-dced35b29965 you may find useful.
  • We want to stress that the infographic ought to focus on the Architecture story. In the first round we've found many have focused on the five pillars which is a part of it but not the focus.
  • Copy should be short and concise and not dominate the infographic. The idea is to simplify the story and not to copy and paste directly from the story.
  • Colour Palette - avoid heavy usage of the old KMD green and yellow-orange. Would prefer usage of the interim KMD colour palette.
  • Recommended fonts: Montseratt, Roboto, Open Sans, Helvetica, or Arial.
  • Graphical - Imagery should complement the associated copy. Diagrams are encouraged in place of simple icons to explain more complex technology concepts.
  • Interim KMD colour palette
Interim KMD Colour Palette
If you’ve not been included in the first round it’s because the submission hadn’t been made when the team reviewed. Don’t worry though because we’re organising hangouts and further feedback to help.
  • #001 Infographic Link // Reddit Post Link by thesudio. There’s a lot of good points made, however, these would work better if there is a clear narrative and flow to the information being presented. Otherwise, it can be overwhelming and confusing to the reader. The #1 objective is to visually depict the architecture story and how KMD is redefining blockchain platform architecture.
  • #002 Infographic Link // Reddit Post Link by thesudio. We like that there is a clear structure and clear messaging aligned to each of the 5 pillars. However, the infographic should be focused on telling the architecture story vs the pillars.
  • #003 Infographic Link // Reddit Post Link by VolsenVols. Love how you’ve incorporated our existing graphic design elements into the infographic. This is heading in the right direction and the level of copy and content are well balanced. It would be nice to align this closer to the architecture story and to expand on the different layers of our technology using the same style.
  • #004 Infographic Link // Reddit Post Link by dexter_laabo. Needs to tell the architecture story. This looks more like it took information from our current website. “Anonymous” is not a key aspect of our technology that we’re focusing on.
  • #005 Infographic Link // Reddit Post Link by savandra. The visuals are strong but the narrative could be stronger. It would be nice to align this closer to the architecture story and to expand on the different layers of our technology using the same style.
  • #006 Infographic Link // Reddit Post Link by VolsenVols. Team prefers the other submission style in entry #003.
  • #007 Infographic Link // Reddit Post Link by cryptol1. Doesn’t depict the architecture narrative. Inaccurately describes cross-chain tech as “proprietary”. Simplification has the wrong messaging associated, should be white-label focused. This is considered more of a graphics versus an infographic. Needs to be more comprehensive.
  • #008 Infographic Link // Reddit Post Link by pacosenda. We like the unique design style and approach taken. Doesn’t follow the architecture narrative. Should be expanded out as it is a bit short on content with no clear flow or narrative.
  • #009 Infographic Link // Reddit Post Link by jeanetteLine. Great level of detail and thought on the layout and content. Doesn’t, however, cover the architecture story. Would be preferred if the design direction reflects interim colour and style vs. legacy KMD. The roadmap should be avoided. Looks like they borrowed more from the website than the guidelines.
  • #010 Infographic Link // Reddit Post Link by Meyse. Very creative way to explain and layout the content. This could be expanded out more to encompass the entire architecture story. Cross-chain verifications/smart contracts, blockchain bridging need to be incorporated in.
  • #011 Infographic Link // Reddit Post Link by Brenny431. Follows the 5 pillars versus the architecture story. Would prefer stronger visuals and design elements.
  • #012 Infographic Link // Reddit Post Link by ProofDraw. Design elements are good but need to follow architecture story versus 5 pillars.
  • #013 Infographic Link // Reddit Post Link by sayonara_girl. Needs to follow the architecture story.
  • #014 Infographic Link // Reddit Post Link by Limiter02. Good thought has gone into the copy, however, there’s way too much of it. Would prefer stronger visuals and utilizing a more visual storytelling approach. Doesn’t follow the architecture story. Remove the lizard.
  • #015 Infographic Link // Reddit Post Link by piptothemoon. Great thought into visually representing key points. Needs to be expanded out to incorporate the architecture story, but this is heading in the right direction from a visual storytelling POV.
  • #016 Infographic Link // Reddit Post Link by thecryptofoundation. Love the timeline approach, and mostly followed the guidelines and architecture story. Also, like the incorporation of accomplishments at the end. Would like to get the stock imagery used to reflect our interim colour palette. Not all visuals match what is being represented in the copy.
  • #017 Infographic Link // Reddit Post Link by jsteneros. As discussed in the Zoom call, this graphic is really solid but a little heavy on the copy. Would be good to see more visualizations of the info. This graphic hits on some of the important messages (e.g. Komodo is built differently from other blockchain platforms and solves many of the issues that first-gen platforms are struggling with) but it would be great if there was more information about Komodo’s architecture and how Komodo is different from other platforms.
  • #018 Infographic Link // Reddit Post Link by gravigocrypto. This one was also discussed in the Zoom call. Outstanding visuals and overall design. The info follows the architecture story well but could be stronger if the 3 layers of Komodo’s architecture were tied together into one, coherent visual. It’s a challenging task but that’s part of the contest : )
  • #019 Infographic Link // Reddit Post Link by PacoSenda. This is a really creative infographic, which is great! However, we’d really like to see the visuals a bit more in line with fonts and color palette described above in the “First Round of Feedback” section. Also, as with the feedback for many of the infographic submissions, sticking to the Komodo architecture story would be best.
  • #020 Infographic Link // Reddit Post Link by emmanmalaman. The visuals are pretty cool but this one misses most of our core messaging. It would be much stronger if it followed the architecture story and touched on the info provided in this post. There’s definitely potential here but it needs some work.
  • #021 Infographic Link // Reddit Post Link by immimidada. The colors and visuals here are spot-on. It’s also really great that it sets up the problem and then presents the Komodo solution. However, the problem and solution aren’t defined exactly the way we’d like. Check out the architecture narrative to learn more, and try to follow that story a bit more closely.
  • #022 Infographic Link // Reddit Post Link by mohitgfx3. This one is a bit heavy on the KMD logos. We’re really hoping to see a visualization of Komodo’s infrastructure architecture. As with the feedback for many of the infographics, it would be best to re-read Komodo’s architecture story and try to stick to that as much as possible. Using images from the current website is also not a great approach, as we’re preparing to launch a new site in the coming months.
  • #023 Infographic Link // Reddit Post Link by u/sayonara_girl. Some of the visuals are cool! It’s missing the narrative we’re looking for. In general, less copy and more visual storytelling would improve this graphic a lot. We’d like to see a smooth, linear flow of information. Take another look at the architecture story and try to follow that narrative.
  • #024 Infographic Link // Reddit Post Link by brunopugens. This one follows the narrative well! But it’s a little heavy on the copy. It would be much stronger if the architecture was displayed visually, rather than explained with text. Also, the design is cool but it’s difficult to read b/c the perspective of the text is skewed. It’s a really cool idea but might be better to put the text flat for the sake of readability and clarity.

We hosted a round of live feedback sessions via Zoom. The recording is here:

https://soundcloud.com/blockchainists/zoom-call-first-round-of-feedback-for-komodos-infographic-contest#t=3:50

Timeline

The first block in the KMD blockchain was mined just under two years ago, on September 13, 2016 to 9:04 PM. Since then, Komodo has demonstrated a commitment to innovation and established a history of execution.
  • February 21, 2016 — The vision for Komodo Platform is born with jl777’s Declaration of Independence.
  • September 13, 2016 — The first block in the KMD chain is mined.
  • October 15, 2016 — Komodo’s initial coin offering (ICO) is launched.
  • November 20, 2016 — Komodo’s ICO comes to a close with a total of 2,639 BTC raised.
  • January 2017 — The Komodo Mainnet is launched, complete with independent assetchains and delayed Proof of Work security.
  • January 31, 2017 — The KMD coins purchased in the ICO are issued.
  • March 2017 — Komodo’s development team develops one of the first atomic swap protocols.
  • July 2017 — Thousands of atomic swaps are made in a public, observable setting.
  • August 2017 — Private, zero-knowledge trades made possible with Jumblr, Komodo’s native shuffler.
  • October 2017 — Komodo develops a way to make atomic swaps in SPV Mode (“Lite Mode”), thus eliminating the need for traders to download entire blockchains to do atomic swaps.
  • November 2017 — First GUI for Komodo’s atomic-swap-powered decentralized exchange (DEX) is released, making atomic swap trading more accessible than ever before.
  • January 2018 — The mobile version of Agama wallet is released.
  • February 2018 — A public stress test allows 13,900 atomic swaps in a 48 hour period.
  • March 2018Komodo bridges the gap between Bitcoin-protocol-based coins and Ethereum-based ERC-20 tokens, providing support for 95% of coins and tokens in existence.
  • March 2018 — Komodo holds its second annual Notary Node Elections.
  • May 2018 — The world’s first decentralized ICO is held on Komodo Platform.
  • June 2018 — The alpha release of HyperDEX, a new GUI for Komodo’s decentralized exchange, is launched.
  • July 2018 — Komodo enters a partnership with Netcoins, making KMD coins available for purchase with fiat currencies at over 21,000 locations across three continents.
  • July 2018 — Komodo announces the 5 Pillars of Blockchain technology and begins introducing some Komodo 2.0 technology features, like Federated Multi-Chain Syncing and Cross-Chain Smart Contracts.
  • August 2018 — Komodo takes two big steps towards mass adoption, announces a collaboration with Ideas By Nature, an industry-leading blockchain agency, and releases a full briefing on the development on UTXO-based smart contracts.

Achievements

  • Cryptomiso.com is a website that ranks 866 different blockchain projects according to the Github commit history of that project’s most popular repo. Komodo is ranked #1 overall for Github commits over the last 12 months.
  • China's Ministry Research Initiative regularly ranks Komodo in the top 10.
  • Binance CEO highlights Komodo (see this Five Bullet Friday edition for more info).

If you would like to update your post, please edit and add to the post so people can see the different iterations. Entries and submissions for the infographic contest. You can click here to see them all in a scrollable thread on Twitter.

submitted by benohanlon to komodoplatform [link] [comments]

Bitcoin core - unconfirmed transaction

Last week I posted here about making a transaction from my Bitcoin Core wallet even though the network is over 3 years out of sync, see my post here. Appreciate the advice that I didn't need to wait for the network to fully sync before making the transaction.
I sent the remaining coins to my LBC account, but after 48 hours it still remains unconfirmed. I'm aware these transactions can take a while (says up to 14 days on the LBC website) but I've researched a little bit about unconfirmed transactions and seems it's relatively common.
I'll give it some more time, but if it remains unconfirmed is there anything I can do? I've read on this post that you can "Run bitcoin core with -zapwallettxes -rescan flags" but the unconfirmed transaction will not be gone until the blockchain fully loads. As mentioned mine is out of sync by over 3 years and I don't think my shitty laptop will be able to download all of that, so is there any alternative option? Or have I misunderstood this slightly?
Appreciate any help
edit - forgot to mention I had not included a transaction fee, I didn't recall having to manually input that with transactions in the past (haven't used it in a few years), I wonder whether this is the reason it remains unconfirmed?
submitted by thedudeabides9 to BitcoinBeginners [link] [comments]

My first experience using Lightning Network

I figured it was time to see for myself just how easy or difficult it was to use LN, and no better opportunity than to troll satoshis.place with some memes. I figured if there was a light wallet (Eclair) for android, there'd be something similar for Windows or even Linux to patch through Electrum. Well, after some research, there isn't, at least that I can find. If you want to use LN on desktop, you need a full client which means you need a full Bitcoin Core node.
And apparently, if you want LN to work somewhat decently at all, you need a full client, because out of 100 or more tries to push to satoshis.place payment requests on Eclair for android, only a handful succeeded, as connection to the channel is constantly dropping off an on multiple times a minute, even with a channel opened directly to them.
So I thought I'd try the other mobile LN wallet "Bitcoin Lightning Wallet". After funding it and opening a channel with a large hub, I thought I'd be able to route straight to satoshis.place. Unfortunately no, it appears you have to open a channel directly with who you want to transact with on this one as well, and it won't even let me open a channel with SP because "Data loss protection is not provided by this peer".
Needless to say, it's pretty ridiculous in order just to have some fun on this stupid website, I'd have to spin up a Linux box, install a full Bitcoin Core wallet (yay, let me sync for a few days), then install a full LN Daemon on top if it which I'll need to keep online for as long as I have a channel open.
The user experience is no where near at the point of SPV Bitcoin wallets, it barely works at all on the "easy methods".
submitted by lechango to btc [link] [comments]

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B

Intro

This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
 
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
 
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
 
The updates
 
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
     

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

https://www.youtube.com/watch?v=Snr5e8bzftI
This video shows how long it takes to start Reddcoin Core.   TL;DR:
     

Extra

Backup
Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
 
 
   
Boot with only 1 USB drive plugged in:
Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly.   If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
   
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
   
Start Reddcoin Core easier
Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
   
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
   
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
 
   
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
   
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  
     

Credits:

   
Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

[DEVELOPMENT] Bitcoind IPV4 testnet port (18332) is failing to bind

[SOLVED] Thanks for everyone that have helped!


Hello everyone, this is a development problem that I'm currently having. Since the BTC Development sub is kind of inactive and I couldn't find any rule contraty to posting about BTC Development, I'll try my luck in here as I'm hopeless already. I've posted on BTC Stack Exchange but no answers also. Please, don't get me wrong, I'm trying to solve this problem for many days now, I've looked up everywhere for this.
I'm new to Bitcoin development and I'm currently having difficulties trying to make RPC calls from a Docker Container to a Bitcoin-Core daemon running in a SSH server. I suppose that the problem may be with Firewall or closed ports, but I also do not know much about Network settings.
I'm using nbobtc/bitcoind-php package to make the RPC calls with HTTP requests, and it is running in a Docker container. I'm sure the container is functional and is not the problem.
So here's what happening: when I run bitcoind in root user (but normal also won't work) in my SSH server, the IPV4 testnet port seems to be not opened. This message goes up when I run bitcoind:
Binding RPC on address 0.0.0.0 port 18332 failed.
Here's what my bitcoin.conf looks like (I want to use testnet in here). I'm using Bitcoin-Core "subversion": "Satoshi:0.17.1".
server=1 debug=net txindex=1 testnet=1 rpcuser=userb rpcpassword=test test.rpcport=18332 # I've already tried allowing the IP these 3 ways: # rpcallowip=192.168.xx.xx # My machine's IP # rpcallowip=172.19.x.x/xx # Docker's NBOBTC container IP # rpcallowip=0.0.0.0/0 # Allowing all IP datadir=/home/bitcoin-dev/.bitcoin debuglogfile=/home/bitcoin-dev/.bitcoin/debug.log 
Here's what appears in debug.log right after I run Bitcoind:
2019-05-06T14:43:10Z Bitcoin Core version v0.17.1 (release build) 2019-05-06T14:43:10Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2019-05-06T14:43:10Z Assuming ancestors of block 0000000000000037a8cd3e06cd5edbfe9dd1dbcc5dacab279376ef7cfc2b4c75 have valid signatures. 2019-05-06T14:43:10Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000007dbe94253893cbd463 2019-05-06T14:43:10Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation 2019-05-06T14:43:10Z Default data directory /root/.bitcoin 2019-05-06T14:43:10Z Using data directory /home/bitcoin-dev/.bitcoin/testnet3 2019-05-06T14:43:10Z Using config file /home/bitcoin-dev/.bitcoin/bitcoin.conf 2019-05-06T14:43:10Z Using at most 125 automatic connections (1024 file descriptors available) 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 4 threads for script verification 2019-05-06T14:43:10Z scheduler thread start 2019-05-06T14:43:10Z Binding RPC on address 0.0.0.0 port 18332 failed. 2019-05-06T14:43:10Z HTTP: creating work queue of depth 16 2019-05-06T14:43:10Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-05-06T14:43:10Z HTTP: starting 4 worker threads 2019-05-06T14:43:10Z Using wallet directory /home/bitcoin-dev/.bitcoin/testnet3/wallets 2019-05-06T14:43:10Z init message: Verifying wallet(s)... 2019-05-06T14:43:10Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-05-06T14:43:10Z Using wallet wallet.dat 2019-05-06T14:43:10Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin-dev/.bitcoin/testnet3/wallets/database ErrorFile=/home/bitcoin-dev/.bitcoin/testnet3/wallets/db.log 2019-05-06T14:43:10Z net: setting try another outbound peer=false 2019-05-06T14:43:10Z Cache configuration: 2019-05-06T14:43:10Z * Using 2.0MiB for block index database 2019-05-06T14:43:10Z * Using 56.0MiB for transaction index database 2019-05-06T14:43:10Z * Using 8.0MiB for chain state database 2019-05-06T14:43:10Z * Using 384.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2019-05-06T14:43:10Z init message: Loading block index... 2019-05-06T14:43:10Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/blocks/index 2019-05-06T14:43:10Z Opened LevelDB successfully 2019-05-06T14:43:10Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/blocks/index: 0000000000000000 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file = 161 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=755, size=30875345, heights=1513309...1514061, time=2019-04-29...2019-05-03) 2019-05-06T14:43:19Z Checking all blk files are present... 2019-05-06T14:43:20Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/chainstate 2019-05-06T14:43:20Z Opened LevelDB successfully 2019-05-06T14:43:20Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/chainstate: 2686d59caeb1917c 2019-05-06T14:43:20Z Loaded best chain: hashBestChain=00000000b3b6a5db140b6058b7abe5cb00d8af61afd2a237ae3468cd36e387fa height=927391 date=2016-09-08T15:04:00Z progress=0.311180 2019-05-06T14:43:20Z init message: Rewinding blocks... 2019-05-06T14:43:29Z init message: Verifying blocks... 2019-05-06T14:43:29Z Verifying last 6 blocks at level 3 2019-05-06T14:43:29Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE]. 2019-05-06T14:43:29Z No coin database inconsistencies in last 6 blocks (500 transactions) 2019-05-06T14:43:29Z block index 19450ms 2019-05-06T14:43:29Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex 2019-05-06T14:43:30Z Opened LevelDB successfully 2019-05-06T14:43:30Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex: 0000000000000000 2019-05-06T14:43:30Z init message: Loading wallet... 2019-05-06T14:43:30Z txindex thread start 2019-05-06T14:43:30Z [default wallet] nFileVersion = 170100 2019-05-06T14:43:30Z [default wallet] Keys: 2005 plaintext, 0 encrypted, 2005 w/ metadata, 2005 total. Unknown wallet records: 1 2019-05-06T14:43:30Z Syncing txindex with block chain from height 694205 2019-05-06T14:43:30Z [default wallet] Wallet completed loading in 123ms 2019-05-06T14:43:30Z [default wallet] setKeyPool.size() = 2000 2019-05-06T14:43:30Z [default wallet] mapWallet.size() = 7 2019-05-06T14:43:30Z [default wallet] mapAddressBook.size() = 4 2019-05-06T14:43:30Z mapBlockIndex.size() = 1515581 2019-05-06T14:43:30Z nBestHeight = 927391 2019-05-06T14:43:30Z torcontrol thread start 2019-05-06T14:43:30Z Bound to [::]:18333 2019-05-06T14:43:30Z Bound to 0.0.0.0:18333 2019-05-06T14:43:30Z init message: Loading P2P addresses... 2019-05-06T14:43:30Z Loaded 10420 addresses from peers.dat 36ms 2019-05-06T14:43:30Z init message: Loading banlist... 2019-05-06T14:43:30Z Loaded 0 banned node ips/subnets from banlist.dat 29ms 2019-05-06T14:43:30Z init message: Starting network threads... 2019-05-06T14:43:30Z net thread start 2019-05-06T14:43:30Z dnsseed thread start 2019-05-06T14:43:30Z addcon thread start 2019-05-06T14:43:30Z msghand thread start 2019-05-06T14:43:30Z init message: Done loading 2019-05-06T14:43:30Z opencon thread start 
After all that appears above, there are just "UpdateTip", "Requesting block", "received block" and "getdata" messages. (so the P2P port, 18333, works).

And here is when I netstat:

sudo netstat -nap|grep bitcoin|grep LISTEN
tcp 0 0 0.0.0.0:18333 0.0.0.0:* LISTEN 31185/bitcoind tcp6 0 0 :::18332 :::* LISTEN 31185/bitcoind tcp6 0 0 :::18333 :::* LISTEN 31185/bitcoind 
Thank you in advance!

PS: A few days ago I could make it work when running bitcoind with root user, but now even that won't solve the problem.
submitted by VicPietro to Bitcoin [link] [comments]

Digibyte core wallet sync problem fixed Full Bitcoin Sync in 2 hours 46 minutes with Agama Wallet ... How to Secure & Backup Your Bitcoin or Other Crypto Wallets Increase slow download and sync of bitcoin blockchain on Mac TUTORIAL - How to fix SYNC error / correctly SYNC Electra Wallet

i've been trough 10+ days of syncing the Bitcoin Core and again mSigna wallet with Core... downloaded bootstrap, then building blocks for Core to get synced was relatively fast, but mSigna has to build blocks for itself all over again while synced Core has to be running in the background. Its taking ageeees! way slower than the Core, especially last 100.000 blocks.) And the 1.8 BTC are waiting ... Bitcoin Core is a full Bitcoin client and builds the backbone of the network. It offers high levels of security, privacy, and stability. However, it has fewer features and it takes a lot of space and memory. Features: Bech32 × Bech32: Bech32 is a special address format made possible by SegWit (see the feature description for SegWit for more info). This address format is also known as 'bc1 ... Bitcoin, Dash, Litecoin and every Altcoins has its own core wallet. While the looks of each and every wallet may vary slightly its functionalities remain the same. Whenever you open your QT wallet the first thing your wallet does is; it starts scanning all the recent blocks on the blockchain and tries to catch up with the network. Whether your wallet is a fresh install or you’ve been using ... The wallet will always say out of sync the first time you open it, as it has to download the blockchain. This process can take up to 4 hours or so depending on your internet speed and number of connections to our network, so please be patient. Bitcoin clients with the exception of SPV clients like Multibit need to download the entire blockchain history before consolidating the wallet. Currently the blockchain size is around 22 Gb and increasing. The time it takes for your client to sync will depend on your internet connection. Also if you do not keep your client connected, the next ...

[index] [47762] [31760] [17299] [34876] [46804] [23961] [14756] [14399] [49102] [12993]

Digibyte core wallet sync problem fixed

Digibyte core wallet sync problem is now fixed and the daily payments are going through better than ever. Get FREE coins at jmlbusinesspro.com How to Video and Marketing Tutorials By Jose Nunes ... Find out why Close. Increase slow download and sync of bitcoin blockchain on Mac Daniel's Tutorials ... Getting your Private Keys from the Bitcoin Core wallet - Duration: 5:11. Bitcoin Daytrader ... LEGGIMI READ ME Tutorial - How to correclty sync Electra Wallet / fix sync problem All link: Electra.conf Download: https://goo.gl/LeV5m6 ... How to mine bitcoins (solo mining) with the core client! (*solo mining now removed from client*) - Duration: 1:00. Bitcoin Blaster 49,301 views I made this video showing how I backup and secure my bitcoin and other crypto wallets. Donations Gratefully Accepted, Thank you BTC / SJCX / XCP ...

#