Developer Tools BitPay Documentation

Subreddit Stats: programming top posts from 2019-10-22 to 2020-10-21 06:41 PDT

Period: 364.67 days
Submissions Comments
Total 1000 180545
Rate (per day) 2.74 491.84
Unique Redditors 629 34951
Combined Score 1178903 2688497

Top Submitters' Top Submissions

  1. 47468 points, 49 submissions: iamkeyur
    1. One Guy Ruined Hacktoberfest 2020 (3039 points, 584 comments)
    2. AWS forked my project and launched it as its own service (2956 points, 810 comments)
    3. Privacy analysis of Tiktok’s app and website (2858 points, 234 comments)
    4. 98.css – design system for building faithful recreations of Windows 98 UIs (2781 points, 318 comments)
    5. Microsoft demos language model that writes code based on signature and comment (2621 points, 614 comments)
    6. Why does HTML think “chucknorris” is a color? (2565 points, 531 comments)
    7. Windows 95 UI Design (2309 points, 665 comments)
    8. The Linux codebase has over 3k TODO comments, many from over a decade ago (2119 points, 369 comments)
    9. eBay is port scanning visitors to their website (1829 points, 236 comments)
    10. Using const/let instead of var can make JavaScript code run 10× slower in Webkit (1814 points, 525 comments)
  2. 44853 points, 28 submissions: speckz
    1. From August, Chrome will start blocking ads that consume 4MB of network data, 15 seconds of CPU usage in any 30 second period, or 60 seconds of total CPU usage (8434 points, 590 comments)
    2. How To Spot Toxic Software Jobs From Their Descriptions (6246 points, 1281 comments)
    3. A Facebook crawler was making 7M requests per day to my stupid website (2662 points, 426 comments)
    4. Apple, Your Developer Documentation is Garbage (2128 points, 432 comments)
    5. The code I’m still ashamed of (2016) (2105 points, 429 comments)
    6. Slack Is Fumbling Developers And The Rise Of Developer Discords (2095 points, 811 comments)
    7. The Chromium project finds that around 70% of our serious security bugs are memory safety problems. Our next major project is to prevent such bugs at source. (1959 points, 418 comments)
    8. Advice to Myself When Starting Out as a Software Developer (1934 points, 257 comments)
    9. Software patents are another kind of disease (1893 points, 419 comments)
    10. My favourite Git commit (1772 points, 206 comments)
  3. 35237 points, 28 submissions: whackri
    1. It is perfectly OK to only code at work, you can have a life too (6765 points, 756 comments)
    2. Kernighan's Law - Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. (5171 points, 437 comments)
    3. The entire Apollo 11 computer code that helped get us to the Moon is available on github. (3841 points, 433 comments)
    4. Raytracing - in Excel! (2478 points, 168 comments)
    5. Writing userspace USB drivers for abandoned devices (1689 points, 84 comments)
    6. Drum Machine in Excel (1609 points, 60 comments)
    7. fork() can fail: this is important (1591 points, 264 comments)
    8. Learn how computers add numbers and build a 4 bit adder circuit (1548 points, 66 comments)
    9. Heroes Of Might And Magic III engine written from scratch (open source, playable) (1453 points, 84 comments)
    10. Apollo Guidance Computer: Restoring the computer that put man on the Moon (1277 points, 47 comments)
  4. 14588 points, 11 submissions: pimterry
    1. I'm a software engineer going blind, how should I prepare? (4237 points, 351 comments)
    2. The 2038 problem is already affecting some systems (1988 points, 518 comments)
    3. TLDR pages: Simplified, community-driven man pages (1897 points, 182 comments)
    4. JetBrains Mono: A Typeface for Developers (1728 points, 456 comments)
    5. BlurHash: extremely compact representations of image placeholders (930 points, 159 comments)
    6. Let's Destroy C (855 points, 290 comments)
    7. Shared Cache is Going Away (833 points, 192 comments)
    8. XML is almost always misused (766 points, 538 comments)
    9. Wireshark has a new packet diagram view (688 points, 24 comments)
    10. fork() can fail: this is important (460 points, 299 comments)
  5. 14578 points, 9 submissions: magenta_placenta
    1. Trello handed over user's personal account to user's previous company (2962 points, 489 comments)
    2. Feds: IBM did discriminate against older workers in making layoffs - “Analysis shows it was primarily older workers (85.85%) in the total potential pool of those considered for layoff,” the EEOC wrote (2809 points, 509 comments)
    3. Stripe Workers Who Relocate Get $20,000 Bonus and a Pay Cut - Stripe Inc. plans to make a one-time payment of $20,000 to employees who opt to move out of San Francisco, New York or Seattle, but also cut their base salary by as much as 10% (2765 points, 989 comments)
    4. US court fully legalized website scraping and technically prohibited it - On September 9, the U.S. 9th circuit court of Appeals ruled that web scraping public sites does not violate the CFAA (Computer Fraud and Abuse Act) (2014 points, 327 comments)
    5. I Suspect many Task Deadlines are Designed to Force Engineers to Work for Free (1999 points, 553 comments)
    6. Intent to Deprecate and Freeze: The User-Agent string (1012 points, 271 comments)
    7. Contractor admits planting logic bombs in his software to ensure he’d get new work (399 points, 182 comments)
    8. AlphaStar: Grandmaster level in StarCraft II using multi-agent reinforcement learning (396 points, 97 comments)
    9. Half of the websites using WebAssembly use it for malicious purposes - WebAssembly not that popular: Only 1,639 sites of the Top 1 Million use WebAssembly (222 points, 133 comments)
  6. 13750 points, 3 submissions: pedrovhb
    1. Bubble sort visualization (7218 points, 276 comments)
    2. Breadth-first search visualization (3874 points, 96 comments)
    3. Selection sort visualization (2658 points, 80 comments)
  7. 11833 points, 1 submission: flaming_bird
    1. 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions in source code (11833 points, 956 comments)
  8. 11208 points, 10 submissions: PowerOfLove1985
    1. No cookie consent walls — and no, scrolling isn’t consent, says EU data protection body (5975 points, 890 comments)
    2. Redesigning uBlock Origin (1184 points, 162 comments)
    3. Playing Around With The Fuchsia Operating System (696 points, 164 comments)
    4. Microsoft's underwater data centre resurfaces after two years (623 points, 199 comments)
    5. Microsoft Paint/Paintbrush in Javascript (490 points, 58 comments)
    6. GitHub shuts off access to Aurelia repository, citing trade sanctions (478 points, 81 comments)
    7. How 3D Game Rendering Works: Texturing (475 points, 22 comments)
    8. Simdjson: Parsing Gigabytes of JSON per Second (441 points, 90 comments)
    9. How 1500 bytes became the MTU of the internet (435 points, 60 comments)
    10. It’s OK for your open source library to be a bit shitty (411 points, 130 comments)
  9. 10635 points, 8 submissions: michalg82
    1. Turning animations to 60fps using AI (3449 points, 234 comments)
    2. Bug #1463112 “Cat sitting on keyboard crashes lightdm” (3150 points, 143 comments)
    3. Heroes Of Might And Magic III engine written from scratch (open source, playable) (1431 points, 172 comments)
    4. Vulkan is coming to Raspberry Pi: first triangle - Raspberry Pi (1318 points, 66 comments)
    5. An EPYC trip to Rome: AMD is Cloudflare's 10th-generation Edge server CPU (431 points, 60 comments)
    6. Microsoft cancels GDC 2020 presence due to coronavirus concerns (Following Sony, Facebook, Kojima Productions, Epic Games, Unity, and more) (371 points, 52 comments)
    7. Moving from reCAPTCHA to hCaptcha - The Cloudflare Blog (278 points, 71 comments)
    8. How much of a genius-level move was using binary space partitioning in Doom? (207 points, 109 comments)
  10. 10106 points, 10 submissions: SerenityOS
    1. Someone suggested I should host my website on my own OS. For that we'll need a web server, so here's me building a basic web server in C++ for SerenityOS! (2269 points, 149 comments)
    2. I've been learning about OS security lately. Here's me making a local root exploit for SerenityOS, and then fixing the kernel bugs that made it possible! (1372 points, 87 comments)
    3. SerenityOS was hacked in a 36c3 CTF! (Exploit and write-up) (1236 points, 40 comments)
    4. One week ago, I started building a JavaScript engine for SerenityOS. Here’s me integrating it with the web browser and adding some simple API’s like alert()! (1169 points, 63 comments)
    5. Implementing macOS-style "purgeable memory" in my kernel. This technique is amazing and helps apps be better memory usage citizens! (1131 points, 113 comments)
    6. SerenityOS: The second year (900 points, 101 comments)
    7. Using my own C++ IDE to make a little program for decorating my webcam frame (571 points, 33 comments)
    8. This morning I ported git to SerenityOS. It took about an hour and some hacks, but it works! :D (547 points, 64 comments)
    9. Smarter C/C++ inlining with attribute((flatten)) (521 points, 118 comments)
    10. Introduction to SerenityOS GUI programming (390 points, 45 comments)

Top Commenters

  1. XANi_ (10753 points, 821 comments)
  2. dnew (7513 points, 641 comments)
  3. drysart (7479 points, 202 comments)
  4. MuonManLaserJab (6666 points, 233 comments)
  5. SanityInAnarchy (6331 points, 350 comments)
  6. AngularBeginner (6215 points, 59 comments)
  7. SerenityOS (5627 points, 128 comments)
  8. chucker23n (5465 points, 370 comments)
  9. IshKebab (4898 points, 393 comments)
  10. L3tum (4857 points, 199 comments)

Top Submissions

  1. 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions in source code by flaming_bird (11833 points, 956 comments)
  2. hentAI: Detecting and removing censors with Deep Learning and Image Segmentation by 7cmStrangler (9621 points, 395 comments)
  3. US Politicians Want to Ban End-to-End Encryption by CarrotRobber (9427 points, 523 comments)
  4. From August, Chrome will start blocking ads that consume 4MB of network data, 15 seconds of CPU usage in any 30 second period, or 60 seconds of total CPU usage by speckz (8434 points, 590 comments)
  5. Mozilla: The Greatest Tech Company Left Behind by matthewpmacdonald (7566 points, 1087 comments)
  6. Bubble sort visualization by pedrovhb (7218 points, 276 comments)
  7. During lockdown my wife has been suffering mentally from pressure to stay at her desk 100% of the time otherwise after a few minutes her laptop locks and she is recorded as inactive. I wrote this small app to help her escape her desk by periodically moving the cursor. Hopefully it can help others. by silitbang6000 (7193 points, 855 comments)
  8. It is perfectly OK to only code at work, you can have a life too by whackri (6765 points, 756 comments)
  9. Blockchain, the amazing solution for almost nothing by imogenchampagne (6725 points, 1561 comments)
  10. Blockchain, the amazing solution for almost nothing by jessefrederik (6524 points, 1572 comments)

Top Comments

  1. 2975 points: deleted's comment in hentAI: Detecting and removing censors with Deep Learning and Image Segmentation
  2. 2772 points: I_DONT_LIE_MUCH's comment in 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions in source code
  3. 2485 points: api's comment in Stripe Workers Who Relocate Get $20,000 Bonus and a Pay Cut - Stripe Inc. plans to make a one-time payment of $20,000 to employees who opt to move out of San Francisco, New York or Seattle, but also cut their base salary by as much as 10%
  4. 2484 points: a_false_vacuum's comment in Stack Overflow lays off 15%
  5. 2464 points: iloveparagon's comment in Google engineer breaks down the problems he uses when doing technical interviews. Lots of advice on algorithms and programming.
  6. 2384 points: why_not_both_bot's comment in During lockdown my wife has been suffering mentally from pressure to stay at her desk 100% of the time otherwise after a few minutes her laptop locks and she is recorded as inactive. I wrote this small app to help her escape her desk by periodically moving the cursor. Hopefully it can help others.
  7. 2293 points: ThatInternetGuy's comment in Iranian Maintainer refuses to merge code from Israeli Developer. Cites Iranian regulations.
  8. 2268 points: xequae's comment in I'm a software engineer going blind, how should I prepare?
  9. 2228 points: turniphat's comment in AWS forked my project and launched it as its own service
  10. 2149 points: Rami-Slicer's comment in 20GB leak of Intel data: whole Git repositories, dev tools, backdoor mentions in source code
Generated with BBoe's Subreddit Stats
submitted by flpezet to subreddit_stats [link] [comments]

Transcript of how Philip the tyrant admin of the Bitcoin Cash Telegram group called Spoice stupid, an idiot, a parrot among other insults then banned her instead of discussing Bitcoin Cash. That Telegram group is hostile, ABC/IFP shills run and follows the rBitcoin toxic censorship modus operandi.

David B., [18.10.20 01:46]
https://www.reddit.com/btc/comments/jdagi3/whats_up_with_the_bchn_hypocrisy/

David B., [18.10.20 01:47]
Wut x2

J Stodd, [18.10.20 01:49]
[In reply to David B.]
Their words are meaningless. They have no principles. Wish i could comment but bitcoinxio banned me from rbtc and never told me why

David B., [18.10.20 01:59]
These comments are so toxic

Spoice, [18.10.20 01:59]
In reality, the real continuation of Bitcoin as we all know it is what is carried on by BCHN, BU, BCHD and others

Spoice, [18.10.20 02:00]
ABC is changing the rules to something that is not Bitcoin

Spoice, [18.10.20 02:00]
anyone denying those facts is selling you snake oil

Spoice, [18.10.20 02:00]
If Blockstream tried to take some % to their own benefit, we would have never needed BCH in the first place

Spoice, [18.10.20 02:00]
everyone would have rejected them in a second

J Stodd, [18.10.20 02:01]
[In reply to Spoice]
Bitcoin Cash is not Bitcoin to start with, so who cares?

David B., [18.10.20 02:01]
[ Album ]

Spoice, [18.10.20 02:01]
yet we have ABC trying to pull this theft and all those puppets think it's ok

Spoice, [18.10.20 02:01]
JSTodd that's bullshit

David B., [18.10.20 02:01]
Like trying to talk to a core maxi about altcoins

Spoice, [18.10.20 02:01]
Bitcoin Cash is the most Bitcoin out of all Bitcoins

Spoice, [18.10.20 02:01]
it is the continuation of what Satoshi started

David B., [18.10.20 02:02]
Tbh they aren't even toxic

Michael Nunzio, [18.10.20 02:02]
[In reply to Spoice]
If the hash follows then it is Bitcoin Cash. Only if it doesn't is your claim true

J Stodd, [18.10.20 02:03]
[In reply to Spoice]
Bitcoin is Bitcoin. Bitcoin failed to be Peer to Peer Cash, so Bitcoin Cash attempted to fix this by forking Bitcoin and attacking the root of the problem. This does not mean Bitcoin Cash is literally Bitcoin. Adopt a different argument. Sorry if you bought into that bc of Rogers rantings

J Stodd, [18.10.20 02:05]
Bitcoin Cash can replace Bitcoin, and if Bitcoin dies and BCH wins then sure maybe it can take its name from its grave, but they are different products, trying to say Bitcoin stopped being "Bitcoin" and became BCH is a self contradiction.

Jingles, [18.10.20 02:08]
Jstodd's got some good points.

Jingles, [18.10.20 02:08]
He's learnt so much in the last year ☺️

Spoice, [18.10.20 02:08]
"Bitcoin is Bitcoin" is a false statement. BTC is just an instance of Bitcoin. Bitcoin is the set of rules defined in the whitepaper first and foremost, it is peer to peer electronic cash. BTC no longer fits that criteria. Bitcoin Cash meets them. The fork proposed by ABC also fails to meet that criteria. Therefore the continuation of Bitcoin is in whatever BU, BCHN, Flowee and others will continue.

Jingles, [18.10.20 02:09]
What rules were defined in the WP?

Spoice, [18.10.20 02:10]
Let's see which rules aren't: 1) No coinbase tax going to any centralized entity such as ABC 2) No throttling of TX throughput such as BTC

Spoice, [18.10.20 02:10]
therefore they both fail the simple "Is this Bitcoin?" test

Spoice, [18.10.20 02:11]
Finally, Michael, if you think Hash rate defines what Bitcoin is, you should stick to BTC

Jingles, [18.10.20 02:11]
21 million coins isn't in the WP

Jingles, [18.10.20 02:11]
I asked what rules did the WP define.

Spoice, [18.10.20 02:12]
Because BCH failed that criteria since it forked, therefore your point is wrong

Spoice, [18.10.20 02:12]
https://www.metzdowd.com/pipermail/cryptography/2009-January/014994.html

Spoice, [18.10.20 02:12]
The announcement of the white paper included the 21 million limit, close enough

Jingles, [18.10.20 02:12]
HIs announcement isn't the WP

Spoice, [18.10.20 02:12]
show me where Satoshi said that Amaury shoudl tax the chain?

Spoice, [18.10.20 02:12]
Doesn't matter- close enough

Jingles, [18.10.20 02:12]
Bitcoin is the set of rules defined in the whitepaper first and foremost - You

Jingles, [18.10.20 02:13]
My ears pricked up on that comment, so I'm asking you what you meant.

Spoice, [18.10.20 02:13]
Correct. Changing the 21 million hard limit is still more Bitcoin than taxing the Coinbase, yet both will never ever happen. Not to Bitcoin anyway

Jingles, [18.10.20 02:13]
If you meant Satoj's writings pre and post WP then you should be clear about it

Spoice, [18.10.20 02:13]
some bastardized chain might, just not Bitcoin

Jingles, [18.10.20 02:14]
The closest we have to anything to indicate what is "Bitcoiness" is general things like "the longest chain"

Spoice, [18.10.20 02:14]
No, it is never a single thing

David B., [18.10.20 02:15]
REEEE

Jingles, [18.10.20 02:15]
trustless, no single trusted third parties, and rules can change due to incentives via consensus

Spoice, [18.10.20 02:15]
it is a set of common sense and experiment driven and historical relevance and initial parameters and "peer to peer electronic cash" definition indicators

Spoice, [18.10.20 02:15]
never a single thing

Jingles, [18.10.20 02:16]
[In reply to Spoice]
This is like the exact opposite of what you said earlier

Jingles, [18.10.20 02:16]
Bitcoin is defined by the rules in the WP, I mean common sense.

Jingles, [18.10.20 02:16]
🤷‍♂️

Spoice, [18.10.20 02:16]
Nope, the rule set is defined in the white paper should never change, but I never said all rules are defined in the white paper

Jingles, [18.10.20 02:16]
What rules?

Spoice, [18.10.20 02:16]
It is a union

Jingles, [18.10.20 02:17]
What rules are there?

Spoice, [18.10.20 02:17]
Rules in the white paper + what continued to define Bitcoin thereafter

J Stodd, [18.10.20 02:17]
[In reply to Spoice]
> "Bitcoin is Bitcoin is a false statement."
Alas, if we cannot agree on the law of identity, aka A=A, then i dont understand how to hold a conversation with you using logic.
> BTC is an instance of Bitcoin
No, BTC is a ticker used optionally by exchanges. Other common tickers for bitcoin include XBC, XBT, BC (correct me if im wrong on any of these)
> "Bitcoin is a set of rules in the whitepaper"
Super hard to defend this. Theres no mention of a 21M supply cap, no blocksize limit *at all*, and it also says additional rules and incentives can be enforced (implying maybe they should).

Jingles, [18.10.20 02:17]
I go through this with BSVers all the time. We have no spec sheet of rules defining what Bitcoin is from Satoshi.

Spoice, [18.10.20 02:18]
Rules such as what defines a correct block, miners receiving the full incentive of mining it, etc

Jingles, [18.10.20 02:18]
The WP is a highlevel document

Spoice, [18.10.20 02:18]
The WP is a description of a scientific experiment

Spoice, [18.10.20 02:18]
if you want to start your own experiment, be my guest

Jingles, [18.10.20 02:18]
[In reply to Spoice]
Valid tx rules aren't defined in the WP

Spoice, [18.10.20 02:18]
just don't try to call it Bitcoin

Jingles, [18.10.20 02:19]
The word majority is in the WP an awful lot wouldn't you say?

Spoice, [18.10.20 02:19]
Not valid TX rules, but what a proof of work block is and how it diverts the reward to the miner, etc

Jingles, [18.10.20 02:20]
[In reply to Spoice]
and? what about BTC doesn't apply?

Jingles, [18.10.20 02:20]
I'm not arguing for any fork of BCH here.

Spoice, [18.10.20 02:20]
It no longer meets the very title of the white paper experiment, "Peer to peer electronic cash"

Spoice, [18.10.20 02:20]
The BTC instance of the experiment is destined to move away from the very title of the white paper

Jingles, [18.10.20 02:20]
It's electronic, and I use it like cash.

Spoice, [18.10.20 02:20]
that the maintainers even wanted to edit the white paper (Cobra and co) because of this fact

J Stodd, [18.10.20 02:20]
u/Spoice When did BTC stop being Bitcoin in your view? The day Amaury decided to launch the fork, before Segwit happened?
If someone else launched a fork first, they would have been "the real bitcoin"?
This is a game of whoever forks first becomes the real Bitcoin?
What if two people launched a fork at the exact same time, maybe even with identical specs?

Jingles, [18.10.20 02:21]
Where did I go wrong?

Jingles, [18.10.20 02:21]
[In reply to Spoice]
Did they?

Spoice, [18.10.20 02:21]
Doesn't matter if you use it today, its very technical fabric will have to move your transactions to 2nd layers and it will no longer be peer to peer electronic cash on chain

Jingles, [18.10.20 02:21]
peer to peer electronic cash on chain - Not in the wp

Jingles, [18.10.20 02:22]
We have satoj talking about HFT with sidechannels.

Jingles, [18.10.20 02:22]
So what?

Jingles, [18.10.20 02:23]
I think this is a good discussion Phil, nothing disrespectful is being said. I hope this is ok?

Spoice, [18.10.20 02:23]
Doesn't matter, the rule of common sense, which is closer to that title? Increasing a simple variable (Blocksize) to stay on track of the title and experiment, or introduce IOUs and Watchtowers and channels and locked BTC and that whole LN Bastardization? Which is close to the title?

Jingles, [18.10.20 02:23]
No one said that can't happen

Michael Nunzio, [18.10.20 02:24]
[In reply to Spoice]
Congratulations you've made an argument which isn't an argument.

Jingles, [18.10.20 02:25]
The whole thing that was said was the system is based on majority rules, and incentives can be changed. Majority breaks any deadlock.

David B., [18.10.20 02:25]
How to kill a coin 101

Spoice, [18.10.20 02:25]
Logic fails anyone who tries to claim BTC, ABC, BSV or any similar standalone experiments as Bitcoin, because of simple sanity checks and logic checks, often stemming out of common sense - If what you have moves you a single step away from what is otherwise the same old experiment which Satoshi wrote about and unleashed, you're not Bitcoin. If what you have moves you a step closer, it is Bitcoin. and so on and so forth.

Phlip - Not giving away coins, [18.10.20 02:25]
Wow, really fanatical almost religious statements. I guess its Sunday morning.

Jingles, [18.10.20 02:27]
[In reply to Spoice]
There's nothing common about common sense. You point to the WP to make a point, and your point isn't in there.

Spoice, [18.10.20 02:27]
Throttled and you need off-chain IOUs and always-on services to function (BTC) ? Not Bitcoin. Requires permission to be used and could be centrally confiscated on the whim of the organization behind it (BSV)? Not Bitcoin. Premined (Bitcoin Gold, Diamond)? Not Bitcoin. Taxing the miners through Coinbase and changing the incentives which were at play since day 0 (ABC)? Not Bitcoin

Spoice, [18.10.20 02:27]
simple checks really, yet those who are set to benefit will of course be oblivious to these

Phlip - Not giving away coins, [18.10.20 02:28]
This whole “Bitcoin Cash is the true Bitcoin - see whitepaper” is really stupid. It also ignores the history of how Bitcoin Cash came into existence

Jingles, [18.10.20 02:28]
Phillip, remove anyone here that has said Bitcoin Gold was the original Bitcoin immediately

Jingles, [18.10.20 02:28]
^^^^

Jingles, [18.10.20 02:29]
[In reply to Phlip - Not giving away coins]
It falls to pieces the moment it's questioned.

Spoice, [18.10.20 02:29]
It is not about "True" Bitcoin

Spoice, [18.10.20 02:30]
It is about the Bitcoin closest to the experiment which always was

Spoice, [18.10.20 02:30]
I don't care about "True" or not, they all are true

Phlip - Not giving away coins, [18.10.20 02:30]
[In reply to Jingles]
Sorry, I hve stopped reading all the sillyness above. Will reread later

Jingles, [18.10.20 02:30]
[In reply to Phlip - Not giving away coins]
I'm joking around 😂

Spoice, [18.10.20 02:30]
but the rule of entropy says I shouldn't place my money nor effort in experiments which are set to fade eventually, because they have skewed incentives

Phlip - Not giving away coins, [18.10.20 02:31]
[In reply to Spoice]
You get to chose that for yourself but you do not get to dictate it for others

David B., [18.10.20 02:31]
[In reply to Phlip - Not giving away coins]
Don't read it. You will have no braincells left

Spoice, [18.10.20 02:31]
Bitcoin as we know it has a long track record of incentives which work

Spoice, [18.10.20 02:31]
I won't ever dictate it for others

Spoice, [18.10.20 02:31]
I only would dictate it for myself, just like how I never use BTC or BSV today, I won't use ABC tomorrow

Spoice, [18.10.20 02:32]
only because they're new experiments

Spoice, [18.10.20 02:32]
interesting, and I wish them luck

Jingles, [18.10.20 02:32]
"Bitcoin is Bitcoin" is a false statement - Spoice 2020

Spoice, [18.10.20 02:32]
but I would rather stick to the Bitcoin I know

Spoice, [18.10.20 02:32]
that's all

Jingles, [18.10.20 02:32]
I won't ever dictate it for others - Also Spoice
Phlip - Not giving away coins, [18.10.20 02:32]
Bitcoin Cash came with a plan snd goals. They were clearly presented in two presentations that happened before viabtc announced they would mine with ABC software and create a coin and chain named Bitcoin Cash

Spoice, [18.10.20 02:32]
Yes, because he means BTC is Bitcoin, and that's a false statement

Jingles, [18.10.20 02:32]
How is it false?

Spoice, [18.10.20 02:32]
It is an instance of Bitcoin

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:33]
[In reply to Michael Nunzio]
you're looking intimidatingly handsome in your new profile picture

Phlip - Not giving away coins, [18.10.20 02:33]
[In reply to Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ]]
Lol

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:33]
[In reply to J Stodd]
actually a good question

Spoice, [18.10.20 02:34]
Anyway, those are my two cents

Spoice, [18.10.20 02:34]
Everyone is free to choose which experiments to pour their effort on and their money in

Phlip - Not giving away coins, [18.10.20 02:34]
[In reply to Spoice]
You are entitled to your opinion.

Spoice, [18.10.20 02:34]
Andreas is publishing Lightning Network books, I mean

Spoice, [18.10.20 02:34]
So to each his own

Phlip - Not giving away coins, [18.10.20 02:35]
[In reply to Spoice]
Lets leave it at that

Spoice, [18.10.20 02:35]
but Bitcoin as I know it continues with no Tax, and that in my opinion is BCH with no tax

Phlip - Not giving away coins, [18.10.20 02:35]
Ah you had to continue

Phlip - Not giving away coins, [18.10.20 02:36]
Good thing no tax is proposed by anyone
Spoice, [18.10.20 02:35]
Isn't this the Bitcoin Cash telegram?

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:35]
😅

Spoice, [18.10.20 02:36]
If I don't discuss Bitcoin Cash here, where should I?

Spoice, [18.10.20 02:36]
Tax, IFP, call it what you will

Spoice, [18.10.20 02:36]
from my perspective as a user, it's one the same

J Stodd, [18.10.20 02:36]
[In reply to Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ]]
I bet nobody will answer it, either

Phlip - Not giving away coins, [18.10.20 02:37]
[In reply to Spoice]
Apparently btc /s

David B., [18.10.20 02:37]
[In reply to Spoice]
As a user what do you care?

Jingles, [18.10.20 02:37]
Ooh, can I shill the Bitcoin room in here?

Spoice, [18.10.20 02:37]
Nah, I prefer quick responses and chats

Spoice, [18.10.20 02:37]
Reddit is broken

Phlip - Not giving away coins, [18.10.20 02:37]
[In reply to Jingles]
Lol

J Stodd, [18.10.20 02:37]
[In reply to Spoice]
Nobody even pays it, it just comes out of the block reward. The block reward is not sentient, it cannot be stolen from or wronged

Phlip - Not giving away coins, [18.10.20 02:37]
Dont push your luck 😉

Jingles, [18.10.20 02:37]
[ 😀 Sticker ]

Michael Nunzio, [18.10.20 02:38]
[In reply to Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ]]
You too brother. 🙏

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:38]
[In reply to Michael Nunzio]
but mine is the same....i need new ones everyone always calls me fat because of this one

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:38]
literally if i say 1 thing to any troll anywhere first thing they say is "ok fatass"

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:38]
i blame this dumb photographer

Michael Nunzio, [18.10.20 02:38]
[In reply to Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ]]
Don't listen.

Phlip - Not giving away coins, [18.10.20 02:39]
u/spoice maybe write a read.cash article if you really feel you need to educate people

Spoice, [18.10.20 02:39]
David, as a user I believe that each new experiment carries risk with it, why should I take part in a new fork of Bitcoin which has a new set of game-theory rules which doesn't even benefit me, rather it benefits some other entity which will take 5% of any effort or economic activity I produce on this chain? They're also off-loading the risk to me as a usebuildebusiness who choose to join their experiment.

Spoice, [18.10.20 02:40]
Why should I take that risk while the Bitcoin I know and have known for over 10 years worked perfectly for me thus far? (BCH, that is)

Jingles, [18.10.20 02:40]
small fees and empty blocks?

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:41]
It will insure that a centralized group has control over development and they are by decree in the code, it's a literal take over.

Phlip - Not giving away coins, [18.10.20 02:41]
[In reply to Spoice]
“BSV-freeze the protocol - true Bitcoin” sounds like more your thing

David B., [18.10.20 02:41]
[In reply to Spoice]
Better run bitcoin core 0.1

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:41]
Imagine if satoshi keyd his address in the code to be paid out of every block, but instead of paying himself started a company "Bitcoin Dev Co"

Spoice, [18.10.20 02:42]
Not really, BSV kills the incentives I am discussing too

Phlip - Not giving away coins, [18.10.20 02:42]
[In reply to Jingles]
Please stay nice now

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:42]
No one would ever be able to say Bitcoin was Decentralized, Bitcoin Dev Co would get paid directly from the reward.

Jingles, [18.10.20 02:42]
[In reply to Phlip - Not giving away coins]
"BSV: We have all the Bad Idea. On chain"

Spoice, [18.10.20 02:42]
The Nash equilibrium we have tested for the past 10 years will be changed with ABC, it changed with BTC and BSV too

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:42]
"Bad Solutions Verified"

Spoice, [18.10.20 02:42]
that game-theory set of incentives

Spoice, [18.10.20 02:43]
why would I want to take a risk with any of those experiments when I gain 0?

David B., [18.10.20 02:43]
Better run bitcoin core 0.1

Spoice, [18.10.20 02:43]
Nope, you're talking technical freezing of development, that's not what I am addressing

Jingles, [18.10.20 02:43]
[In reply to David B.]
Thats the BTC chain though

Phlip - Not giving away coins, [18.10.20 02:43]
[In reply to Spoice]
O please share with us your background in the subject. Or are you now just parroting others

Spoice, [18.10.20 02:44]
BSV wants to freeze the technical development and they want a stable protocol from an API/development perspective

Spoice, [18.10.20 02:44]
but from an incentive ruleset perspective, they already butchered the equilibrium Bitcoin had

Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ], [18.10.20 02:44]
[In reply to Phlip - Not giving away coins]
That's one of those phrases, when you hear it you know they are just a parrot of someones propaganda. "MUH NASH EQUILIBRIUM!"

David B., [18.10.20 02:44]
Stable = bad?

Jingles, [18.10.20 02:45]
[In reply to Jc Crown [ I DON'T DM PEOPLE - DON'T GIVE ME MONEY! ]]
I love you

Spoice, [18.10.20 02:45]
Philip, for an admin you are ought to be nicer, if you think I am parroting others you're free to think that, but to state it so bluntly in your position is just... wrong

Spoice, [18.10.20 02:46]
If you think the point I made is wrong, discuss it

Phlip - Not giving away coins, [18.10.20 02:46]
[In reply to Jingles]
Maybe talk to him in DM about that?😉

Spoice, [18.10.20 02:46]
not me

Jingles, [18.10.20 02:46]
[In reply to Phlip - Not giving away coins]
working on it.

Phlip - Not giving away coins, [18.10.20 02:46]
[In reply to Spoice]
I ought to be nicer...😂😂😂

Spoice, [18.10.20 02:47]
Also, anyone who studied Bitcoin at length and its set of incentives and game-theory ruleset should know what a Nash Equilibrium is and who the players are in the Bitcoin game

Phlip - Not giving away coins, [18.10.20 02:47]
[In reply to Spoice]
You state as fact. You get to dhow why your statements or opinions are even relevant.

Spoice, [18.10.20 02:48]
If it's not a fact, highlight how

Spoice, [18.10.20 02:48]
don't attack me

Spoice, [18.10.20 02:48]
prove me wrong

Spoice, [18.10.20 02:48]
if you fail that simple debate test

David B., [18.10.20 02:48]
How's that breakfast helping?

Spoice, [18.10.20 02:48]
you should rename from Janitor to Tyrant

Jingles, [18.10.20 02:48]
I'm still waiting to see the defined rules as per the wp

Michael Nunzio, [18.10.20 02:49]
[In reply to Spoice]
Didn't know this was stand up comedy night in here.

Michael Nunzio, [18.10.20 02:49]
I missed the memo

Phlip - Not giving away coins, [18.10.20 02:49]
If I have to prove all idiots on the internet wrong I would have a hard time. You are starting to really waste everybody’s time. You state, you prove. Or you are just generating noise

Phlip - Not giving away coins, [18.10.20 02:50]
[In reply to Spoice]
Be careful now.

Michael Nunzio, [18.10.20 02:50]
Noisy bugger.

Phlip - Not giving away coins, [18.10.20 02:52]
Getting close to just do some cleaning up.

Spoice, [18.10.20 02:52]
If you can't debate technical points I am making about Bitcoin Cash on a Bitcoin Cash Telegram, and within the span of 10 minutes you called me stupid, idiot, noisy and a parrot, you absolutely are a tyrant and I stand by my point: You should not be an admin here, nor anywhere actually. If you think I should be careful for the fear of you banning me, go ahead. You still fail to debate the simplest technical point and yet claim you can "but can't be bothered to". You remind me of that Thermos guy.

Spoice, [18.10.20 02:53]
How do people with 0 technical know how end up in these admin positions is beyond me

Jingles, [18.10.20 02:53]
I challenged your comments and you just changed the goal posts.

Phlip - Not giving away coins, [18.10.20 02:53]
[In reply to Spoice]
Ok. You are not paying me and you are free to create noise elsewhere
submitted by wisequote to btc [link] [comments]

Scaling Reddit Community Points with Arbitrum Rollup: a piece of cake

Scaling Reddit Community Points with Arbitrum Rollup: a piece of cake
https://preview.redd.it/b80c05tnb9e51.jpg?width=2550&format=pjpg&auto=webp&s=850282c1a3962466ed44f73886dae1c8872d0f31
Submitted for consideration to The Great Reddit Scaling Bake-Off
Baked by the pastry chefs at Offchain Labs
Please send questions or comments to [[email protected] ](mailto:[email protected])
1. Overview
We're excited to submit Arbitrum Rollup for consideration to The Great Reddit Scaling Bake-Off. Arbitrum Rollup is the only Ethereum scaling solution that supports arbitrary smart contracts without compromising on Ethereum's security or adding points of centralization. For Reddit, this means that Arbitrum can not only scale the minting and transfer of Community Points, but it can foster a creative ecosystem built around Reddit Community Points enabling points to be used in a wide variety of third party applications. That's right -- you can have your cake and eat it too!
Arbitrum Rollup isn't just Ethereum-style. Its Layer 2 transactions are byte-for-byte identical to Ethereum, which means Ethereum users can continue to use their existing addresses and wallets, and Ethereum developers can continue to use their favorite toolchains and development environments out-of-the-box with Arbitrum. Coupling Arbitrum’s tooling-compatibility with its trustless asset interoperability, Reddit not only can scale but can onboard the entire Ethereum community at no cost by giving them the same experience they already know and love (well, certainly know).
To benchmark how Arbitrum can scale Reddit Community Points, we launched the Reddit contracts on an Arbitrum Rollup chain. Since Arbitrum provides full Solidity support, we didn't have to rewrite the Reddit contracts or try to mimic their functionality using an unfamiliar paradigm. Nope, none of that. We launched the Reddit contracts unmodified on Arbitrum Rollup complete with support for minting and distributing points. Like every Arbitrum Rollup chain, the chain included a bridge interface in which users can transfer Community Points or any other asset between the L1 and L2 chains. Arbitrum Rollup chains also support dynamic contract loading, which would allow third-party developers to launch custom ecosystem apps that integrate with Community Points on the very same chain that runs the Reddit contracts.
1.1 Why Ethereum
Perhaps the most exciting benefit of distributing Community Points using a blockchain is the ability to seamlessly port points to other applications and use them in a wide variety of contexts. Applications may include simple transfers such as a restaurant that allows Redditors to spend points on drinks. Or it may include complex smart contracts -- such as placing Community Points as a wager for a multiparty game or as collateral in a financial contract.
The common denominator between all of the fun uses of Reddit points is that it needs a thriving ecosystem of both users and developers, and the Ethereum blockchain is perhaps the only smart contract platform with significant adoption today. While many Layer 1 blockchains boast lower cost or higher throughput than the Ethereum blockchain, more often than not, these attributes mask the reality of little usage, weaker security, or both.
Perhaps another platform with significant usage will rise in the future. But today, Ethereum captures the mindshare of the blockchain community, and for Community Points to provide the most utility, the Ethereum blockchain is the natural choice.
1.2 Why Arbitrum
While Ethereum's ecosystem is unmatched, the reality is that fees are high and capacity is too low to support the scale of Reddit Community Points. Enter Arbitrum. Arbitrum Rollup provides all of the ecosystem benefits of Ethereum, but with orders of magnitude more capacity and at a fraction of the cost of native Ethereum smart contracts. And most of all, we don't change the experience from users. They continue to use the same wallets, addresses, languages, and tools.
Arbitrum Rollup is not the only solution that can scale payments, but it is the only developed solution that can scale both payments and arbitrary smart contracts trustlessly, which means that third party users can build highly scalable add-on apps that can be used without withdrawing money from the Rollup chain. If you believe that Reddit users will want to use their Community Points in smart contracts--and we believe they will--then it makes the most sense to choose a single scaling solution that can support the entire ecosystem, eliminating friction for users.
We view being able to run smart contracts in the same scaling solution as fundamentally critical since if there's significant demand in running smart contracts from Reddit's ecosystem, this would be a load on Ethereum and would itself require a scaling solution. Moreover, having different scaling solutions for the minting/distribution/spending of points and for third party apps would be burdensome for users as they'd have to constantly shuffle their Points back and forth.
2. Arbitrum at a glance
Arbitrum Rollup has a unique value proposition as it offers a combination of features that no other scaling solution achieves. Here we highlight its core attributes.
Decentralized. Arbitrum Rollup is as decentralized as Ethereum. Unlike some other Layer 2 scaling projects, Arbitrum Rollup doesn't have any centralized components or centralized operators who can censor users or delay transactions. Even in non-custodial systems, centralized components provide a risk as the operators are generally incentivized to increase their profit by extracting rent from users often in ways that severely degrade user experience. Even if centralized operators are altruistic, centralized components are subject to hacking, coercion, and potential liability.
Massive Scaling. Arbitrum achieves order of magnitude scaling over Ethereum's L1 smart contracts. Our software currently supports 453 transactions-per-second for basic transactions (at 1616 Ethereum gas per tx). We have a lot of room left to optimize (e.g. aggregating signatures), and over the next several months capacity will increase significantly. As described in detail below, Arbitrum can easily support and surpass Reddit's anticipated initial load, and its capacity will continue to improve as Reddit's capacity needs grow.
Low cost. The cost of running Arbitrum Rollup is quite low compared to L1 Ethereum and other scaling solutions such as those based on zero-knowledge proofs. Layer 2 fees are low, fixed, and predictable and should not be overly burdensome for Reddit to cover. Nobody needs to use special equipment or high-end machines. Arbitrum requires validators, which is a permissionless role that can be run on any reasonable on-line machine. Although anybody can act as a validator, in order to protect against a “tragedy of the commons” and make sure reputable validators are participating, we support a notion of “invited validators” that are compensated for their costs. In general, users pay (low) fees to cover the invited validators’ costs, but we imagine that Reddit may cover this cost for its users. See more on the costs and validator options below.
Ethereum Developer Experience. Not only does Arbitrum support EVM smart contracts, but the developer experience is identical to that of L1 Ethereum contracts and fully compatible with Ethereum tooling. Developers can port existing Solidity apps or write new ones using their favorite and familiar toolchains (e.g. Truffle, Buidler). There are no new languages or coding paradigms to learn.
Ethereum wallet compatibility. Just as in Ethereum, Arbitrum users need only hold keys, but do not have to store any coin history or additional data to protect or access their funds. Since Arbitrum transactions are semantically identical to Ethereum L1 transactions, existing Ethereum users can use their existing Ethereum keys with their existing wallet software such as Metamask.
Token interoperability. Users can easily transfer their ETH, ERC-20 and ERC-721 tokens between Ethereum and the Arbitrum Rollup chain. As we explain in detail below, it is possible to mint tokens in L2 that can subsequently be withdrawn and recognized by the L1 token contract.
Fast finality. Transactions complete with the same finality time as Ethereum L1 (and it's possible to get faster finality guarantees by trading away trust assumptions; see the Arbitrum Rollup whitepaper for details).
Non-custodial. Arbitrum Rollup is a non-custodial scaling solution, so users control their funds/points and neither Reddit nor anyone else can ever access or revoke points held by users.
Censorship Resistant. Since it's completely decentralized, and the Arbitrum protocol guarantees progress trustlessly, Arbitrum Rollup is just as censorship-proof as Ethereum.
Block explorer. The Arbitrum Rollup block explorer allows users to view and analyze transactions on the Rollup chain.
Limitations
Although this is a bake-off, we're not going to sugar coat anything. Arbitrum Rollup, like any Optimistic Rollup protocol, does have one limitation, and that's the delay on withdrawals.
As for the concrete length of the delay, we've done a good deal of internal modeling and have blogged about this as well. Our current modeling suggests a 3-hour delay is sufficient (but as discussed in the linked post there is a tradeoff space between the length of the challenge period and the size of the validators’ deposit).
Note that this doesn't mean that the chain is delayed for three hours. Arbitrum Rollup supports pipelining of execution, which means that validators can keep building new states even while previous ones are “in the pipeline” for confirmation. As the challenge delays expire for each update, a new state will be confirmed (read more about this here).
So activity and progress on the chain are not delayed by the challenge period. The only thing that's delayed is the consummation of withdrawals. Recall though that any single honest validator knows immediately (at the speed of L1 finality) which state updates are correct and can guarantee that they will eventually be confirmed, so once a valid withdrawal has been requested on-chain, every honest party knows that the withdrawal will definitely happen. There's a natural place here for a liquidity market in which a validator (or someone who trusts a validator) can provide withdrawal loans for a small interest fee. This is a no-risk business for them as they know which withdrawals will be confirmed (and can force their confirmation trustlessly no matter what anyone else does) but are just waiting for on-chain finality.
3. The recipe: How Arbitrum Rollup works
For a description of the technical components of Arbitrum Rollup and how they interact to create a highly scalable protocol with a developer experience that is identical to Ethereum, please refer to the following documents:
Arbitrum Rollup Whitepaper
Arbitrum academic paper (describes a previous version of Arbitrum)
4. Developer docs and APIs
For full details about how to set up and interact with an Arbitrum Rollup chain or validator, please refer to our developer docs, which can be found at https://developer.offchainlabs.com/.
Note that the Arbitrum version described on that site is older and will soon be replaced by the version we are entering in Reddit Bake-Off, which is still undergoing internal testing before public release.
5. Who are the validators?
As with any Layer 2 protocol, advancing the protocol correctly requires at least one validator (sometimes called block producers) that is honest and available. A natural question is: who are the validators?
Recall that the validator set for an Arbitrum chain is open and permissionless; anyone can start or stop validating at will. (A useful analogy is to full nodes on an L1 chain.) But we understand that even though anyone can participate, Reddit may want to guarantee that highly reputable nodes are validating their chain. Reddit may choose to validate the chain themselves and/or hire third-party validators.To this end, we have begun building a marketplace for validator-for-hire services so that dapp developers can outsource validation services to reputable nodes with high up-time. We've announced a partnership in which Chainlink nodes will provide Arbitrum validation services, and we expect to announce more partnerships shortly with other blockchain infrastructure providers.
Although there is no requirement that validators are paid, Arbitrum’s economic model tracks validators’ costs (e.g. amount of computation and storage) and can charge small fees on user transactions, using a gas-type system, to cover those costs. Alternatively, a single party such as Reddit can agree to cover the costs of invited validators.
6. Reddit Contract Support
Since Arbitrum contracts and transactions are byte-for-byte compatible with Ethereum, supporting the Reddit contracts is as simple as launching them on an Arbitrum chain.
Minting. Arbitrum Rollup supports hybrid L1/L2 tokens which can be minted in L2 and then withdrawn onto the L1. An L1 contract at address A can make a special call to the EthBridge which deploys a "buddy contract" to the same address A on an Arbitrum chain. Since it's deployed at the same address, users can know that the L2 contract is the authorized "buddy" of the L1 contract on the Arbitrum chain.
For minting, the L1 contract is a standard ERC-20 contract which mints and burns tokens when requested by the L2 contract. It is paired with an ERC-20 contract in L2 which mints tokens based on whatever programmer provided minting facility is desired and burns tokens when they are withdrawn from the rollup chain. Given this base infrastructure, Arbitrum can support any smart contract based method for minting tokens in L2, and indeed we directly support Reddit's signature/claim based minting in L2.
Batch minting. What's better than a mint cookie? A whole batch! In addition to supporting Reddit’s current minting/claiming scheme, we built a second minting design, which we believe outperforms the signature/claim system in many scenarios.
In the current system, Reddit periodically issues signed statements to users, who then take those statements to the blockchain to claim their tokens. An alternative approach would have Reddit directly submit the list of users/amounts to the blockchain and distribute the tokens to the users without the signature/claim process.
To optimize the cost efficiency of this approach, we designed an application-specific compression scheme to minimize the size of the batch distribution list. We analyzed the data from Reddit's previous distributions and found that the data is highly compressible since token amounts are small and repeated, and addresses appear multiple times. Our function groups transactions by size, and replaces previously-seen addresses with a shorter index value. We wrote client code to compress the data, wrote a Solidity decompressing function, and integrated that function into Reddit’s contract running on Arbitrum.
When we ran the compression function on the previous Reddit distribution data, we found that we could compress batched minting data down to to 11.8 bytes per minting event (averaged over a 6-month trace of Reddit’s historical token grants)compared with roughly 174 bytes of on-chain data needed for the signature claim approach to minting (roughly 43 for an RLP-encoded null transaction + 65 for Reddit's signature + 65 for the user's signature + roughly 8 for the number of Points) .
The relative benefit of the two approaches with respect to on-chain call data cost depends on the percentage of users that will actually claim their tokens on chain. With the above figures, batch minting will be cheaper if roughly 5% of users redeem their claims. We stress that our compression scheme is not Arbitrum-specific and would be beneficial in any general-purpose smart contract platform.
8. Benchmarks and costs
In this section, we give the full costs of operating the Reddit contracts on an Arbitrum Rollup chain including the L1 gas costs for the Rollup chain, the costs of computation and storage for the L2 validators as well as the capital lockup requirements for staking.
Arbitrum Rollup is still on testnet, so we did not run mainnet benchmarks. Instead, we measured the L1 gas cost and L2 workload for Reddit operations on Arbitrum and calculated the total cost assuming current Ethereum gas prices. As noted below in detail, our measurements do not assume that Arbitrum is consuming the entire capacity of Ethereum. We will present the details of our model now, but for full transparency you can also play around with it yourself and adjust the parameters, by copying the spreadsheet found here.
Our cost model is based on measurements of Reddit’s contracts, running unmodified (except for the addition of a batch minting function) on Arbitrum Rollup on top of Ethereum.
On the distribution of transactions and frequency of assertions. Reddit's instructions specify the following minimum parameters that submissions should support:
Over a 5 day period, your scaling PoC should be able to handle:
  • 100,000 point claims (minting & distributing points)
  • 25,000 subscriptions
  • 75,000 one-off points burning
  • 100,000 transfers
We provide the full costs of operating an Arbitrum Rollup chain with this usage under the assumption that tokens are minted or granted to users in batches, but other transactions are uniformly distributed over the 5 day period. Unlike some other submissions, we do not make unrealistic assumptions that all operations can be submitted in enormous batches. We assume that batch minting is done in batches that use only a few percent on an L1 block’s gas, and that other operations come in evenly over time and are submitted in batches, with one batch every five minutes to keep latency reasonable. (Users are probably already waiting for L1 finality, which takes at least that long to achieve.)
We note that assuming that there are only 300,000 transactions that arrive uniformly over the 5 day period will make our benchmark numbers lower, but we believe that this will reflect the true cost of running the system. To see why, say that batches are submitted every five minutes (20 L1 blocks) and there's a fixed overhead of c bytes of calldata per batch, the cost of which will get amortized over all transactions executed in that batch. Assume that each individual transaction adds a marginal cost of t. Lastly assume the capacity of the scaling system is high enough that it can support all of Reddit's 300,000 transactions within a single 20-block batch (i.e. that there is more than c + 300,000*t byes of calldata available in 20 blocks).
Consider what happens if c, the per-batch overhead, is large (which it is in some systems, but not in Arbitrum). In the scenario that transactions actually arrive at the system's capacity and each batch is full, then c gets amortized over 300,000 transactions. But if we assume that the system is not running at capacity--and only receives 300,000 transactions arriving uniformly over 5 days-- then each 20-block assertion will contain about 200 transactions, and thus each transaction will pay a nontrivial cost due to c.
We are aware that other proposals presented scaling numbers assuming that 300,000 transactions arrived at maximum capacity and was executed in a single mega-transaction, but according to our estimates, for at least one such report, this led to a reported gas price that was 2-3 orders of magnitude lower than it would have been assuming uniform arrival. We make more realistic batching assumptions, and we believe Arbitrum compares well when batch sizes are realistic.
Our model. Our cost model includes several sources of cost:
  • L1 gas costs: This is the cost of posting transactions as calldata on the L1 chain, as well as the overhead associated with each batch of transactions, and the L1 cost of settling transactions in the Arbitrum protocol.
  • Validator’s staking costs: In normal operation, one validator will need to be staked. The stake is assumed to be 0.2% of the total value of the chain (which is assumed to be $1 per user who is eligible to claim points). The cost of staking is the interest that could be earned on the money if it were not staked.
  • Validator computation and storage: Every validator must do computation to track the chain’s processing of transactions, and must maintain storage to keep track of the contracts’ EVM storage. The cost of computation and storage are estimated based on measurements, with the dollar cost of resources based on Amazon Web Services pricing.
It’s clear from our modeling that the predominant cost is for L1 calldata. This will probably be true for any plausible rollup-based system.
Our model also shows that Arbitrum can scale to workloads much larger than Reddit’s nominal workload, without exhausting L1 or L2 resources. The scaling bottleneck will ultimately be calldata on the L1 chain. We believe that cost could be reduced substantially if necessary by clever encoding of data. (In our design any compression / decompression of L2 transaction calldata would be done by client software and L2 programs, never by an L1 contract.)
9. Status of Arbitrum Rollup
Arbitrum Rollup is live on Ethereum testnet. All of the code written to date including everything included in the Reddit demo is open source and permissively licensed under the Apache V2 license. The first testnet version of Arbitrum Rollup was released on testnet in February. Our current internal version, which we used to benchmark the Reddit contracts, will be released soon and will be a major upgrade.
Both the Arbitrum design as well as the implementation are heavily audited by independent third parties. The Arbitrum academic paper was published at USENIX Security, a top-tier peer-reviewed academic venue. For the Arbitrum software, we have engaged Trail of Bits for a security audit, which is currently ongoing, and we are committed to have a clean report before launching on Ethereum mainnet.
10. Reddit Universe Arbitrum Rollup Chain
The benchmarks described in this document were all measured using the latest internal build of our software. When we release the new software upgrade publicly we will launch a Reddit Universe Arbitrum Rollup chain as a public demo, which will contain the Reddit contracts as well as a Uniswap instance and a Connext Hub, demonstrating how Community Points can be integrated into third party apps. We will also allow members of the public to dynamically launch ecosystem contracts. We at Offchain Labs will cover the validating costs for the Reddit Universe public demo.
If the folks at Reddit would like to evaluate our software prior to our public demo, please email us at [email protected] and we'd be more than happy to provide early access.
11. Even more scaling: Arbitrum Sidechains
Rollups are an excellent approach to scaling, and we are excited about Arbitrum Rollup which far surpasses Reddit's scaling needs. But looking forward to Reddit's eventual goal of supporting hundreds of millions of users, there will likely come a time when Reddit needs more scaling than any Rollup protocol can provide.
While Rollups greatly reduce costs, they don't break the linear barrier. That is, all transactions have an on-chain footprint (because all calldata must be posted on-chain), albeit a far smaller one than on native Ethereum, and the L1 limitations end up being the bottleneck for capacity and cost. Since Ethereum has limited capacity, this linear use of on-chain resources means that costs will eventually increase superlinearly with traffic.
The good news is that we at Offchain Labs have a solution in our roadmap that can satisfy this extreme-scaling setting as well: Arbitrum AnyTrust Sidechains. Arbitrum Sidechains are similar to Arbitrum Rollup, but deviate in that they name a permissioned set of validators. When a chain’s validators agree off-chain, they can greatly reduce the on-chain footprint of the protocol and require almost no data to be put on-chain. When validators can't reach unanimous agreement off-chain, the protocol reverts to Arbitrum Rollup. Technically, Arbitrum Sidechains can be viewed as a hybrid between state channels and Rollup, switching back and forth as necessary, and combining the performance and cost that state channels can achieve in the optimistic case, with the robustness of Rollup in other cases. The core technical challenge is how to switch seamlessly between modes and how to guarantee that security is maintained throughout.
Arbitrum Sidechains break through this linear barrier, while still maintaining a high level of security and decentralization. Arbitrum Sidechains provide the AnyTrust guarantee, which says that as long as any one validator is honest and available (even if you don't know which one will be), the L2 chain is guaranteed to execute correctly according to its code and guaranteed to make progress. Unlike in a state channel, offchain progress does not require unanimous consent, and liveness is preserved as long as there is a single honest validator.
Note that the trust model for Arbitrum Sidechains is much stronger than for typical BFT-style chains which introduce a consensus "voting" protocols among a small permissioned group of validators. BFT-based protocols require a supermajority (more than 2/3) of validators to agree. In Arbitrum Sidechains, by contrast, all you need is a single honest validator to achieve guaranteed correctness and progress. Notice that in Arbitrum adding validators strictly increases security since the AnyTrust guarantee provides correctness as long as any one validator is honest and available. By contrast, in BFT-style protocols, adding nodes can be dangerous as a coalition of dishonest nodes can break the protocol.
Like Arbitrum Rollup, the developer and user experiences for Arbitrum Sidechains will be identical to that of Ethereum. Reddit would be able to choose a large and diverse set of validators, and all that they would need to guarantee to break through the scaling barrier is that a single one of them will remain honest.
We hope to have Arbitrum Sidechains in production in early 2021, and thus when Reddit reaches the scale that surpasses the capacity of Rollups, Arbitrum Sidechains will be waiting and ready to help.
While the idea to switch between channels and Rollup to get the best of both worlds is conceptually simple, getting the details right and making sure that the switch does not introduce any attack vectors is highly non-trivial and has been the subject of years of our research (indeed, we were working on this design for years before the term Rollup was even coined).
12. How Arbitrum compares
We include a comparison to several other categories as well as specific projects when appropriate. and explain why we believe that Arbitrum is best suited for Reddit's purposes. We focus our attention on other Ethereum projects.
Payment only Rollups. Compared to Arbitrum Rollup, ZK-Rollups and other Rollups that only support token transfers have several disadvantages:
  • As outlined throughout the proposal, we believe that the entire draw of Ethereum is in its rich smart contracts support which is simply not achievable with today's zero-knowledge proof technology. Indeed, scaling with a ZK-Rollup will add friction to the deployment of smart contracts that interact with Community Points as users will have to withdraw their coins from the ZK-Rollup and transfer them to a smart contract system (like Arbitrum). The community will be best served if Reddit builds on a platform that has built-in, frictionless smart-contract support.
  • All other Rollup protocols of which we are aware employ a centralized operator. While it's true that users retain custody of their coins, the centralized operator can often profit from censoring, reordering, or delaying transactions. A common misconception is that since they're non-custodial protocols, a centralized sequencer does not pose a risk but this is incorrect as the sequencer can wreak havoc or shake down users for side payments without directly stealing funds.
  • Sidechain type protocols can eliminate some of these issues, but they are not trustless. Instead, they require trust in some quorum of a committee, often requiring two-third of the committee to be honest, compared to rollup protocols like Arbitrum that require only a single honest party. In addition, not all sidechain type protocols have committees that are diverse, or even non-centralized, in practice.
  • Plasma-style protocols have a centralized operator and do not support general smart contracts.
13. Concluding Remarks
While it's ultimately up to the judges’ palate, we believe that Arbitrum Rollup is the bakeoff choice that Reddit kneads. We far surpass Reddit's specified workload requirement at present, have much room to optimize Arbitrum Rollup in the near term, and have a clear path to get Reddit to hundreds of millions of users. Furthermore, we are the only project that gives developers and users the identical interface as the Ethereum blockchain and is fully interoperable and tooling-compatible, and we do this all without any new trust assumptions or centralized components.
But no matter how the cookie crumbles, we're glad to have participated in this bake-off and we thank you for your consideration.
About Offchain Labs
Offchain Labs, Inc. is a venture-funded New York company that spun out of Princeton University research, and is building the Arbitrum platform to usher in the next generation of scalable, interoperable, and compatible smart contracts. Offchain Labs is backed by Pantera Capital, Compound VC, Coinbase Ventures, and others.
Leadership Team
Ed Felten
Ed Felten is Co-founder and Chief Scientist at Offchain Labs. He is on leave from Princeton University, where he is the Robert E. Kahn Professor of Computer Science and Public Affairs. From 2015 to 2017 he served at the White House as Deputy United States Chief Technology Officer and senior advisor to the President. He is an ACM Fellow and member of the National Academy of Engineering. Outside of work, he is an avid runner, cook, and L.A. Dodgers fan.
Steven Goldfeder
Steven Goldfeder is Co-founder and Chief Executive Officer at Offchain Labs. He holds a PhD from Princeton University, where he worked at the intersection of cryptography and cryptocurrencies including threshold cryptography, zero-knowledge proof systems, and post-quantum signatures. He is a co-author of Bitcoin and Cryptocurrency Technologies, the leading textbook on cryptocurrencies, and he has previously worked at Google and Microsoft Research, where he co-invented the Picnic signature algorithm. When not working, you can find Steven spending time with his family, taking a nature walk, or twisting balloons.
Harry Kalodner
Harry Kalodner is Co-founder and Chief Technology Officer at Offchain Labs where he leads the engineering team. Before the company he attended Princeton as a Ph.D candidate where his research explored economics, anonymity, and incentive compatibility of cryptocurrencies, and he also has worked at Apple. When not up at 3:00am writing code, Harry occasionally sleeps.
submitted by hkalodner to ethereum [link] [comments]

Weekly Update: 21st June, 2019

Hi everyone 👋 The sun is shining here and Bitcoin is up, so all is good with the world ☀️
I have quite a bit to update you on today... here we go!
Moses Skoda joined the team this week. He's working on our services layer.
We've made strong headway with the build of our updated site, focused on core network services. We've also closed out the final colour ways and font choices or the brand update. I'll be sharing some detail on this front with you next week.
And I expect us to be rolling out the changes in the first half of July.
Suffice to say, Ravi's done an awesome job.
We had the PPA awards this week, where Paul presented one of the gongs.
It was a really positive evening for us – we have 20+ new conversations opened up on the back of the event.
I met with David Wilde to plan introductions to local government, and to explore methods for supporting delivery, for example by embedding our networking software within local data centres.
We also discussed the detail of his ongoing engagement with the project, covering speaking arrangements, articles and an approach for central government.
I wrote an article for Fintech magazine which should be published next week. I'll share the link when it's published.
We kicked off with our new PR. Wind up time can take a while, but it's underway.
We've increased our engagement with one of our existing customers, who are now working with us on a deeper level to integrate core services.
One of our advisors Sean King is representing us in Cannes for the Cannes Lions this week, and has a few promising leads which we will be follow up on next week.
We have another promising engagement in the construction industry, which is the final throws of being defined before kicking off. As soon as we have more to share, we will.
The networking team have been continuing to put the finishing touches to the ACL migration piece required ahead of next months Mainnet release. This will make the transition from a single global ACL token to a per-user token seamless.
They also closed out enhancement work to the DNS service within the Edge network. it now supports all major record types in full, including MX, CNAME, NS and SOA record types.
It has also been refactoring in to an interface which makes extending record type coverage simple and lightweight. A version of this will be used for consumer level interfaces. More detail on this service will be released in the coming weeks.
Roadmap updates and timings were also completed this week. Items in the roadmap include:
...And a bunch more besides
!
We will be releasing a version of this to the community next week, and a full version with the release of the updated site in July.
Ecohustler went viral.
One of their articles (https://ecohustler.com/article/one-corporation-to-pollute-them-all/) was picked up by just about every social platform you can imagine. At peak the site was receiving 1k+ concurrent connections.
That's an increase in traffic of 16,566%. Pretty significant! Uptime during the stampede? 100%
API version 5 was released!
Release notes as follows:
https://github.com/dadi/api/releases/tag/v5.0.0
And documentation can be found here:
https://github.com/dadi/api/releases/tag/v5.0.0
We've also made huge strides in the definition of what will become a stand alone SaaS proposition for our web services. Some of you are already aware of the work being done on this front, but in summary: we are breaking out the web services in the network and will be offering them under a new brand and on a new - and very powerful - domain.
The reason for this is to allow us to focus the network on network-level services, better supporting its go to market.
This approach also means that we don't loose the momentum and investment made in the web services to date, and will present a stand alone entry point to use of the network (use of the web services under their new brand will deliver revenue directly back to the network).
We'll be announcing this formally when the full branding work for the proposition has been completed. We expect this to be in July.
The focus for the technology has been on maintaining an open source platform and enabling local development workflows as a key point of difference and supporting mechanic for the SaaS solution.
With regard to token price, I'm happy to see a continued upward trend since early May (+32%).
The token remains central to the network as the only method of realising an internal marketplace that pays for services within an edge proposition at scale. This utility will be further cemented as we move closer to stand alone contracts, and as we work to find new methods for storing the data of the network in the blockchain.
And that's it this week. Enjoy your weekends ✌️
submitted by josephdenne to edgenetwork [link] [comments]

Sharering (SHR) I believe this one is going to surprise so many. Already generating revenue and doing buybacks every week. Already over 10 000 registered users. Mainnet + app + masternodes and staking before EOY.

I got this stuff from Steve Aitchison, he wrote this review and posted it on Uptrennd. Figured I should put it on here as well since I truly believe this is an incredible moonshot. I'm personally holding SHR myself and am very convinced it will do extremely well.
Give a read through it and you will immediatly see why. Enjoy guys.
Introduction
Imagine for a second the following scenario. You are a 2 car family. One car is used every day going back and forth to work, for shopping, all the little jaunts you and your husband like to go on. Your grown children are at university and come home for the weekends so the other car sits in the driveway all week and doesn’t get used during the week. What a waste of a perfectly good car. You think to yourself we could put that car to good use and actually help to pay for university fees, by renting it out during the week. However, then you think “well it’s only a little Ford Fiesta who’s going to want to rent that.” Well, it turns out a lot of people want to rent it and for a good price: £34 ($40) per day, a possible $800 per month.
Peer to peer car sharing has grown massively over the last few years and people are making serious money by letting our vehicles on a daily basis, emulating the Airbnb model. In fact companies like Turo, Getaround and Drivy, which has just been acquired by Getaround for $300 Million, are bringing in serious investors like Toyota, Softbank Vision Fund, Menlo Ventures, and IAC to the tune of over $800 Million.
A key difference between rental companies and peer to peer is that they have vastly improved technology with app interfaces that make locating assets and resources, reserving and using them, and making payment convenient and seamless. This, combined with location-specific analytics, allows by-the-minute access to assets and resources (e.g. cars or bicycles) and enables customers to pick up and drop these assets where and when convenient.
Car sharing is just one example of an industry that is being disrupted. We have seen, experienced and read about the amazing growth of Airbnb which is now estimated to be valued at $38 Billion. Airbnb has been so successful that companies like booking.com are trying to get in on the act by adopting a similar model when it comes to booking accommodation.
There is also the phenomenal rise of bicycle rentals which we see in cities all over the world, not quite the same as peer to peer sharing, but it’s another rental model that is ripe for being disrupted by the new sharing model.
With this business model in mind what other areas could it be used in:
Transport: Used for the rental of cars, trucks, scooters, trailers, and even heavy vehicles. Delivery Drivers: Facilitate booking and payment for delivery drivers. Agriculture: Garden sharing, seed swap, bee-hive relocation, etc. Finance: Peer to peer lending Food bank, social dining Travel Tours, shared tour groups Real Estate Airbnb, co-housing, co-living, Couchsurfing, shared office space, house swapping. Time: Labour, co-working, freelancing Assets Book swapping, clothes swapping, fractional ownership, freecycling, toy libraries. Transportation Car sharing, ride-sharing, car-pooling, bicycle sharing, delivery company, couriers And so much more!
This newly emerging, but highly fragmented sharing industry, is currently worth over $100 billion. It is predicted to grow to at least $335 billion by 2025.
As you can see from a few examples above the sharing economy has a lot of room to grow but what it doesn’t have, yet, is a company who can facilitate ALL of the above use cases in one place.
That is until now!
ShareRing is disrupting the disruptors by bringing everything together in one place and making it easy for you and me to share anything and everything and making it as easy as opening an app on your phone.
Business Case
The sharing market has exploded over the last several years. This is due, in part, to the digital age we live in, as we now have over 2.82 Billion people with smart phones around the world. It also due to how easy the business model of sharing lends itself to the digital world, and how with the simple installation of an app we can access a plethora of markets to rent almost anything from.
Due to this rise of digital platforms and the proliferation of smartphones, revenues coming from sharing economy platforms are only expected to increase. It is estimated to grow to a $335 billion industry in 2025, compared to its $14 billion value in 2014. (PwC UK).
The beauty of the sharing economy is that it is a win/win/win situation for the person who wants to rent something for a few days or weeks, the person who is renting out, and the company who facilitates the ease of the transactions between the renter and the person renting out. Typically the renter will save a lot of money whilst renting out someone else’s apartment, car, bicycle, clothes, dog sitting services etc and they can almost be assured of quality due to the social side of the business model with reviews from real people. The person who is renting out can make additional income and will want good reviews and therefore keep the standard of service higher. The company that is facilitating all of this can make a lot of money on transaction fees, as well as from advertising, and partnership deals, and obviously have an exit strategy for possible buyouts.
When it comes to looking at the business model, ShareRing fits in to the Commission Based Platform as described in Ritter and Schanz study where they looked at the core difference in difference business models of the sharing economy: Singular Transaction Models, Subscription-Based Models, Commission-Based Platforms and Unlimited Platforms.)
Commission Based Platforms are dominated by (at least) triadic relationships amongst providers, intermediaries and consumers with a utility-bound revenue stream. These business models enable their customers to switch between provider and consumer roles by creating and delivering the value proposition. Only a few employees work for the intermediary and the value creation and delivery is externalized. From a consumer perspective, consumers are empowered to collaborate with each other and to design the collaboration terms by negotiating the terms and conditions of the content, creation, distribution and consumption of the value proposition. Depending on the orientation of the value proposition, consumers purchase commodities (Tauschticket, ebay), access commodities in a defined timespan (booking.com, Airbnb) or buy services (uber, turo) from occasional and professional providers found via an intermediary. The intermediary mainly focuses on nurturing a community feeling and reducing exchange insecurity by incorporating rating systems, micro-assurances and standardizations of payment and delivery into the platform. The platform mainly takes commissions for successful matching and executing trade. (Journal of Cleaner Production Volume 213, 10 March 2019, Pages 320-331)
The USP of the ShareRing Business Model
The USP that ShareRing has is that it brings all of the different forms of sharing together in one app through partnerships and onboarding of users.
No other company, to date, is bringing everything together in such a way. However there are other factors that make ShareRing unique, which we will look at.
Token Economics
SHR is a utility token and will be used to pay for transactions on the network, such as 'new booking', 'add asset', etc. SHR is used by providers to pay for their access to the ShareLedger blockchain, including the addition of assets, renting out of assets, adding attributes, adding smart contracts, and other features.
SharePay (SHRP) is used by customers to pay for the rental of assets.
Masternodes will also be a main feature of the SHR token. When a transaction fee is incurred, it will be distributed in a way that allows for masternode holders who provide a service to the platform to receive a reward from each transaction. Transaction fees are charged to sharing providers in SHR. The distribution of transaction fees will be as follows: 50% - will be distributed amongst the active masternode holders who host an active node on the blockchain at that point in time (these holders provide a service to the platform). The distribution will be based on a calculation of the Total Amount Staked and the total continuous uptime of the node. 50% - will be provided to ShareRing Ltd (view ShareRing owned masternodes) for various purposes that contribute to working capital and platform growth.
Leased Proof of Stake Consensus
ShareRing have chosen the Leased Proof-of-Stake protocol as the consensus algorithm for ShareLedger. This choice is based on the practicality and security benefits evident in the Waves platform. It is also much more cost effective than Proof-of-Work (POW), and will not suffer from the current issues Bitcoin and other POW cryptocurrencies are facing such as scalability and electricity consumption.
As explained above master nodes will be a main feature but there is the other feature of lightweight nodes. A user with a lightweight node will be able to stake their tokens to a full node of their choosing and participate in reaching consensus. They will also be free to cancel their leasing at any time as there are no contracts or freezing periods. The more tokens that have been staked in a full node, the higher the probability the node will have in producing the next block. Since the reward is given based on the total number of tokens staked in the full node, there will always be a trade-off between the size of the full node and the percentage of the reward. As an average user of the platform, you will not need to have technical knowledge on how to set up a node nor will you have to download the entire blockchain in order to stake your tokens. Only a user who sets up a full node will be required to do this, making it simpler than ever for users to earn a reward for supporting the platform.
The return expected for staking is expected to be around 6 - 8% although this has yet to be confirmed.
Buybacks
ShareRing are currently implementing a series of buybacks which started in the beginning of November:
The buyback operation is done at a random time during the week.
If there is enough liquidity, SHR tokens will be bought through a single market order at the time of buyback. In case there is not enough liquidity, a limit buy order at last sell order price will be placed on the market, and will remain open until it gets filled.
The buyback program was implemented to test the API purchase process for when live transactions occur on ShareLedger
The Buyback Program is expected to:
  1. Reduce the supply of ShareTokens available in both public and private markets
  2. Bring New capital and fund inflows into the Shareledger
  3. Substantially magnify value creation for the ShareToken holders
The Token Flow
ShareRing will bring in hundreds of merchants to list their rental products, either exclusively or as part of an aggregator system e.g. When you look at the likes of trivago.com they will list the best hotel prices from multiple merchants who are listed on their website. Essentially ShareRing will become part of the aggregator ecosystem and be listed on sites like trivago.com as well as have exclusive agreements with merchants who are listed directly on their app.
ShareRing’s USP is that they have everything on one place as well as their OneID module with means buyers can get a hotel, rent a car, rent their ski equipment, book events all through the one app and using the OneID.
With that in mind they are going to attract a lot of merchants.
This is where it gets exciting so pay attention to this part.
When a merchant is part of the ShareRing ecosystem and a buyer rents something from that merchant ShareRing will take a small % commission from that transaction. So say someone books a hotel for $100 for the night, ShareRing might take $0.50 as a commission. What ShareRing will then do is go to one of the exchanges that ShareRing (SHR) is listed on and buy SHR tokens directly using an API system using USDT.
Now, the actual commission has not been disclosed yet however if we assume even a 0.25% commission that means for every $100 Million worth of bookings made through the app will net ShareRing $250,000 which means buy backs of $250,000 for the SHR token, which increases the liquidity of SHR on the exchanges.
If you think $100 Million of bookings is a lot, booking.com customers book around 1.5 Million rooms per day, if we estimate an average of $50 per room that is $75 million of bookings PER DAY or $2 Billion worth of bookings per month.
This revenue coupled with revenue from OneID and eVOA makes ShareRing profitable almost from day one of the app going live.
OneID And eVOA
Another exciting development from the ShareRing team is the collaboration between ShareRings Self Sovereign Identity protocol and third party providers to bring OneID and eVOA which will utilise OneID
With the huge rise in E-commerce and with over 2.82 billion people who now own a smartphone we are entrusting our personal information to more and more centralised entities. These entities are frequently hacked and our information is leaked to outside parties.
ShareRing aims to tackle this with their service OneID module.
ShareRing’s OneID solution protects users' data by handling Know Your Customer (KYC) information through third parties and ShareRing’s Self Sovereign Identity Protocol. ShareRing does not hold any identifying information anywhere on its servers. It provides the ultimate security for the renter and also the provider, as the Protocol encrypts and stores your data in a secure manner within your device. Essentially, this means that it is near impossible for a hack or data leak to happen, simply because there is no centralized server of data for hackers to exploit.
The OneID module is very easy to use. The end-user needs to complete their ID submission only once, with the entire submission process requiring less than two minutes to complete. Once this step has been completed, the customers KYC is destroyed by the 3rd party document verification system and the OneID module allows merchants to verify a customer’s identity via a hashed verification packet, stored on the users device and ShareLedger. This removes the need for merchants to store or see personal information; safeguarding both merchants and users from fraud.
To create your ShareRing OneID, simply:
  1. Take a picture of your government ID document
  2. Take a selfie
  3. Confirm and submit your details
This is something I am really excited about for ShareRing and they already have made partnerships for other companies to use this feature which is another income stream for ShareRing.
eVOA
E-Visa On Arrival allows applicants to apply online and receive a travel authorisation before departure – this eVOA can be shown at dedicated Thailand immigration counters on arrival at major Thailand airports, allowing travellers to pass through in minutes.
OneID system is scheduled to become the lynchpin technology in Thailand’s electronic Visa On Arrival (eVOA) system; one of only two companies to partner with Thai authorities to provide this service. The new Visa system eliminates much of the hassle involved in entering the country:
This is a strong validation of the OneID system - immigration controls are some of the most scrutinized processes in any branch of government, and if the OneID solution can operate to their standards then it is truly business-ready. As explained by our COO, Rohan Le Page:
“We are providing our OneID product for Thailand e-VOA (Visa On Arrival) that allows 5 Million travellers from 20 countries including China and India to complete the visa process on their mobile through our app. This provides a streamlined immigration process that negates the need for an expensive and time-consuming process when you get off the plane. Additionally, fraud is mitigated with several extra layers of security in the back end including our blockchain (ShareLedger) consensus model that makes all data immutable and all but impossible to hack.”
Profit Margins on OneID
So how does ShareRing make money from OneID and eVOA?
With each application for an eVOA using the OneID module ShareRing will make an undisclosed commission. The e-VOA is available to citizens of 21 different countries and is intended for those who will be holidaying in Thailand and not working in the country.
This means that each eVOA will last for a period of around 15 days which effectively means that ShareRing will get commission multiple times from each person travelling to one of the 21 countries listed below:
Andorra, Bhutan, Bulgaria, China, Ethiopia, Fiji, India, Kazakhstan, Latvia, Lithuania, Maldives, Malta, Mauritius, Papua New Guinea, Republic of Cyprus Romania, San Marino, Saudi Arabia, Taiwan, Ukraine, Uzbekistan
The profits on this alone, according to projections, are worth millions of dollars per year to ShareRing, with a healthy growth of about 35% in raw profit over the next 5 years, ultimately netting the company about $1.5 million profit per quarter.
The ShareLedger Blockchain Platform
ShareRing will utilize the registered intellectual property from the existing KeazACCESS framework (KEAZ: A car sharing company founded by Tim Bos) as well as improving it the blockchain experience in their team.
It will consist of fo the primary elements:
SharePay (SHRP) – SharePay is the base currency that will allow users of the ShareRing platform to pay for the use of third party assets. ShareToken (SHR)
ShareToken (SHR) is the digital utility token that drives sharing transactions to be written to the ShareRing ledger that is managed by the ShareRing platform.
Account – This will be a standard account, which such an account being represented by a 24-byte address. The account will contain 4 general fields:
SHRP – SharePay token balance
SHR – ShareToken balance
ASSETS – linked/owned by the account (see below for definition of an Asset) ATTRIBUTES – Any additional attributes that are associated with this account. These attributes may be updated or added by Sharing Economy providers that utilise the ledger such as ID checks by rental companies. These attributes may be ‘global’ (i.e. used by any sharing providers) or ‘local’ (i.e. used by a specific sharing provider).
Assets – An asset represents a tangible real-world or digital asset that is being shared, such as a car, a house, industrial machinery, an e-book, and so on.
Smart Contracts – Similar to a number of other blockchain platforms, such as Ethereum and NEO, the ShareLedger blockchain will feature highly customisable smart contracts. These Smart Contracts will allow for decentralised autonomous applications that can be attached to an asset and/or account. Every smart contract will be Turing complete, meaning it will have the ability to implement sophisticated logic to manage the sharing of the assets. The smart contracts will be tested and reviewed by ShareRing in a sandbox as well as audited by reputable third-party code auditors prior to implementation.
Proof of Stake Consensus
ShareRing have chosen the Leased Proof-of-Stake protocol as the consensus algorithm for ShareLedger. This choice is based on the practicality and security benefits evident in the Waves platform. It is also much more cost effective than Proof-of-Work (POW), and will not suffer from the current issues Bitcoin and other POW cryptocurrencies are facing such as scalability and electricity consumption.
The ShareRing App
At the heart of the ShareRing project lies the ShareRing app:
A universal ‘ShareRing’ app is being developed that will allow anyone to easily see and use any sharing services around them. Each partner will have the option of developing a ‘mini’ app within the ShareRing app that will have functionalities specific to that partner. The app will use geolocation-based services to display the ShareRing services that are nearby
Social Media Presence
Coming from a social media background I feel this is an extremely important area to look into, especially in the crypto world.
ShareRing has done an okay job in growing their social media presence however I feel it could be much better. Here is a look at some of the key stats for their online social media presence:
Youtube: 191 Subscribers Instagram: 238 Followers Linkedin: 376 Followers Telegram: 6,525 members (very active) Twitter: 2,216 Followers (Fairly regular updates) Facebook: 1,965 Followers
Whilst social media may not be a priority just now I feel there has to be a big presence with image-based platforms and video-based platforms. Youtube and Instagram should be made a priority here as it spans all generations:
Other News on ShareRing
There is a lot of stuff going on at the moment with ShareRing which is what makes it an exciting prospect. Rather than give information on each of them here are some highlights provided by the ShareRing team.:
- ShareRing's revolutionary ID management based module OneID.
- Worlds first Blockchain based eVOA in place with major Thai company targeting 5 to 10 million travellers from 20 countries.
- 2.6 million International Hotels/ Accommodation coming on to the Platform. Lots more to come!
- Partnership with HomeAway
- 200,000 Activites, Tours and Events added to the ShareRing App
- Multi Global Car Sharing Partnerships
- 1 Partner Directly Integrating SHR's OneID consisting of 1.2 million Vehicles across 150 Countries
- Luxury Car Brand Sharing Platform purely based on SHR
- SHR payment system SHRP available in 10% Taxi Terminals in Australia
- SHRP available in 10,000 EFTPOS Terminals Australia wide
- White Labelling Services incorporating ShareRings revolutionary OneID
- 20 Significant Unannounced Partnerships, more to come!
- Major Partners include -
- BYD (Largest Electric Car Maker in the World)
- DJI (Largest Drone Maker in the World)
- Keaz (300 locations around the world)
- Yogoo EV Car Sharing
- MOBI Alliance Member
Overview of Positives and Negatives
Negatives
Social Media and marketing possibly needs to be ramped up in order to bring more awareness to the project.
The roadmap and white paper has not been updated recently for 2019/2020 but this I believe is coming soon.
Positives
With a low market cap project like ShareRing the risk to reward ratio is very good for retail and institutional investors.
Technical analysis of current prices, currently at 31 Satoshi, is also very good with resistance levels at 50, 77 and 114 Satoshi which would be nearing its all time high.
Referral program will increase the numbers of users that are currently using the site.
If ShareRing can capture even a small % of the overall sharing market then success looks assured.
There are 20 new announcements coming up and with Tim Bos looking for more partnerships it seems likely that ShareRing will break ATH prices soon.
Great long term hold, in my opinion.
Realistic Expectations of ROI
Short term (4 weeks - 12 weeks)
Short term looks great for ShareRing both from a TA point of view and a fundamental point of view.
With lots of news still to come out about ShareRing there is not going to be a shortage of fundamentals to drive the price up. From a TA point of view the next line of resistance stands at around the 50 Satoshi level which would complete a massive cup and handle formation from August 24th of this year. After that we are looking at resistances of 77 and 114 to reach near the all time highs which i expect ShareRing to reach going into 2020.
Long term (6 Months - 2 Years)
If ShareRing can onboard users and keep on making partnerships at the same rate there will be no stopping it. It’s all about onboarding the users and utilising the most powerful marketing tool ever - word of mouth!
When a great app is realised with great and useful functionality then it tends to go viral and I am hoping this happens for ShareRing.
With a market cap at the moment of just under $6 Million then I don’t think it’s crazy to talk about 1000% increases in the next 2 years and I really believe that is being extremely conservative, given where we think crypto is heading as a whole.
submitted by Grills93 to CryptoMoonShots [link] [comments]

Marchero

With two cryptocurrency integrations under my belt I've set out with a solid plan for Monero.
Instead of jumping in and figuring it out as I go along I want to make sure that I have the solutions I'll need, well defined and scoped out. It's a good thing I'm going this path, too.
Turns out that there isn't really much in the way of JavaScript code for Monero out there. Probably the two best (and possibly only), solutions at the moment are monero-javascript and MyMonero.
Although there's no official Monero JavaScript library, the monero-javascript project is probably the closest to the original C++ client. This derived code comes in the form of WebAssembly, a low-level language that runs a lot closer to the metal than JavaScript. This means that WebAssembly is generally faster when doing things like calculations, but with some trade-offs like ease of use. JavaScript is a lot easier to code and understand, but it tends to run slower. In modern browsers, both run side by side so developers can decide which parts need to work fast, and which parts need to be easier to change and maintain.
The MyMonero project is actually a set of supporting libraries for a Monero wallet. It seems to have a lot more "real world" mileage but has a smaller dev team and hasn't been updated for many months, unlike monero-javascript which was updated as recently as today. MyMonero also uses WebAssembly for some of the core wallet functionality but the "bindings", or how this functionality is exposed to JavaScript, are different.
Between the two solutions, I've had more luck in getting support for monero-javascript. Neither project is well documented so having someone to run questions by is, at least at this point, a winning feature.
This will be my first time working with WebAssembly so factoring in some learning time is prudent. I'll only be learning to use existing code rather than learning how to write it but still, it's a new thing for me.
As I mentioned, support for Monero via JavaScript is surprisingly rare, so I may end up contributing some original code back to the project(s) I'll be using. I haven't yet decided which of them will find its way into CypherPoker.JS because there are still some open questions about how certain things are done and if they're even possible. However, right now monero-javascript is looking like the best choice.
Once I'm satisfied that all the building blocks are viable, I'll add the cryptocurrency handler and integrate it all the way through to the front end. As with BTC and BCH, a Monero testnet option will be available along with a faucet so that you can test it out without using any actual XMR. A full client option that uses the downloadable monerod client, the equivalent of a full Bitcoin node, will be available alongside the "light" option which will use external APIs. After that I'll upgrade the live demo (and server), update the wallet generator, post v0.5.2 code documentation, create a new release, and write a wrap-up post.
I want to stress again that this is all contingent on whether or not the JavaScript libraries actually do what I need them to do, and if there exists at least one public API that can be used in place of the daemon (monerod). But based on the help I've received from the Monero community so far I'm feeling optimistic.
Probably the most interesting thing about the Monero integration is that it represents the final, Rumsfeldian, "known unknown" of the CypherPoker.JS project. It's the last thing I'm embarking on with essentially zero prior knowledge; I know that I know nothing.
The rest of the project, the other cryptocurrencies, smart contracts, peer-to-peer communications - those are all things I'd at least had an introduction to if not outright practical knowledge of. When it comes time to add Ethereum support I'll be able to confidently say that it's nothing new. Incorporating Tor anonymization ... been there, done that.
When it comes to Monero, though, I'm a wide-eyed ignoramus. Never owned any XMR, never ran a Monero wallet, never tried out a Monero block explorer; seems I'm even getting some of the technical terminology wrong. Basically, it's the last part of the project's core vision that comes with a steep learning curve and a not-insignificant chance of failure. I mean, I don't think I'm gonna fail but I can't point to any definitive reason why I should think that.
There's no pragmatic reason to believe that March and (the) Monero (integration) will be contemporaneous but then again, why not?
submitted by monican_agent to cypherpoker [link] [comments]

Homelab collective ressources post!

Hey guys!
I'm fairly new to this sub and to having a home lab in general and I found this community to be so kind and helping, I wanted to give back what I've learned. I'm seeing a lot of questions asked around on improvements and on what to do with x extra hardware so I thought it would be nice to have a thread to regroup that.
 
I'll put here some stuff I gathered and the most common questions I've seen, feel free to contribute and i'll update the post along.
 
Latest Additions
 
Homelab Dashboard
Posts about dashboards have been growing lately and here are some of the best that were kind enough to provide us with their sources.
User Screenshot Source
yours truly http://imgur.com/a/GhCNH https://github.com/Gabisonfire/dashboard-q
lastditchefrt http://i.imgur.com/5zQdao4.png https://github.com/d4rk22/Network-Status-Page
_SleepingBag_ http://i.imgur.com/Ql9ZM4W.png https://github.com/jsank/homelabdash
NiknakSi https://niknak.org/extras/sysinfo TBA
DainBramaged http://imgur.com/jYNlUEQ https://github.com/gordonturneBigBoard
michaelh4u https://i.imgur.com/XkZwMKj.png https://github.com/michaelh4u/homelabfrontpage
spigotx http://imgur.com/a/1zMht https://github.com/spigotx/HomeLab2
SirMaster https://nicko88.com/ https://github.com/dashbad/plex-server-status
yourofl10 http://imgur.com/a/AyROa TBA
TheBobWiley http://imgur.com/a/oU6d3 https://github.com/TheBobWiley/ManageThis-LandingPages
0110010001100010 http://i.imgur.com/iwtQcsL.jpg https://github.com/danodemano/monitoring-scripts
mescon & SyNiK4L https://i.imgur.com/gqdVM6p.jpg https://github.com/mescon/Muximux
ak_rex http://i.imgur.com/a/RJkrT https://github.com/ak-rex/homelab-dashboard
 
Or build yours from scratch: PRTG API, ELK, Grafana, freeboard, JumpSquares
 
Some other resources: Custom Monitoring Scripts by 0110010001100010
 
Credits to apt64 for his original post
= Pi specific =
 
= Download Automation =
 
= Virtualization =
 
= Monitoring =
 
= Media Center =
 
= Remote access =
 
= VOIP =
 
= Networking =
 
= File Servers/Storage/RAID =
 
= Cameras =
 
= Documentation =
 
= Dynamic DNS =
 
= Backup =
 
= Creating network diagrams =
 
= Guides =
 
= Misc =
 
That's all I could come up with on top of my head + some research, passing over to you guys so we can get a nice complete list!
 
Let's try and stick with free(or mostly) softwares, let me know if you guys feel otherwise.
submitted by Gabisonfire to homelab [link] [comments]

BiblePay Evolution - What is it?

Quote from: togoshigekata on March 16, 2019, 02:00:02 PM BiblePay is a fork of the Dash code, our code started out as some version of the Dash coin code, but we havent included (merged in) all the latest Dash code changes (we have had our own developments and only merged in security things)
Dash has released a few new updates called Dash Evolution, and Rob is [adding] those into BiblePay A little more technical, I believe Rob [starting] with the latest Dash code, and then [putting] all the BiblePay stuff inside of it Quote from: bible_pay on March 16, 2019, 02:52:17 PM
Yes, this is exactly right, BiblePay Evolution is going to be our next version, and it includes all the features of Dash Evolution
- deterministic sanctuaries - chainlocks - non-financial transactions - atomic trade - lightning support - daaps - decentralized api - segwit - all the new DIPS - all the latest bitcoin commits for security - all the stuff that happened over the last year in Dash - the Depends system for devs - c++14 source code - new compiler support - easier building
Lots of good things to be a base from. And we do whats called a "re-base", meaning we merge our biblepay code into Evolution, and offer a new release.


Some Dash Evo Documentation https://docs.dash.org/en/latest/introduction/features.html#evolution https://dashcrypto.org/technology/dash-evolution/ https://github.com/dashpay/dash/blob/v0.13.0.0/doc/release-notes.md
Dash Roadmap https://www.dash.org/roadmap/
Dash Paper v13 https://issuu.com/dash-coin/docs/dashpaper-v13-v1 (Read by Amanda B Johnson?: https://www.youtube.com/watch?v=tfBAsxh6H50)
Dash DIPs (Dash Improvement Proposals) https://github.com/dashpay/dips

Dash Releases Evolution's Foundation in Largest Upgrade Ever by Amanda B Johnson https://www.youtube.com/watch?v=tLInZDCIdEo
Dash To Become Immune to 51% Attacks https://www.youtube.com/watch?v=EDIfxfjbpkA

TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts) https://forum.biblepay.org/index.php?topic=391.msg5518#msg5518
Generic Smart Contracts https://wiki.biblepay.org/Generic_Smart_Contracts
BiblePay Roadmap https://wiki.biblepay.org/Roadmap

Quote from: bible_pay on April 07, 2019, 07:19:19 AM
With the release of BiblePay-Evolution coming in 60 days, I thought this would be a good time to:
  1. Demonstrate our differences - and explain how/why we are Superior to other cryptos
  2. Compare BiblePay to a potential slot in the Top 100 (I see that our features rank us somewhere between #70 and #100, but I will make a case for #26 once Evolution is released - see chart column D features to achieve #26)
  3. Show exactly where we expect this feature to fit in our release schedule (note that most of these features are being tested in Evo, and only some are held back for Dec 2019 and Dec 2020).
  4. Show our progress over time - how our decisions evolved that resulted in constant improvements to our core platform over time. See on this matrix how we have transcended from problematic in certain areas, with responsible improvements addressing the problems, and finally releasing a good and permanent solution (See Chart #2).
In the First Chart, (Nutritional Info Guide), you can see some of BiblePay's advanced features. These are things that are not in other communities wallets. Obviously over the last 2 years, some features have been removed, but its clear that a significant amount of our code has withstood the test of time and has survived the transition to Evo and is useful to the community.
The in-wallet bible reader, the decentralized GSC creatovoter, our persisted data storage cache (for prayers, campaigns and points), our anti-gpu and upcoming ABN feature, etc. The wallet is changing again in it's foundation, to provide new interfaces and abstraction layers (as Q3 approaches) so we will have the base to add our extended UI (HTML5) for example for the features to the far right in the chart.
I also provide a key of definitions for anyone that is not familiar - or if you think we need more explanation for a term. Please don't hesitate to ask for definitions to be added, and I will modify the wiki!
Finally at the bottom of the page, please see the detail table demonstrating how we have evolved in a positive way. This shows that we have taken into consideration everything complaints in production (for example, improving Prod reliability as you can see is #1 in paramount importance, anti-fork technology is prioritized to #2, etc). You can also see that all the work we did in 2018 has not been wasted and that what we learned about botnets and POBH is also still present and has evolved for this next release.
Nutritional Information Guide: https://wiki.biblepay.org/Nutrition_Information

Quote from: bible_pay on April 16, 2019, 08:58:32 AM
I spoke to RattleR at GIN today and he confirmed they have upgraded their platform to handle Deterministic Sanctuaries (Evolution).
So this is a positive thing for us as we will not be hindered while transitioning.
GIN Masternode Hosting: https://p.ginplatform.io/#!/

Quote from: bible_pay on April 09, 2019, 07:08:31 AM
I realize we have been through an absolutely massive amount of changes and this is partially because the IT requirements list in this project has expanded beyond the original scope required for a launch and then software maintenance (even for a DAC).
But let me put your mind at ease in a couple areas. Inside the Evo release, we are no longer looking at individual requirements to fulfill an objective. We are now actually making a generic extensible abstraction layer that I believe can handle all of the DAC requirements in the future. (Including decentralized orphanage contracts and Cioccolanti's integration ideas and web tipping and HTML5 and all that).
So what this means is the end is coming for continual changes (and I don't want those either, I'm on board with this). The other very large item is our change to be rebase proof that is coming. Starting in Evo, we are going to release code in a way where we continually honor Dash's future prod commits as they commit also (meaning this will future proof biblepay).
Regarding the actual content you do have a say. Please join us in the testnet thread and test Evo and paste wishlist items. I want Evo to be easy to use for everyone + Grandma.
Finally, even though Evo looks daunting because of acronyms, we are still going to create a dashboard for Grandma towards the end of the cycle so you can drive Evo like a normal car.

Quote from: togoshigekata on April 17, 2019, 07:14:08 PM
BiblePay Forum - TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts) https://forum.biblepay.org/index.php?topic=391.0
Github - BiblePay Evolution https://github.com/biblepay/biblepay-evolution
Quote from: bible_pay I'm starting to add some documentation to explain to new users how to get started:
Getting started with Evolution: https://wiki.biblepay.org/Getting_Started_with_Evolution
GSC's: https://wiki.biblepay.org/Generic_Smart_Contracts
Healing Campaign: https://wiki.biblepay.org/BiblePay_Healing_Campaign
Street Healing: https://wiki.biblepay.org/Street_Healing
Spiritual Warfare: https://wiki.biblepay.org/Spiritual-Warfare-I
I realize we need a specific section for Grandma also - I'll continue to refine the getting started guide.
Please let me know if anyone would like to see more expanded info on any of these, and/or if this is sufficient to call us "easy to use" with the release of Evo.

Reference: https://bitcointalk.org/index.php?topic=2388064.msg50692748#msg50692748
submitted by togoshige to BiblePay [link] [comments]

11 Ways to Earn Bitcoins & Make Money with Bitcoin - YouTube Building a Bitcoin Price Tracking Python Script using the Luno API Bitcoin NodeJS Part 1 - Hello World Bitcoin: Beyond The Bubble - Full Documentary - YouTube KenFM - YouTube

Query API Plaintext query api to retreive data from blockchain.info. Some API calls are available with CORS headers if you add a &cors=true paramter to the GET request Please limit your queries to a maximum of 1 every 10 seconds. All bitcoin values are in Satoshi i.e. divide by 100000000 to get the amount in BTC. Real-Time. getdifficulty - Current difficulty target as a decimal number ... Our bitcoin payment API returns a simple JSON document for you to handle on your server however you would like. Low Fees In order to continue to keep our bitcoin payment gateway API online, we take a 1% commission. CoinDesk provides a simple and free API to make its Bitcoin Price Index (BPI) data programmatically available to others. Find out how to use it here. Bitcoin puts the current compact-format target and the arbitrary-precision "extraNonce" number there, which increments every time the Nonce field in the block header overflows. Outputs can be anything, but Bitcoin creates one exactly like an IP address transaction. The extranonce contributes to enlarge the domain for the proof of work function. Miners can easily modify nonce (4byte), timestamp ... Introduction¶. The Developer Reference aims to provide technical details and API information to help you start building Bitcoin-based applications, but it is not a specification.To make the best use of this documentation, you may want to install the current version of Bitcoin Core, either from source or from a pre-compiled executable.. Questions about Bitcoin development are best asked in one ...

[index] [45304] [2634] [34771] [38207] [17129] [45800] [48920] [38066] [33374] [30722]

11 Ways to Earn Bitcoins & Make Money with Bitcoin - YouTube

KenFM ist ein freies Presseportal, eine Nachrichtenplattform, die bewusst das Internet als einziges Verbreitungsmedium nutzt und damit im gesamten deutschspr... Thanks for watching! For donations: Bitcoin - 1CpGMM8Ag8gNYL3FffusVqEBUvHyYenTP8 شرح API Documentation شرح API specification شرح API definition و توضيح الفروق بنهم Qu'est-ce que le bitcoin, pourquoi faut-il s'y intéresser ? 🤔 L'ACTUALITÉ, TOUS LES JOURS SUR INSTAGRAM : http://instagram.com/hugodecrypte/ L'ACTUALITÉ TOUS... Thanks to Away for sponsoring this video! Go to https://www.awaytravel.com/techquickie and use promo code techquickie to get $20 off your next order! Bitcoin...

#