SoftTouch integrates bitcoin acceptance into POS | QSRweb

Reddcoin (#RDD) May 2020 Team Update, or “New Wallets & What to Expect when You’re Expecting PoSV v2”

Link to Medium post -> https://medium.com/@techadept/reddcoin-rdd-may-2020-team-update-or-what-to-expect-when-youre-expecting-posv-v2-b708319221ce?sk=b5eafc57b67327d99a35380f390d77ca
Hey, ReddHeads!
To new ReddHeads, welcome! To old ReddHeads, welcome back! It’s an exciting time in Reddcoin (RDD) for a lot of reasons, and we, the Reddcoin Core development team, wanted to get a brief update out to touch base on some of the highlights.
Attached are some screenshots of our work to enhance security and interoperability, and to extend support to MacOS Catalina in our newest v3.10.1 wallet.
This wallet release also includes components and performance & security upgrades taken from the Bitcoin 0.10 codebase, and we will be following much of that same development and enhancement in our Reddcoin Core wallet in the future, with 0.11 up next.
This release is not a required upgrade (except for Catalina users), but will benefit user experience and security significantly. We’ll be publishing, of course, a full public changelog, hashes and commit list in Github along with open source code and compiled executables upon release.
But the major changes in Reddcoin v3 are just about to start, as PoSV v2 gets ready to activate. Released to the community on 12/24/19, the blockchain has (at time of writing) reached 8197 of the required 9000 block threshold, or 91.08% of our goal of supermajority. If you haven’t upgraded yet, or aren’t staking, it’s time.
After PoSV v2 activation, older (v2.x, v1.x) wallets will not be able to send transactions or stake.
We anticipate activation to be reached within a very short time period, especially once our Mac ReddHeads are able to participate, and as such we want to ensure that information for the general community is available and up to date.
1) AM I GOING TO LOSE MY REDDCOIN (RDD)??
a. NO. This is a soft-fork, and whether you’ve upgraded to a v3 wallet or not, you cannot lose your coins. The blockchain itself will remain the same, it is only the rules of staking that are changing. Older wallets WILL stop functioning immediately after the threshold is passed and PoSV v2 activates, but all that is required at that point to restore functionality is to install the new v3 wallet. If you need help, please join our Telegram or Discord live chats for community or Dev help directly. No ReddHead left behind!
2) WHAT DO I NEED TO DO??
a. If you’re staking, make sure you’re using a v3 wallet, preferably the latest version. Right now, that is v3.0.1, in a few days with the above noted release it will be v3.10.1. You may also wish to use the “Backup…” function at this time to make sure you have a backup of the only important file you need, the “wallet.dat” file. There are no mobile staking options at this time due to the nature of our PoSV protocol, but you can deposit coins in the dev team-run ReddBot on Telegram to stake if you have no other options until a mobile staking option is made available.
b. If you’re not staking, or are holding on Coinomi, or Guarda, or other 3rd party wallets, or on an exchange, or a paper wallet, you will also have no operational issues, but of course you’re encouraged to help secure the network and validate transactions, by starting to stake.
3) I’M BORED. ENTERTAIN ME!
a. OK. As successful as our first meetup was, we agree. Look for an upcoming benefit concert from Reddcoin and hopscotchmafiamusic.com at the end of this month. No, really. Free awesome music, cool people, come have a bit of fun with the ReddHead community virtually!
4) I’M HUNGRY. FEED ME!
a. Well…with the activation of PoSV v2, and the creation of Reddcoin’s self- funded development mechanism, we’re very excited to be able to provide at least some resources and RDD toward the Reddcoin Community Food & Supply Bank initiative in the near future. Reddcoin Core will also be donating any funds received in connection with the above concert event to worthy and working charities, especially if we can convince them to receive RDD (or BTC). Watch for further info about this and other charity initiatives to come. Our own efforts rely on PoSV v2 activation, but will be documented publicly and transparently as they evolve.
5) I WAS USING RDD AND THEN X (or Y or Z) HAPPENED AND NOW I’M BROKE AND SAD AND ANGRY. HELP ME!
a. Perhaps you’ve not heard about Reddcoin’s uniquely conceived “Reddcoin Restitution Fund”. Been hacked? Lost a few coins when your computer crashed or your brother formatted your hard drive? Reddcoin has committed a percentage of PoSV v2 funding to give back to users legitimately affected by events beyond their control.
Cases of extreme stupidity will be vetted on a case by case basis, obviously fraudulent claims will be laughed at, and all cases will be dependent on a reasonable standard of proof and verification. This is also going to be an evolving and good faith approach to giving back to our real ReddHead community, and will require both transparency and abuse-prevention to be successful, but we look forward to being able to help those who deserve and need it. NOTE: Trading and speculative losses aren’t covered in any of this. Obviously.
6) I WANT TO KNOW MORE!
We’re working right now to rebuild our main website www.reddcoin.com into a more informative and resource-rich site, but it’s a good starting point. We are in the process of updating our roadmap to cover the end of 2020 and the future as well, and both of those should be available and will be announced within the next month.
a. www.medium.com/@techadept
b. www.reddcoin.com/reddpaper and https://reddcoin.com/reddpaper-faq/
c. www.twitter.com/@reddcoin
d. www.reddit.com/reddcoin
e. https://t.me/ReddcoinOfficial (Telegram chat)
g. https://www.facebook.com/reddcoin
7) IS TECHADEPT DRINKING WHILE WRITING THIS UPDATE??
a. Yes. Macallan. Fight me.
submitted by TechAdept to reddCoin [link] [comments]

Reddcoin (#RDD) May 2020 Team Update, or “New Wallets & What to Expect when You’re Expecting PoSV v2”

Link to Medium post -> https://medium.com/@techadept/reddcoin-rdd-may-2020-team-update-or-what-to-expect-when-youre-expecting-posv-v2-b708319221ce?sk=b5eafc57b67327d99a35380f390d77ca
Hey, ReddHeads and Crypto Fans!!
To new ReddHeads, welcome! To old ReddHeads, welcome back! It’s an exciting time in Reddcoin (RDD) for a lot of reasons, and we, the Reddcoin Core development team, wanted to get a brief update out to touch base on some of the highlights.
Attached are some screenshots of our work to enhance security and interoperability, and to extend support to MacOS Catalina in our newest v3.10.1 wallet.
This wallet release also includes components and performance & security upgrades taken from the Bitcoin 0.10 codebase, and we will be following much of that same development and enhancement in our Reddcoin Core wallet in the future, with 0.11 up next.
This release is not a required upgrade (except for Catalina users), but will benefit user experience and security significantly. We’ll be publishing, of course, a full public changelog, hashes and commit list in Github along with open source code and compiled executables upon release.
But the major changes in Reddcoin v3 are just about to start, as PoSV v2 gets ready to activate. Released to the community on 12/24/19, the blockchain has (at time of writing) reached 8197 of the required 9000 block threshold, or 91.08% of our goal of supermajority. If you haven’t upgraded yet, or aren’t staking, it’s time.
After PoSV v2 activation, older (v2.x, v1.x) wallets will not be able to send transactions or stake.
We anticipate activation to be reached within a very short time period, especially once our Mac ReddHeads are able to participate, and as such we want to ensure that information for the general community is available and up to date.
1) AM I GOING TO LOSE MY REDDCOIN (RDD)??
a. NO. This is a soft-fork, and whether you’ve upgraded to a v3 wallet or not, you cannot lose your coins. The blockchain itself will remain the same, it is only the rules of staking that are changing. Older wallets WILL stop functioning immediately after the threshold is passed and PoSV v2 activates, but all that is required at that point to restore functionality is to install the new v3 wallet. If you need help, please join our Telegram or Discord live chats for community or Dev help directly. No ReddHead left behind!
2) WHAT DO I NEED TO DO??
a. If you’re staking, make sure you’re using a v3 wallet, preferably the latest version. Right now, that is v3.0.1, in a few days with the above noted release it will be v3.10.1. You may also wish to use the “Backup…” function at this time to make sure you have a backup of the only important file you need, the “wallet.dat” file. There are no mobile staking options at this time due to the nature of our PoSV protocol, but you can deposit coins in the dev team-run ReddBot on Telegram to stake if you have no other options until a mobile staking option is made available.
b. If you’re not staking, or are holding on Coinomi, or Guarda, or other 3rd party wallets, or on an exchange, or a paper wallet, you will also have no operational issues, but of course you’re encouraged to help secure the network and validate transactions, by starting to stake.
3) I’M BORED. ENTERTAIN ME!
a. OK. As successful as our first meetup was, we agree. Look for an upcoming benefit concert from Reddcoin and hopscotchmafiamusic.com at the end of this month. No, really. Free awesome music, cool people, come have a bit of fun with the ReddHead community virtually!
4) I’M HUNGRY. FEED ME!
a. Well…with the activation of PoSV v2, and the creation of Reddcoin’s self- funded development mechanism, we’re very excited to be able to provide at least some resources and RDD toward the Reddcoin Community Food & Supply Bank initiative in the near future. Reddcoin Core will also be donating any funds received in connection with the above concert event to worthy and working charities, especially if we can convince them to receive RDD (or BTC). Watch for further info about this and other charity initiatives to come. Our own efforts rely on PoSV v2 activation, but will be documented publicly and transparently as they evolve.
5) I WAS USING RDD AND THEN X (or Y or Z) HAPPENED AND NOW I’M BROKE AND SAD AND ANGRY. HELP ME!
a. Perhaps you’ve not heard about Reddcoin’s uniquely conceived “Reddcoin Restitution Fund”. Been hacked? Lost a few coins when your computer crashed or your brother formatted your hard drive? Reddcoin has committed a percentage of PoSV v2 funding to give back to users legitimately affected by events beyond their control.
Cases of extreme stupidity will be vetted on a case by case basis, obviously fraudulent claims will be laughed at, and all cases will be dependent on a reasonable standard of proof and verification. This is also going to be an evolving and good faith approach to giving back to our real ReddHead community, and will require both transparency and abuse-prevention to be successful, but we look forward to being able to help those who deserve and need it. NOTE: Trading and speculative losses aren’t covered in any of this. Obviously.
6) I WANT TO KNOW MORE!
We’re working right now to rebuild our main website www.reddcoin.com into a more informative and resource-rich site, but it’s a good starting point. We are in the process of updating our roadmap to cover the end of 2020 and the future as well, and both of those should be available and will be announced within the next month.
a. www.medium.com/@techadept
b. www.reddcoin.com/reddpaper and https://reddcoin.com/reddpaper-faq/
c. www.twitter.com/@reddcoin
d. www.reddit.com/reddcoin
e. https://www.facebook.com/reddcoin
7) IS TECHADEPT DRINKING WHILE WRITING THIS UPDATE??
a. Yes. Macallan. Fight me.
submitted by TechAdept to CryptoCurrency [link] [comments]

Since the year and #BitcoinBowl campaign are over I wanted to share my "year end" summary of Bitcoin in 2014

I'm Tony Sakich from BitPay and I have been an active member of the community for a while, but I decided it's time that I increase my presence publicly so I wanted to give my opinion (not BitPay's) about what happened this year.
Also please follow me on Twitter @TonySwish
Bitcoin in 2014: - The biggest story in mainstream media is that the price drop meant it was a bad investment, I think it was a result of the "get rich quick" crowd slowly abandoning bitcoin. This isn't good or bad, it's just another step in the growth. This isn't the biggest story in the bitcoin industry though.
2015 PREDICTION: My sole prediction of 2015 is that I will do everything I can to be a bigger voice in this community. I tend to only make predictions I can control.
Edit: Clarified my stance on altcoins as some redditors rightfully called me out.
submitted by TonySBitPay to Bitcoin [link] [comments]

BitTorrent inventor Bram Cohen on medium.com argues *against* a "simplistic plan" for scaling Bitcoin with "popular support" among "people who don't know any better" and want a "simple fix". He favors "people doing actual development who aren’t particularly good at talking". Here's why he's wrong.

TL;DR:
https://medium.com/@bramcohen/whiny-ragequitting-cab164b1e88#.3svog9gfg
Sorry Bram, but part of "real engineering work" often involves actually interacting with real users to solve their real problems, as quickly and as simply as possible (or as you prefer to dismissively put it in your essay: "people who don’t know any better" who are looking for a "simple fix").
This is why Bitcoin Classic is rapidly gaining consensus among major Bitcoin stakeholders, who are rejecting the needlessly slow & complicated roadmap from Core / Blockstream devs - who, as you yourself admit in your essay, "aren’t particularly good at talking" (or listening, for that matter).
Experience on successful real projects in the real world has shown us (with Satoshi's initial release of Bitcoin being a case in point) that the fastest, simplest and most popular solutions are actually often the best.
In the above essay, Bram Cohen, inventor of BitTorrent, makes the following arguments:
Mike Hearn, Jeff Garzik, and Gavin Andresen ... are doing a good job of whipping up popular support ...
They have a simplistic plan which appeals to people who don’t know any better or want to be told that technical problems can be made to magically go away with a simple fix.
On the other side are the people doing actual development, who aren’t particularly good at talking to the press or whipping up support on reddit and have a plan which requires real engineering work moving forwards.
There are several things seriously wrong with the Bram Cohen's central argument above:
(1) The first part of his statement above is obsolete and hence irrelevant.
Mike and Gavin did indeed previously support BIP 101 (smoothly scaling from 8 MB to 8 GB max blocksize by doubling every 2 years for 20 years) - but in the past week, things have changed dramatically, and the community has moved on:
  • Mike is gone, and it's become clear that support for BIP 101 / XT has dried up;
  • Gavin and Jeff support Bitcoin Classic, which is not BIP 101.
So Bram's comparison of Core's current roadmap with a deprecated roadmap (BIP 101) is now irrelevant.
All the buzz is around a recent new competing repo: Bitcoin Classic.
(2) The second part of Bram's statement above is wrong because it is precisely the simplicity and "appealingness" of Bitcoin Classic which are its strengths.
He dismisses those factors as if they were bad things - but they're actually good things.
The main reason for the past year of impasse is that all previously proposed solutions weren't simple and appealing enough to gain any actual consensus (among the actual users themselves - I don't mean among the devs at a single, out-of-touch and ultimately replaceable team: Core / Blockstream).
Bitcoin Classic's only initial change is to do an immediate bump to merely 2 MB - while also providing, long-term, a more democratic, transparent means of governance - based not on Core / Blockstream devs ACKing and NACKing pull-requests on the GitHub repo - but rather on a much more inclusive and deliberative multi-phase process.
The fact of being simple and inclusive (which Bram erroneously dismisses as being "simplistic" and "popular" by which he presumably means "populist") is precisely why Bitcoin Classic has been rapidly gaining consensus among all stakeholders in the Bitcoin community: miners, users, devs and businesses:
https://np.reddit.com/btc/comments/40rwoo/block_size_consensus_infographic_consensus_is/
https://np.reddit.com/btc/comments/4089aj/im_working_on_a_project_called_bitcoin_classic_to/
Bram can talk all he wants on medium.com about what might have been, and about how his favorite dev team knows better than actual users (who he insultingly dismisses as "people who don't know any better").
But figuring out how to safely and quickly and simply scale Bitcoin (which is the main issue right now) might not be the exclusive province of C/C++ devs who code in isolation all day.
In fact, as we are now seeing, it turns out that there are other stakeholders in the Bitcoin space who might actually have better ideas on how to do this kind of scaling.
So it's wrong (as well as being elitist) for Bram to dismissively insult such stakeholders as "people who don't know any better" - particularly because in many cases, what we're actually talking about here are major companies with annual revenues in the millions of dollars, with qualified dev teams of their own.
To take just one obvious example: look at Coinbase. They were banned from /Bitcoin and bitcoin.org by Theymos for daring to announce that they were testing XT - in order to serve better serve their users under all possible scenarios in the future.
Coinbase, as we know, also happens to be one of the major on-ramps for many new Bitcoin users, since they're a major US-registered financial institution.
And Coinbase also happens to have the technical and engineering expertise to have written their own open-source fully-validating Bitcoin node from scratch based on Ruby and PostgreSQL.
This is kind of Bitcoin stakeholders that Bram is insulting and dismissing when he talks about "people who don't know any better": a company which basically produced a clone of the full-node part of Core. And note that Coinbase wrote this from scratch in different langauges (Ruby and PostgreSQL), instead of inheriting (some would say "hijacking") Satoshi's orignal C/C++ codebase.
So Bram is simply being rude and mean when he dismisses a major company like Coinbase as being merely "people who don't know any better". Bitcoin expertise is not confined to Core / Blockstream devs.
In fact, there is new breed of Bitcoin experts emerging now - people who know more about the challenges Bitcoin faces today (eg, scaling and network topology) rather than the challenges Bitcoin faced in the past (eg, hasing and crypto).
Two names are worth mentioning among this new wave of experts:
  • Dr Peter R. Rizun - who has also joined Bitcoin Classic now - and who has been terribly maligned and censored by Core / Blockstream:
Dr Peter R. Rizun, managing editor of the first peer-reviewed cryptocurrency journal, is an important Bitcoin researcher. He has also been attacked and censored for months by Core / Blockstream / Theymos. Now, he has now been suspended (from all subreddits) by some Reddit admin(s). Why?
https://np.reddit.com/btc/comments/4095lb/dr_peter_r_rizun_managing_editor_of_the_first/
  • Cornell researcher Emin Gün Sirer
Miners produce a generic COMMODITY: transactions included in blocks on the chain. If certain miners refuse to produce ENOUGH of this commodity, then they CAN and WILL be REPLACED. (Important reminders from Cornell researcher Emin Gün Sirer)
https://np.reddit.com/btc/comments/411yz7/miners_produce_a_generic_commodity_transactions/
Look, I really like the stuff that Pieter Wuille is doing with SegWit - and I also really like the stuff that Greg Maxwell could contribute with Confidential Transactions (but please just ignore the few posters in this search-link who worry that CT is "dangerous" because quantum computing might come along someday.). (Although I think that any such major upgrades should be done as a hard-fork, which is more explicit and thus safer than a soft-fork).
So there is room for many types of devs in Bitcoin, and there is exciting work to be done long-term.
But Bram's essay is really about scaling now. And Core / Blockstream has not provided any solutions available now, nor have they researched what users really want and need now.
Thus it's understandable that users are gravitating towards a new dev team which can deliver a "simple fix" - in this case, Bitcoin Classic. And that's normal and healthy.
(3) Finally, there's plenty of owners of major multi-million-dollar mining operations who Bram also dismisses as "people who don’t know any better", people who believe in "magic" or a "simple fix".
At the same time, Bram inexplicably praises a bunch of devs who - as he himself admits - "aren't particularly good at talking" or "whipping up support" - while ignoring the fact that it is is precisely this lack of communication skills which got us into this whole mess. Core / Blockstream are screwing up the short-term and long-term project management of Bitcoin, because they have shown that they are totally incapable of coming up with a realistic roadmap which the community could actually support. (They may have their own reasons for the strange way they prioritized their roadmap, but we don't really know - there's lots of theories out there.)
On the other hand, the people behind Bitcoin Classic (not mentioned by Bram here, as he focuses instead on the obsolete strawman of Mike Hearn / BIP 101), have proven themselves to be "particularly good at talking" (and more important: listening) to actual users and major businesses, in order figure out a a safe, reasonable and practical "simple fix" to satisfy users' needs and requirements now.
Specifically, jtoomim (founder of Bitcoin Classic) has done extensive research, interacting with miners all over the world - on both sides of the Great Firewall of China.
As it turns out (and as stated by Gavin, another lead dev on Bitcoin Classic) the Great Firewall of China, and the concentration of so much mining on the "other" side of it, is one of the main obstacles to simple "blocksize-based" scaling solutions.
So Gavin previously experimented with 20 MB blocks, and more recently jtoomim experimented with 2-3 MB - in the field - producing empirical evidence that 2-3 MB blocks are feasible and acceptable to miners now.
This is the very definition of a "simple fix", with massive "support" from the people who matter: the miners themselves.
And this kind of research with users in the field is exactly what Bitcoin needs now - despite the fact that it might not a sexy enough engineering-based solution to satisfy Bram Cohen and the out-of-touch devs at Core / Blockstream, who have proven themselves time and time again to be unable and/or unwilling to do deliver a simple, popular scaling solution.
So by isolating themselves in their bubble of censorship to focus on elegant engineering, and avoiding the messy public forums where open debate actually occurs - and openly scorning their users (Greg Maxwell calling /btc a "cesspool" and more recently supporting Luke-Jr's attempt to sabotage Bitcoin Classic by injecting a poison-pill pull request to change the PoW and kick all miners off the network, Peter Todd releasing RBF over massive protests and recently doing a gray-hat double-spend against major US-registered Bitcoin financial processor Coinbase) - Core / Blockstream have shown themselves to be arrogant and out of touch, and have alienated the Bitcoin community by being willing jeopardize the network as they chant their mantra that "there's no emergency yet".
This is people are rejecting Core / Blockstream's so-called "scaling" roadmap (which unfortunately includes no "simple fix" - ie a minimal blocksize-based solution acceptable to the community - and instead relies on complicated, untested, fancy code such as SegWit and LN - which be might good later but which aren't ready now).
It's too little and too late, too slow and too complicated (and possibly vaporware).
Instead, people want the simpler, faster and field-tested solutions researched and developed by the devs over at the new repo: Bitcoin Classic.
Bram Cohen is needlessly focusing in his essay on what used-to-be and what might-have-been and what could-be-someday.
Meanwhile the researchers and developers at Bitcoin Classic, like Gavin and JToomim, have been focusing on the here-and-now.
In this sense, the Bitcoin Classic researchers and developers are closer to Satoshi, with his preference for practical solutions which work "good enough" to be implemented now, instead of "perfect" solutions which are so complicated that they might never get implemented at all.
Also recall that several major Core / Blockstream devs didn't believe Bitcoin would work:
  • Gregory Maxwell "mathematically proved" that Bitcoin would be "impossible" (ignoring a little thing like "complexity" - which shows that he might not be that well-rounded, since many mathematicians are indeed familiar with "complexity theory", involving termination, NP, and all that fun stuff).
  • Adam Back missed out on being an earlier adopter of Bitcoin even when tipped off by Satoshi (Adam had invented an earlier prototype called HashCash, but in his case he ignored how inflation might work - which shows that he also might not be that well-rounded, since many economists in the real world do indeed know how currency inflation works).
  • Peter Todd is an odd case, focusing on breaking things that aren't broken in order to petulantly prove a point (so he might be good in Testing or Threat Assessment, but he's probably not the kind of guy you want in Project Management).
These are the kinds of people Bram is arguing we should to support - people whose track record of being right on Bitcoin has been spotty at best, often because they're more interested in spending ages solving complicated engineering problems rather than in providing "simple fixes" for real users in the real world.
Meanwhile, guys like Gavin, JGarzik, and JToomim - all of whom are involved with Bitcoin Classic - are operating more in the spirit of Satoshi - they've been working closely with real users in the real world, figuring out what they really need and want and getting ready to actually deliver it, soon - which is why consensus among users, miners, devs and businesses has been rapidly coalescing around the new competing repo Bitcoin Classic.
submitted by ydtm to btc [link] [comments]

Ethereum Research Directions

Hello potential research collaborator! Rumour has it that you, a researcher or manager of researchers, are interested in joint research with the Ethereum Foundation. Below are the primary topics the Foundation will be thinking about for the next 2-3 years. If you, like us, enjoy the prospect of thinking about one or more of these topics for the majority of your waking hours, do get in touch. The Foundation does have money to pay the salaries/stipend of those undertaking high-value research.
We have topics in both pure research and applied research. The Foundation as well as the larger Ethereum community seek help on both. Typical outputs from researchers are: peer-reviewed academic papers, technical reports, and/or implementations (prototypes as well as production-ready).
Questions in Fundamental Research Q1: Can we create a theory of cryptoeconomic mechanisms? There are certain patterns that are often used in cryptoeconomic mechanisms. These can be studied in the abstract independently of any specific use case. Security deposits (see also proof of stake) How do we model capital lockup costs? Dual-use of security deposits Challenge-response games (one group of actors is given the opportunity to submit evidence that fact X is false, and if no one submits evidence within some period of time, then X is assumed to be true). See also challenge-response authentication. Channels State channels How do we minimize the vulnerability of challenge-response games and channels to liveness or censorship faults of the underlying blockchain? Escalation games Cross-chain interoperability (see the R3 interoperability paper ) Relays Hash timelock atomic swaps Q2: What is the role of cryptoeconomics in distributed systems? What is the role of economics in cryptography? Can we formalize how algorithmic incentives (“cryptoeconomics”) can enhance information security?
Modeling behavior of participants in mechanisms
Simple (crash) faults Byzantine faults (arbitrary) Byzantine-Altruistic-Rational (BAR) model Uncoordinated majority (e.g., as in selfish mining) Coordinated choice Bribing attacker (as in P+epsilon attacks or iceman) Behavioral economics models (prospect theory, endowment effect, loss aversion, morality, etc.) Complex game-theoretic interactions
Blackmail Quantifying cooperative interactions among agents (e.g. dynamic coalition formation) Evolution and enforcements of group norms Q3: How do distributed systems influence current economics? On net, when and how much does decentralization lower transaction costs? No obvious answer. Decentralization _decreases_transaction costs because of: Reduced number of counterparties and reduced need for building trust Yet decentralization increases transaction costs because of: increased technical overhead, Decreased usability, increased responsibility. Are Transaction costs = transaction fees + coordination costs? Q4: Within game-theory, can we quantify coordination costs? for players running a particular protocol for players executing a particular strategy Q5: What are ways we can manipulate (e.g., guarantee/minimize) coordination costs? For example, we can reduce risk by increasing coordination costs. Coordination costs are costs from multiple-agents coordinating. For example: Discovering potential peers, agreeing on computing coalition strategies, synchronization required for execution, costs of proving to the coalition that players followed coalition strategies, cost of getting rid of individual incentives to deviate Q6: What protocols have better fault attribution? A protocol fault is uniquely attributable if there is evidence that could be used to umambiguously convince any observer which actor caused the protocol fault. If a fault is non-uniquely-attributable, the blame for the fault can often at least be narrowed down to within N specific actors.
Fault attributability in various consensus algorithms
Chain-based (synchronous) consensus Partially synchronous consensus (see minimal slashing conditions) Common coins in asynchronous consensus Attributability of censorship or liveness faults.
Translating fault attributions into penalties
Shapley values Q7: What are decentralization’s fundamental limits? Building on hundreds of impossibility results. E.g., 1 and 2, or even fundamental limits from other areas of computer science.
What centralized protocols can be decentralized (while preserving guarantees)? At what cost in protocol overhead? Are there limits to scalability? For Bitcoin: On Scaling Decentralized Blockchains Only because of the requirement for shared state? At what cost in incentivization? What are the limits to incentivization? Limits to attribution Limits to mechanism budgets With how much security (against coordinated choice, trusted majority required)? Limits to fault tolerance e.g. in objective protocols and subjective protocols Objectives in Applied Research Also knows as Pasteur’s Quadrant.
Right now our primary topics in applied research are: plasma, sharding, and Casper.
  1. Base Layer (core protocols) 1.1 Plasma and Sharding [49%] Goal: Allow Ethereum transaction capacity to scale to better than linear with computational capacity of the n nodes.
Sharding FAQ
Stateless clients
State channels
Plasma implementation
Data availability proofs [65%]
A note on data availability and erasure coding Effective state-space partitioning / Cross-shard communication [15%]
Vitalik’s R3 paper, particularly Section “scalability” (p20-30). The whole paper also has a three-page executive summary. High-Level-Languages [20%]
Topic: Developing a language that knows to send the cross-shard asynchronous messages whenever contracts are located on different shards. Topic: Applying prior theory from multicore CPUs/parallel threading to sharding.
1.2 Proof of Stake [70% complete] Goal: Fully transition Ethereum from Proof-of-work to Proof-of-stake.
Casper the Friendly Finality Gadget
Cryptocurrencies without Proof of Work
Proof of stake FAQ
Economic Incentive analysis [49%]
Ouroboros: A Provably Secure Proof-of-Stake Blockchain Protocol Minimum Slashing Conditions Slasher Ghost, and Other Developments in Proof of Stake Least Authority Performs Incentive Analysis For Ethereum Demystifying incentives in the consensus computer On Stake Safety Under Dynamic Validator Sets Delegation protocols (or Voting Pool for PoS) [20%]
Using trusted hardware Formal Verification [45%]
Formal methods on some PoS stuff A mechanized safety proof with dynamic validators Formal methods on another Casper Securify.ch Testing and Implementation [20%]
History of Casper: Chapters 1, 2, 3, 4, and 5 Stage 1 CASPER contract and JSON RPC demo 1.3 Protocol Economics [50%] Goal: Increase economic incentive confluence in all aspects of the Ethereum protocol.
Gas Limit Policy / state-resource pricing
A theory of Blockchain Resoure Pricing [not ready for release; ask Virgil for link to pre-release] Topic: Validatominer economic policy—how much should we pay out?
1.4 Stategies for efficaciously hardforking for upgrades [40%] Goal: Smart-contracts are new territory and the best ideas in the space remain undiscovered. When we discover them, we must be able to roll them out gracefully.
Hard Forks, Soft Forks, Defaults and Coercion
The beautiful Vlad Zamfir on Soft forks, hard forks, and the Ethereum Social Contract
Topic: Hardforking the EVM
1.5 Ethereum Virtual Machine (EVM) upgrades and optimization [100%] Goal: Have a fast, efficient virtual machine optimized for processing cryptographic operations and smart-contracts. Update: Solved! We’re moving to eWASM!
  1. Layer 2 2.1 On-chain Random Number Generation [63%] Goal: This is an important special-case necessary for many applications. We wish to solve it.
Implementation Ethereum’s RANDAO A candidate alternative design from Vitalik Bitcoin Beacon On Bitcoin as a public randomness source NIST Randomness Beacon Bitcoin Beacon — Princeton Bitcoin seminar final project Tor project’s attempt at the same. 2.2 Privacy [40%] Goal: Allow apps to benefit from the transparency of blockchain-execution while preserving author privacy and the confidentiality of zer data. One solution, among several, is homomorphic encryption.
General: Privacy on the Blockchain
Mixers [30%] Bitcoin mixing remains an unsolved problem. As what’s possible in Ethereum is a strict superset of Bitcoin, solving for either case is sufficient. Incentivized Mixing?
Princeton Bitcoin course: Anonymity (Lecture 6) An Empirical Analysis of Linkability in the Monero Blockchain CoinParty: Secure Multi-Party Mixing of Bitcoins Secure and Anonymous Decentralized Bitcoin Mixing Decentralized Mixer based on RingSignature Laundromat: Mixing via ring signatures Voting [10%]
A Smart Contract for Boardroom Voting with Maximum Voter Privacy Zero knowlege proofs [30%]
ZK-Snarks Other
Confidential assets 2.3 Decentralized exchanges [50%] Goal: We wish to minimize the necessity of trusted third parties in currency exchanges.
Atomic swap on-chain decentralized exchanges mkr market etherdelta 2.4 High-level-languages (HLLs) [40%] Goal: Coding contracts (especially secure ones!) is hard. It should be easier. Please help us.
Our packet for recruiting PLT researchers.
Languages
Solidity Viper Pact Composing contrats: an adventure in finanial engineering Ivy Bamboo functional-solidity-language Pax Codex Hammurabi Project in Wolfram Language Formal Verification of HLLs [15%]
Formal Certification of a Compiler Back-end or: Programming a Compiler with a Proof Assistant Short Paper: Formal Verification of Smart Contracts Other programming language techniques to analyse smart contracts
Oyente, a symbolic execution based analyser for smart contracts Using Oyente to optimize smart contracts Defensive programming [30%]
Step by Step Towards Creating a Safe Smart Contract: Lessons and Insights from a Cryptocurrency Lab A Programmer’s Guide to Ethereum and Serpent A survey of attacks on Ethereum smart contracts Thinking About Smart Contract Security Ethereum Contract Security Techniques and Tips 2.5 Better Tokens, better token sales Goal: Understand how to design and manipulate tokens for specific properties, particularly paying attention to better ICOs
Vitalik on his Interactive Coin Offering The MiniMe/ERC223 talk from DEVCON3 An Optimal ICO mechanism Better ICOs category on ethresear.ch All about DAICOs Appendix Ethereum’s old list of open problems. Relevant Conferences Research communities whose interests intersect with Ethereum’s research include (in alphabetical order, non-exhaustive):
Algorithmic Game Theory. ACM Conference on Economics and Computation, Conference on Web and Internet Economics, Symposium on Algorithmic Game Theory, International Conference on Game Theory Blockchain. Annual Blockchain Summit, Coinfest, Consensus, Internet of Things World, Workshop on Bitcoin and Blockchain Research Computer Security. ACM Conference on Computer and Communications Security, IEEE Computer Security Foundations Symposium, USENIX Security Symposium Cryptography. CRYPTO (International Association for Cryptologic Research), EUROCRYPT (Annual International Conference on the Theory and Applications of Cryptographic Techniques) Distributed Computation. ACM Symposium on Principles of Distributed Computing, ACM Symposium on Parallelism in Algorithms and Architectures Multi-Agent Systems. International Conference on Autonomous Agents and Multiagent Sytems, AAAI Conference on Artificial Intelligence, International Joint Conference on Artificial Intelligence
http://notes.eth.sg/s/rkxpeG0ff
submitted by gwood333 to stellar1 [link] [comments]

An overview of in-person POS and payment gateway solutions for small businesses (in the US)

Bitcoin acceptance solutions for online merchants are fairly numerous, but the options for in-person transaction solutions by physical merchants are rather limited and underdeveloped. As I've been working with a small business right now to integrate Bitcoin payments, I thought I'd share my own experiences and opinions on our present choices. Here are the various ways I can think of to accept bitcoin payments for in-person transactions, with comments:
Pros: Simplest to setup with high versatility for managing payments and choosing services on the backend. No merchant account required.
Cons: Static addresses are terrible for personal and network privacy. Hard to verify payments depending on the backend solution and availability to the cashier at the time of the transaction. Requires the use of some other currency exchange conversion tool to generate BTC amount. Burdensome on the customer to manually type in transaction total and requires trust or verification that they do so accurately. Limited-to-no bookkeeping export.
Pros: Use of proven software and existing knowledge making business setup easy. Potential, though limited, for dynamic address generation per transaction. Potential use of existing hardware (computer or staff's phones). Widespread availability of built-in currency conversion and encoding into an address+amount QR codes. Widest selection of software.
Cons: For dedicated devices, unlimited access by staff to wallet balance and send functions (unless secured by passcode requiring authorized user presence and effective procedures for use) -or- use of staff's personal devices (unless dedicated phones carried by authorized users). Likely use of static addresses with negative privacy implications. Typically slow and error-prone to convert currency totals and present to customer (e.g., must select correct currency denomination, bring up mobile keyboard, be sure to type a decimal point in the right position). Potential for showing wallet balance to the customer. Limited to no bookkeeping export.
Pros: Faster, less error-prone total entry and checkout processing with address+amount QR display. Potential for an all-in-one solution to Bitcoin acceptance with customer support and minimal or no handling or understanding of Bitcoin wallets, addresses, ect., by merchant staff. Potential for automatic bitcoin conversion to local currency with deposit to a business bank account. Potential for sales item setup and easy tap-to-add ordecart generation with sales tax addition. Potential for Payment Protocol (BIP 70-73) support. Likely use of dynamic address generation per transaction. Some bookkeeping export. Potential to avoid bookkeeping complexity with capital gains and separate currency tracking via daily currency conversion.
Cons: More complicated setup and testing. Dedicated hardware recommended. Very limited app and processor selection at this time. Less tested and more experimental. Merchant signup and approval likely needed. Recurring or per-payment costs for backend services. Likely limited backend technical support.
Pros: Most elegant solution for bitcoin payments. Bitcoin included as an option along with other payment methods without switching programs. Easiest to use and train staff to use. Possibility to include Bitcoin as one of multiple split payments in a single transaction. Inclusion in standard receipt generation. Tracking in POS suite along with other payment methods. Best bookkeeping support. Best technical support. Potential to support Bitcoin debit cards.
Cons: Most expensive (by far), unless writing your own API-based custom software. Custom software requiring the most testing. Better for medium-to-large size businesses. Dependent on POS solutions provider for continued Bitcoin support.
My recommendation: The best compromise between privacy, convenience, speed, reliability, setup time, cost, and complexity right now seems to be BitPay with their device-independent hosted checkout (recently updated to work much better) that you can keep open or bookmarked in a browser on a computer, phone, or tablet. Coinbase with the Coinbase Merchant app I can't recommend right now due to significant delays in my tests before the app would recognize payment. The Coinbox app linked to Coinbase solves this problem and functions beautifully, but right now it is not generating dynamic addresses (a bug I've reported). Coinbox linked to BitPay has a more serious bug (also reported): Rounding mismatches upon currency conversion.
If you don't care about address reuse or the merchant is willing to periodically generate new addresses, then any of the regular wallets could work including CoinBox + Coinbase (you can periodically reset and relink CoinBox to generate a new address). A business-dedicated tablet is what we use at Boss Stage Arcade.
submitted by bits-of-change to acceptbitcoin [link] [comments]

Integrated Bitcoin POS system for a restaurant?

I am a partner in a new restaurant group that will rolling out a few locations of small sandwhich style shops in the Chicagoland area next year. I am a huge fan of Bitcoin and would like to offer Bitcoin payment at our sites. Right now we are putting together budgets and I said I would research POS solutions. The two other partners in the group have no idea what Bitcoin is and could care less as long as it's not more expensive to offer it.
These are small 1500 square foot sites with only a couple employees so there is no need for an extravagant and expensive restaurant POS system. There will only be one location to checkout and no servers.
I am aware of the tablet style solution that is common that sites like Bitpay offer but personally I don't like this idea. I know there will be a strong contingent of people that will disagree but something like this is not for us. Between training employees, dead tablets, spilled drinks I just don't see it fitting well in the long run.
I came across this solution from SoftTouch which I will investigate further but it seems like it may be a little too much for what we need and therefore probably costly.
http://www.coindesk.com/softtouch-pos-helps-restaurants-turn-bitcoins-dollars/
http://www.softtouchpos.com/
I also came across this idea which is a little more of what I was thinking.
https://en.bitcoin.it/wiki/Casascius_Bitcoin_POS_system
The problem is the price of XBT on this wiki is $5.00 which dates it and I couldn't find anything else on it.
Does anyone know of any other POS systems that integrate Bitcoin? Any help is greatly appreciated.
Thanks guys
PS... I left just enough in the design to hopefully install a Bitcoin ATM if they ever become available in the US.
submitted by Plumbum27 to Bitcoin [link] [comments]

How to Send Bitcoin Using Email or SMS Proof of Stake PoS is REPLACING Proof of Work PoW  Decentralized Finance Rare Autec Evolution Car Wash System Older Oasis Typhoon FULL WASH Youre StiLL The One

SoftTouch POS has announced the integration of bitcoin acceptance into its flagship point-of-sale payment system. According to CoinDesk, the integration was made to "capitalize on the explosion in the popularity of bitcoin.". SoftTouch's POS system is geared specifically toward the restaurant industry. Schedule a POS demo today! Learn more about POS mobile and iPad ordering, POS EMV & PA-DSS, cloud services, and real-time reporting. Leader in blockchain news. Restaurant electronic solutions maker SoftTouch POS is integrating bitcoin into its flagship point-of-sale payment system. --Our Solutions-- With innovative point-of-sale solutions that range from SoftTouch POS™, currently sold through a national reseller network spanning over 40 states, to Bitcoin Payment Read the latest headlines, news stories, and opinion from Politics, Entertainment, Life, Perspectives, and more.

[index] [29216] [20014] [11835] [11673] [24377] [8762] [2952] [8706] [23935] [30755]

How to Send Bitcoin Using Email or SMS

All-In-One Point of Sale System Touchscreen ... Bitcoin NFC POS prototype by XBTerminal ... 0:41. Retail POS Software Demo - POS Nation - Duration: 7:42. POS Nation Recommended for you. (Rare Find) Really Fast Older Oasis Typhoon With Peco Dryers at a Canadian Tire Car Wash in Bolton - Duration: 8:23. Tyler M 630 views Aplus computerised Food & Beverage Portal (FBP) System is specially designed and developed locally since 1983 to suit the Malaysia business environment. Aplus FBP10K is the easiest POS software in ... In this FasTrax video, learn how to create, edit, and delete tax rates and tax groups in the POS. FasTraxPOS comes equipped with a powerful suite of integrated tools that fully automate your POS ... (*NEW*) NCS Ryko Radius Touch Free Car Wash w/Washify POS - Duration: 8:51. CarWashNews 26,678 views. 8:51 ... RARE Nu-Star Soft Touch Plus Friction Curtain - Galleria Car Wash, ...

Flag Counter