Prometheus exporter for monitoring statistics of Bitcoin

Part 2: A great tip for Brazilians, Venezuelans and other nationalities which choose to play Tibia as their main income

Hello,
I have gotten so many replies and messages since my last post in this thread, that I can't answer them all individually. Previous topic:
https://www.reddit.com/TibiaMMO/comments/h8tu5u/a_great_tip_for_brazilians_venezuelans_and_othe
It has been shared on multiple subreddits so I have no idea where to even post this. But I'd like to come up with a follow-up thread with some more information. The internet is the most powerful tool that mankind has ever invented. You have the ability to reach thousands, millions and even billions of people with just a computer and some internet access.
If you're on this subreddit, chances are you're already playing Tibia and you already have a computer and internet access. It doesn't need to be the best internet, but as long as websites will load (eventually) you are good to go.
In this topic I will go more in-depth on web development and software engineering. If you have a very slow internet connection, you may want to look into web development instead of software development. An application/software is much heavier (larger file size) than a website. And most developer jobs require that you send and download files, back and forth, between you and your company's server. So if you feel like your internet is too slow to send a lot of files - do not worry! There are plenty of jobs.
First, I will go through some more details on how to learn web development and software development. After that, I will list a few other kinds of jobs that you can do remotely. These types of jobs can be done from anywhere in the world as long as you have internet access.

Part 1: Some languages you should learn
What is web development? Well, it can be a lot of things. You perhaps make websites for shops/restaurants/hair dressers/dentists, or you work for a big company and work on their web application, like Outlook, Discord or Spotify (which can all be accessed via a browser: their web app). You can also work with design and user experience, instead of programming. Being a web developer can mean so many different things, it's impossible to name them all. But most web developers are just developers: they program. They make websites, and they either sell the websites to companies (as a consultant) or you work full/part-time for a company.
I can not provide in-depth information about every single thing, but I can give you some pointers. The very basics any web developer should know is this:

Part 2: Technologies and useful tools
To become a web developer you will need a few tools. You need a text editor, a FTP client, a SSH client and some other things. Also a good browser.

Other things you may want to look into:
Web services, SSL certificates, Search Engine Optimization, Databases, API, Algorithms, Data Structures

Part 3: Learning platforms

If you want to learn in-depth about algorithms, data structures and more. Then you can take a look at the curriculum of the top-tier universities of USA. Such as: UC Berkeley, Harvard and MIT. These courses are very hard and are specifically for people who want to become experts in software engineering. You can enroll some of them for free, like the one on Harvard. And by having a such diploma (which costs $90 extra) can get you a lot of job opportunities. You can enroll those courses if you want, but it can have a fee. But just take a look at what they are studying and try do their exercises, that is 100% free. Get the knowledge. It's mostly on video too! These course below are the very same courses that many of the engineers at Facebook, Google, Amazon, Apple, Netflix, Uber, AirBnb, Twitter, LinkedIn, Microsoft, etc. has taken. It's what majority of people in Silicon Valley studied. And it's among the best classes that you can take. These course are held by some of the world's best professors in IT.

UC Berkeley: CS 61a & CS 61b:

Harvard University: CS50 (free enrollment --- 90$ to get a certificate).

MIT (Massachusetts Institute of Technology): 6.006

Part 4: Finding jobs
Portfolio / Code Sharing / Source Control:

Part 5: Other types of jobs you can work with (remotely) - with/without coding experience

You can find information about all of the things I have mentioned by using YouTube or Google search.
Hope it helps.

And I hope that in 1 year, there will be at least some new web developers in Brazil, Venezuela and other countries in South America.
submitted by International-Unit-8 to TibiaMMO [link] [comments]

LIVESTREAM today (Saturday) at 4:00pm UTC: Always wanted to become a Script developer? Bored b/c Corona? See you at 4:00pm then where I'll release Iguana, the new pretty & powerful Bitcoin Cash Transaction debugger, as well as the new handy bitcoin-cash crate for Rust!

LIVESTREAM today (Saturday) at 4:00pm UTC: Always wanted to become a Script developer? Bored b/c Corona? See you at 4:00pm then where I'll release Iguana, the new pretty & powerful Bitcoin Cash Transaction debugger, as well as the new handy bitcoin-cash crate for Rust!
Link to the stream at 4:00pm UTC: https://www.youtube.com/watch?v=ivy9lkiPwOM
Picture of the newly released Iguana Debugger:
isn‘t it pretty?
I‘ve been able to publish the following pieces of software:
Docs are still lacking, but I will update them in due time. All opcodes are well documented already.
Due to popular demand, I will also host a livestream on YouTube (https://www.youtube.com/watch?v=ivy9lkiPwOM, 4:00pm UTC):
  • I‘ll walk you through setting up the development environment on a new machine (on Windows 10, because it‘s THE WORST use linux or mac guys ), i.e. Visual Studio Build Tools, Rust, VSCode and rust-analyzer.
  • I‘ll setup a small project with the bitcoin-cash crate and connect it with the Iguana UI.
  • I‘ll briefly explain how Script works by toying around with some opcodes.
  • I‘ll then actually get work done and implement the simplest contract of CashNumbers (the one that creates the NFT1 child token), which demonstrates a real world example.
Now more than ever would be a great time to develop new skills, and with the new tools I‘ve just published, that‘ll be easier than ever.
You‘re welcome to join and ask questions. There are no dumb questions (Script is a pretty unexplored territory tbh) as long as they are on the topic!
Donations are welcome: bitcoincash:qqcj96s449qmxhzrmvmpewynswpze2d72c0kvlkz9e
submitted by eyeofpython to btc [link] [comments]

Start learning programming " Here is the best Platforms for you"

Step by step Help for you:
Platforms Node.js Frontend Development iOS Android IoT & Hybrid Apps Electron Cordova React Native Xamarin Linux ContainersOS X Command-Line ScreensaverswatchOS JVM Salesforce Amazon Web Services Windows IPFS Fuse HerokuProgramming Languages JavaScript Promises Standard Style Must Watch Talks Tips Network Layer Micro npm Packages Mad Science npm Packages Maintenance Modules - For npm packages npmAVA - Test runner ESLintSwift Education PlaygroundsPython Rust Haskell PureScript Go Scala Ruby EventsClojure ClojureScript Elixir Elm Erlang Julia Lua C C/C++ R D Common Lisp Perl Groovy Dart JavaRxJava Kotlin OCaml Coldfusion Fortran .NET PHP Delphi Assembler AutoHotkey AutoIt Crystal TypeScriptFront-end Development ES6 Tools Web Performance Optimization Web Tools CSS Critical-Path Tools Scalability Must-Watch Talks ProtipsReact RelayWeb Components Polymer Angular 2 Angular Backbone HTML5 SVG Canvas KnockoutJS Dojo Toolkit Inspiration Ember Android UI iOS UI Meteor BEM Flexbox Web Typography Web Accessibility Material Design D3 Emails jQuery TipsWeb Audio Offline-First Static Website Services A-Frame VR - Virtual reality Cycle.js Text Editing Motion UI Design Vue.js Marionette.js Aurelia Charting Ionic Framework 2 Chrome DevToolsBack-end Development Django Flask Docker Vagrant Pyramid Play1 Framework CakePHP Symfony EducationLaravel EducationRails GemsPhalcon Useful .htaccess Snippets nginx Dropwizard Kubernetes LumenComputer Science University Courses Data Science Machine Learning TutorialsSpeech and Natural Language Processing SpanishLinguistics Cryptography Computer Vision Deep Learning - Neural networks TensorFlowDeep Vision Open Source Society University Functional Programming Static Analysis & Code Quality Software-Defined NetworkingBig Data Big Data Public Datasets Hadoop Data Engineering StreamingTheory Papers We Love Talks Algorithms Algorithm Visualizations Artificial Intelligence Search Engine Optimization Competitive Programming MathBooks Free Programming Books Free Software Testing Books Go Books R Books Mind Expanding Books Book AuthoringEditors Sublime Text Vim Emacs Atom Visual Studio CodeGaming Game Development Game Talks Godot - Game engine Open Source Games Unity - Game engine Chess LÖVE - Game engine PICO-8 - Fantasy consoleDevelopment Environment Quick Look Plugins - OS X Dev Env Dotfiles Shell Command-Line Apps ZSH Plugins GitHub Browser Extensions Cheat SheetGit Cheat Sheet & Git Flow Git Tips Git Add-ons SSH FOSS for DevelopersEntertainment Podcasts Email NewslettersDatabases Database MySQL SQLAlchemy InfluxDB Neo4j Doctrine - PHP ORM MongoDBMedia Creative Commons Media Fonts Codeface - Text editor fonts Stock Resources GIF Music Open Source Documents Audio VisualizationLearn CLI Workshoppers - Interactive tutorials Learn to Program Speaking Tech Videos Dive into Machine Learning Computer HistorySecurity Application Security Security CTF - Capture The Flag Malware Analysis Android Security Hacking Honeypots Incident ResponseContent Management System Umbraco Refinery CMSMiscellaneous JSON Discounts for Student Developers Slack CommunitiesConferences GeoJSON Sysadmin Radio Awesome Analytics Open Companies REST Selenium Endangered Languages Continuous Delivery Services Engineering Free for Developers Bitcoin Answers - Stack Overflow, Quora, etc Sketch - OS X design app Places to Post Your Startup PCAPTools Remote Jobs Boilerplate Projects Readme Tools Styleguides Design and Development Guides Software Engineering Blogs Self Hosted FOSS Production Apps Gulp AMA - Ask Me Anything AnswersOpen Source Photography OpenGL Productivity GraphQL Transit Research Tools Niche Job Boards Data Visualization Social Media Share Links JSON Datasets Microservices Unicode Code Points Internet of Things Beginner-Friendly Projects Bluetooth Beacons Programming Interviews Ripple - Open source distributed settlement network Katas Tools for Activism TAP - Test Anything Protocol Robotics MQTT - "Internet of Things" connectivity protocol Hacking Spots For Girls Vorpal - Node.js CLI framework OKR Methodology - Goal setting & communication best practices Vulkan LaTeX - Typesetting language Network Analysis Economics - An economist's starter kit
Few more resources:
submitted by Programming-Help to Programming_Languages [link] [comments]

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

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

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

Prizes for winning infographics.

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

Prizes for sharing and giving feedback!

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

Your Goals

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

Our Criteria to Judge

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

How do you win?

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

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

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

Resources

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

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

25/09/18 - First Round of Feedback

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

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

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

Timeline

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

Achievements

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

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

submitted by benohanlon to komodoplatform [link] [comments]

Kin Community FAQ, Guidelines, & Ecosystem Directory

Kin Community FAQ, Guidelines, & Ecosystem Directory
Kin FAQ
  1. What is Kin?
  2. Where can I earn & spend Kin?
  3. Where can I buy Kin?
  4. Where can I store Kin?
  5. Why is the total supply so large?
  6. Why isn't Kin on [xyz] exchange? When will it be?
  7. Is there any update on [Y] announcement? Can you speak on [insert rumor here]? When will we be able to do [Z]?
  8. How can I contact the developers / support staff of [insert app name here]?
  9. How can I contact the Kin Foundation?
  10. How can I track transactions on the Kin blockchain?
  11. I still have ERC-20 based Kin (on the Ethereum blockchain), how can I migrate?
  12. I heard the SEC is suing Kik, is that true? What does it mean for Kin?
  13. How was Kin distributed at launch and how does it enter circulation?
  14. I want to integrate Kin into my software project. How do I get started? Where is the developer community?
  15. How can I keep up with the latest developments in Kin?
1 - What is Kin?
Kin is money for the digital world. It can be earned and spent across an entire ecosystem of applications, thanks to the blockchain. If you don’t know what that means, don’t worry; you don’t have to. Kin is designed to be accessible by a broad mainstream audience- computer science degree not required. By bringing together developers and users of all kinds to build in a shared new digital economy, we can create a more fair playing field; one in which the developers and content creators that build these virtual realities are rewarded based on their contributions, not harvested for their personal data and attention against their will. If you’d like to learn more about Kin, here are some resources to get you started:
· Kin Website: https://www.kin.org/
· Kin Whitepaper: https://www.kin.org/static/files/Kin_Whitepaper_V1_English.pdf
· The Vision for Kin: https://medium.com/kinblog/the-vision-for-kin-6ee048a3a979
· Announcement of Kin: https://www.youtube.com/watch?v=5le2n230oTk
· Introduction to Kin (by u/kyzermf): https://medium.com/hackernoon/introduction-to-kin-universal-virtual-currency-for-apps-ea6464225ffc
2 - Where can I earn & spend Kin?
Kin is going live in a growing number of apps. To see which ones, you can check out the Ecosystem Directory below, or keep up with some of these resources:
· via Kin Website: https://www.kin.org/kin-apps/
· Apps with Kin (by u/Neliss31) https://appswithkin.com/index.php
· Kin Appz (by u/hepays) https://www.kinappz.com/
3 - Where can I buy Kin?
In addition to the ecosystem of apps available to earn Kin, you can also purchase it in larger amounts. It is currently available for purchase on cryptocurrency exchanges listed here:
· CoinMarketCap Exchanges List for Kin https://coinmarketcap.com/currencies/kin/#markets
Note that these are independent organizations and therefore only they can provide guarantees on customer service and experience, please do your due diligence in navigating and utilizing these exchanges. Also note that cryptocurrencies are inherently volatile, trade at your own risk. Kin is money for the digital world, not a stablecoin.
4 - Where can I store Kin?
While using Kin inside of apps, make sure to create a backup of your wallet when possible. It is not recommended that you store large amounts of Kin in your user wallets, and instead seek out a more robust solution. There are lots of subtle differences to the kinds of wallets and how to use them, including trade-offs in security vs convenience. Make sure to do your research and be careful when handling your hard-earned Kin:
Offline (“Cold”) Storage:
· My Kin Wallet https://www.mykinwallet.org/
· Guide: Creating A Paper Wallet for Storing Your Kin Safely Offline (by u/TheRealChaseEB) https://www.reddit.com/KinFoundation/comments/bylk0creating_a_paper_wallet_for_storing_your_kin/
Hardware Wallets:
· Ledger Hardware Wallets (works with My Kin Wallet) https://www.ledger.com/
Software Wallets:
· Trust Wallet (Mobile) https://trustwallet.com/
· Atomic Wallet (Mobile & Desktop) https://atomicwallet.io/
· Guarda Wallet (Mobile & Desktop) https://guarda.co/
· Magnum Wallet (Web) https://magnumwallet.co/
5 - Why is the total supply so large?
Kin is meant to be transacted by a large number of users in manageable denominations, just like physical money.
6 - Why isn’t Kin on [xyz] exchange? When will it be?
A healthy market for developers and users is essential to all stakeholders who want to build a vibrant economy around Kin as a currency. That said, a number of blockers have prevented further listings from happening; for example we needed to first have a unified & functional product and underlying technology before pursuing secondary markets. In addition to this there has been regulatory uncertainty surrounding the listing of digital assets in the United States including Kin specifically, especially since the filing of a misleading legal complaint by the US SEC. Due to this, the Kin Foundation is pressing on in other markets on behalf of the ecosystem to try and facilitate more platforms for everyone to buy & use Kin in their different ways. We do not know when Kin will be listed on exchanges, and anyone who does cannot say due to legal and security agreements.
7 - Is there any update on [Y] announcement? Can you speak on [insert rumor here]? When will we be able to do [Z]?
While we believe in maintaining the utmost transparency wherever possible, we will typically announce things as they are ready and report on progress as it becomes pertinent, as to not create unfounded hype and adhere to internal strategies. While it might be tempting to seek constant updates, please remember that answering questions takes time, and everyone is busy working hard to actually build the things we are all excited to see. We will do our best to keep everyone updated on the things they care about. We do not comment on rumors and we may be constricted in our ability to communicate at any given moment on ongoing internal affairs that may fall within certain legal or strategic confines.
8 - How can I contact the developers / support of [insert app name here]?
Please refer to the Kin Ecosystem directory below.
9 - How can I contact the Kin Foundation?
You can email us at [[email protected]](mailto:[email protected]) , or if you’d like to DM a specific representative or discuss something in an open setting you can also reach out to us and the community here.
Here are some relevant contacts that represent Kin Foundation,Kin Tel Aviv, & Kin San Francisco in the community:
Community u/benji5656
Communications u/kevin_from_kin
Developer Experience (Kin.org, Kin SDK, and Kin Developer Program) u/therealchaseeb
Blockchain (Core infrastructure of the Kin Blockchain) u/gadi_sr
Ecosystem (High touch integrations with mature developers) u/rinatbogin
KRE (The incentive protocol that drives the growth of the ecosystem) u/oradwe
UX Research u/YonatanDub
Kin San Francisco u/matty_hibs
10 - How can I track transactions on the Kin blockchain?
Here are some resources for monitoring the blockchain:
· via Kin Website https://www.kin.org/blockchainExplorer
· Kin Explorer (by u/Chancity) https://v2.kinexplorer.com/explorer
· Kin Bubbles (by u/kidwonder) https://kin-bubbles.herokuapp.com/
· Kin Transaction Visualizer (by u/sednax) http://bitcoin.interaqt.nl/kin.html
11 - I still have ERC-20 based Kin (on the Ethereum blockchain), how can I migrate?
Follow the directions laid out here: https://www.kin.org/migration/
12 - I heard the SEC is suing Kik, is that true? What does it mean for the Kin Foundation?
It’s true. After cooperating with an investigation and multiple attempts to reach an amicable settlement, the SEC filed a disparaging and mischaracterized complaint against Kik for not registering the initial sale of Kin as a security offering. Kik is fighting back. They are in a unique position to take on this case, however, unlike the initial Wells Notice, the Kin Ecosystem Foundation is not named in the complaint.
As noted by the Blockchain Association:
When we look at the Kik investigation, we can tell from the Wells Notice that the SEC originally looked at both Kik Interactive and the Kin Foundation. However, when the complaint was issued, it only focused on the offering of Kin in the September 2017 token sale, not Kin in the ecosystem today. The fact that the SEC investigated the Kin Foundation, but decided not to pursue a complaint is good news for developers, platforms, and others in the ecosystem who use these tokens because it separates the question of the token sale from the activities in the ecosystem since then. ("What the SEC-Kik complaint didn’t cover — and why this is good news for the crypto community")
As the legal battle rages on, the foundation will help Kik to amplify their defense as they correct the record publicly; but also focus on the development of the ecosystem which will continue beyond the SEC battle regardless. Expect ongoing updates as the fight continues to unfold publicly.
**Update**: - Kik has put together DefendCrypto, a fund dedicated to legal initiatives that benefit the cryptocurrency industry, so that companies that don't have the same resources can stand up against unfair regulation in fights of their own. Visit DefendCrypto.org to learn more and join the fight to defend innovation and participation in the cryptocurrency industry in the United States.
- Kik Answers SEC Complaint: https://www.prnewswire.com/news-releases/kik-answers-sec-complaint-300897681.html?tc=portal_CAP Kik has filed and published a 130 page, paragraph-by-paragraph refutation of the SEC's allegations.
- Additional Resources: Interview w/ Eileen Lyon, General Counsel and Chief Compliance Officer at Kik https://medium.com/kinblog/kin-foundation-asks-interview-w-eileen-lyon-general-counsel-and-chief-compliance-officer-at-kik-bbcf3b7a6961
13 - How was Kin distributed at launch and how does it enter circulation?
The Kin Foundation sold 1 trillion (10% of total supply) in a token distribution event in September 2017 that was split between a pre-sale (487.80 billion sold) and a public sale (512.20 billion sold). Half of the tokens sold during the pre-sale (244 billion) are subject to a one-year lock-up period. Kik received 3 trillion tokens (30% of total supply), which vested at a rate of 300 billion tokens quarterly for 10 quarters, and the Kin Foundation received 6 trillion (60% of total supply). The Kin Foundation tokens will be distributed through the Kin Rewards Engine, which divides the allocation between network participants and marketing and operational costs for the Kin Foundation (6 trillion Kin has been split into 4.5 trillion for network participants, and 1.5 trillion for marketing and other operational costs of the Kin foundation). Kin Foundation tokens for network participants are schedule to be distributed to the network at a rate of 20% of the remaining balance per year.
To learn more about and follow along with Kin allocation, check out Kin's page below, which was published in the spirit of transparency and disclosure in collaboration with Messari:
https://messari.io/asset/kin
14 - I want to integrate Kin into my software project. How do I get started? Where is the developer community?
Check out these developer resources!
Website: https://www.kin.org/developers
Documentation: https://docs.kin.org/intro
Android Tutorial Series: https://medium.com/kinblog/kin-android-development-tutorial-part-i-introduction-to-kin-83b21834a27e
Unity Tutorial Series: https://medium.com/kinblog/building-a-kin-powered-app-with-unity-cf8deef56bdb
Developer Communities: Kin Foundation Developer Forums: https://kindevforum.kin.org/ Kin Foundation Developer Discord: https://discordapp.com/invite/JavjKSx
Implementing Kin in PHP, Ruby, Javascript, Go, and 51+ Other Languages (by u/sednax): https://medium.com/@luc.hendriks/implement-kin-in-php-javascript-ruby-go-and-51-other-programming-languages-c7ae616de700
15 - How can I keep up with the latest developments in Kin?
Sign up for the Kin Newsletter here: https://ecopartners.kin.org/newsletter_signup
This subreddit also serves as a civil space for community to share and discuss developments.
Forum Rules & Guidelines
Purpose of the Forum
The KinFoundation subreddit is the public square for discussion and collaboration across the Kin ecosystem. It is important that we embrace the potential of the forum and foster a space where developers do not censor themselves, the curious are free to ask questions without shame, and holders are willing to collaborate on initiatives and discuss ongoing developments. For that reason, we have decided to broaden the discussion while also pinpointing fair and transparent moderation guidelines that will allow for a productive and healthy environment. This subreddit exists for the purpose of maintaining insight on what’s happening with the Kin Ecosystem, acting as a social gathering for its many participants, and mobilizing the community for things like collaborative initiatives, product feedback for developers, idea-sharing, and more.
Moderation Principles
· Transparency
All moderation actions should be guided by the principles laid out in this document and in the spirit of creating a productive and healthy environment for discussion & collaboration, although it is also understood to be iterative and subject to change.
· Objectivity
All moderation actions should be guided by a rules & practices-based approach, not one of personal judgment.
· Fairness
All moderation actions should be even-handed and based on agreeable principles that enable free but also fruitful discussion.
Code of Conduct
To participate in the public square, you must adhere to certain rules of conduct, which were created with the maintenance of productivity & civility in mind. Please review & refer to the rules here before and when posting:https://www.reddit.com/KinFoundation/about/rules/
Kin Ecosystem Directory
The Kin Ecosystem is a growing collective of independent teams, all aligned through a common incentive to build a more fair digital world. These teams build the tools, the infrastructure, and the apps that drive the reach and impact of Kin. As we continue to grow as an ecosystem, we want to make sure that the directory is maintained so that it can be a tool for everyone to use and contribute to. If you don’t see your app listed or want something changed, feel free to DM me or post here and tag me so that it can be updated. Some apps may be missing due to incomplete or inaccurate available details.
Organization -- Website -- Support / Contact--
· Bettapoint Website: https://bettapoint.com/ Contact: https://bettapoint.com/contact
· Castle Rush AR Website: https://www.darkvoodoostudios.com/castlerushar.html Contact: [[email protected]](mailto:[email protected]) (email)
· Catpurse Website: https://twitter.com/CatPurse1 Contact: [[email protected]](mailto:[email protected]) (email)
· Find (Find Travelers) Website: https://www.findtravelers.com/ Contact: [[email protected]](mailto:[email protected]) (email)
· FistBump.io Website: https://virtualbotgames.wixsite.com/fistbump Contact: [[email protected]](mailto:[email protected]) (email)
· imgvue Website: https://imgvue.com/ Contact: Contact Form
· Just Joking Website: https://kinloops.com/ Contact: See Website
· Kard Website: https://kinkard.org/ Contact: [[email protected]](mailto:[email protected]) (email)
· Kik Website: https://www.kik.com Contact: https://help.kik.com/hc/en-us
· Kimeo Website:https://kimeoapp.com/ Contact:[[email protected]](mailto:[email protected]) (email)
· Kinetik Website:https://www.kinetik.app/ Contact:[[email protected]](mailto:[email protected])
· KinFit Website:https://www.mykinfit.com/ Contact:[[email protected]](mailto:[email protected]) (email)
· Kin Foundation Website: https://www.Kin.org Contact: https://www.reddit.com/Kinfoundation
· Kinguist Website: Contact: [[email protected]](mailto:[email protected]) (email)
· Kinit Website:https://www.kinitapp.com/ Contact: [[email protected]](mailto:[email protected]) (email)
· Kinny Website: https://kinny.io/ Contact: [[email protected]](mailto:[email protected]) (email)
· Love & Loud Radio Website: https://www.loveandloudmusic.com/loveandloudradio Contact: [[email protected]](mailto:[email protected])
· Madlipz Website:https://www.madlipz.com/ Contact:https://www.madlipz.com/contact
· Matchmaker Website: Contact: [[email protected]](mailto:[email protected]) (email)
· MonkingMe Website: https://www.monkingme.com/ Contact: [[email protected]monkingme.com](mailto:[email protected]) (email)
· Nearby Website: https://www.wnmlive.com/ Contact: https://help.wnmlive.com/hc/en-us
· Pause For Website:https://pausefor.us/ Contact: [[email protected]](mailto:[email protected]) (email)
· PeerBet Website:https://peerbet.io/ Contact: [[email protected]](mailto:[email protected]) (email)
· Perfect365 Website: https://perfect365.com/ Contact: [[email protected]](mailto:[email protected]) (email)
· Photo Mail Joy Website: Contact:[[email protected]](mailto:[email protected]) (email)
· Planets Nu Website: https://planets.nu/#/home Contact:[[email protected]](mailto:[email protected]) (email)
· pop.in Website: https://pop.in/getapp Contact: [[email protected]](mailto:[email protected]) (email)
· Rave Website: https://rave.io/ Contact: https://rave.io/contact.html
· rentmole Website: https://rentmole.com/ Contact: [[email protected]](mailto:[email protected]) (email)
· Rentomania Website: http://rentomania.online/ Contact: [[email protected]](mailto:[email protected]) (email)
· RPS (Rock Paper Scissors) Website: http://www.rps.ack.ee/ Contact: [[email protected]](mailto:[email protected]) (email)
· Simple Transfer Website: https://www.kinlabs.ca/ Contact: [[email protected]](mailto:[email protected]) (email)
· Speed Genius Website: https://kinloops.com/ Contact: See website
· Step & Spend Website: Contact: [[email protected]](mailto:[email protected]) (email)
· Subti Website: https://vblago.github.io/ Contact: [[email protected]](mailto:[email protected]) (email)
· Subway Scooter Website: https://virtualbotgames.wixsite.com/fistbump Contact: [[email protected]](mailto:[email protected]) (email)
· Swelly Website: https://www.swelly.ai/ Contact: https://www.swelly.ai/#contact
· Sxlve Website: Contact:[[email protected]](mailto:[email protected]) (email)
· Syngli Website: https://www.syngli.com/ Contact: [[email protected]](mailto:[email protected]) (email)
· Tapatalk Website: https://www.tapatalk.com/ Contact: https://www.tapatalk.com/support
· ThisThat Website: https://www.thisthatapp.com/ Contact:
· Tiny Ted Website: https://www.kinlabs.ca/ Contact: [[email protected]](mailto:[email protected]) (email)
· Tippic Website: Contact: [[email protected]](mailto:[email protected]) (email)
· Trivia Clan Website: Contact: [[email protected]](mailto:[email protected]) (email)
· Trymoi Website: Contact: [[email protected]](mailto:[email protected]) (email)
· Uwe Website: https://www.uwe.ng/ Contact: [[email protected]](mailto:[email protected]) (email)
· Vent Website: https://www.vent.co/ Contact: [[email protected]](mailto:[email protected]) (email)
· Wicrypt Website: https://wicrypt.com/ Contact: [[email protected]](mailto:[email protected]) (email)
submitted by Kevin_from_Kin to KinFoundation [link] [comments]

Decred Journal – July 2018

Note: you can read this on Medium, GitHub or old Reddit to view all the links

Development

dcrd: Several steps towards multipeer downloads completed: an optimization to use in-memory block index and a new 1337 chain view. Maintenance: improved test coverage, upgrading dependency management system and preparing for the upcoming Go 1.11 release.
dcrwallet: A big change introducing optional privacy-preserving SPV sync mode was merged. In this mode dcrwallet does not download the full blockchain but only gets the "filters", uses them to determine which blocks it needs and fetches them from random nodes on the network. This has on-disk footprint of 300-400 MB and sync time of minutes, compared to ~3.4 GB and sync time of hours for full sync (these are rough estimates).
jy-p: the server side of SPV (in dcrd) was deployed in v1.2.0, the client side of SPV (in dcrwallet) is in our next release, v1.3.0. Still some minor bugs in SPV that are being worked out. There will be an update to add the latest features from BIP 157/158 in the next few months. SPV will be optional in v1.3.0, but it will become the default after we get a proper header commitment for it (#general)
Decrediton: besides regular bugfixes and design improvements, several components are being developed in parallel like SPV mode, Politeia integration and Trezor support.
Politeia: testing started on mainnet, thanks to everyone who is participating. A lot of testing, bugfixing and polishing is happening in preparation for full mainnet launch. There are also a few missing features to be added before launch, e.g. capacity to edit a proposal and versioning for that, discussion to remain open once voting starts. Decrediton integration is moving forward, check out this video for a demo and this meta issue for the full checklist.
Trezor: Decrediton integration of initial Trezor support is in progress and there is a demo.
Android: app design version 2.0 completed.
dcrdata: development of several chart visualizations was completed and is awaiting deployment. Specifically, voting agendas and historic charts are merged while ticket pool visualization is in testing.
atomicswap: @glendc is seeking reviews of his Ethereum support pull request.
Dev activity stats for July: 252 active PRs, 220 master commits, 34,754 added and 12,847 deleted lines spread across 6 repositories. Contributions came from 6-10 developers per repository. (chart)

Network

Hashrate: the month started at 40.5 and ended at 51.6 PH/s, with a low of 33.3 and a new all time high of 68.4 PH/s. F2Pool is leading with 40-45%, followed by the new BeePool at 15-25% and coinmine.pl at 18-23%.
Staking: 30-day average ticket price is 92.6 DCR (-2.1). The price started the month at 94.6 and quickly retreated to month's low of 85 until 1,860 tickets were bought within a single period (versus target 720). This pushed the pool of tickets to 41,970 (2.5% above target), which in turn caused 10 price increases in a row to the month's high of 100.4. This was the highest ticket price seen on the new ticket price algorithm which has been in effect since Jul 2017. Second half of the month there was unusually low volatility between 92 and 94 DCR per ticket. Locked DCR held between 3.75 and 3.87 million or 46.6-48.0% of supply (+0.1% from previous peak).
Nodes: there are 212 public listening and 216 normal nodes per dcred.eu. Version distribution: 67% on v1.2.0 (+10%), 24% on v1.1.2 (-1%), 7% on v1.1.0 (-7%). Node count data is not perfect but we can see the steady trend of upgrading to v1.2.0. This version of dcrd is notable for serving compact filters. The increased count of such full nodes allows the developers to test SPV client mode in preparations for the upcoming v1.3.0 release.

ASICs

Obelisk posted three updates in July. For the most recent daily updates join their Discord.
New miner from iBeLink: DSM7T hashes Blake256 at 7 TH/s or Blake2b at 3.5 TH/s, consumes 2,100 W and costs $3,800, shipping Aug 5-10.
There were also speculations about the mysterious Pangolin Whatsminer DCR with the speed of 44 TH/s at 2,200 W and the cost of $3,888, shipping November. If you know more about it please share with us in #pow-mining channel.

Integrations

Meet new stake pool: dcrpool.ibitlin.com has 1% fees and is hosted by @life.
An interesting detail about decredbrasil.com stake pool was posted in chat:
emiliomann: stakebrasil is one of the pools with the lowest number of missed and expired tickets. It was one of the first and has a smaller percentage than the most recent ones who haven’t had the time to do so. (...) The Brazilian pool should be the one with the more servers spread around the world: 6 to decrease the latency. This is to explain to you why the [pool fee] rate of 5% (currently around 0.06 DCR) on the reward is also one of the highest. girino: 8 voting wallets now. I just finished setting up a new one yesterday. All of them in different datacenters, 3 in europe, 3 in north america, 1 in brazil and one in asia. We also have 3 more servers, 1 for the front end, one for "stats" and one for dcrdata. (#general)
On the mining side, Luxor started a new set of pool servers inside mainland China, while zpool has enabled Decred mining.
StatX announced Decred integration into their live dashboard and public chat.
Decred was added to Satowallet with BTC and ETH trading pairs. Caution: do your best to understand the security model before using any wallet software.

Adoption

VotoLegal update:
Marina Silva is the first presidential candidate in Brazil using blockchain to keep all their electoral donations transparent and traceable. VotoLegal uses Decred technology, awesome use case! (reddit)
The story was covered by criptonoticias.com (translated) and livecoins.com.br (translated), the latter received hundreds of upvotes and comments on brasil.
On the OTC trading front, @i2Rav from i2trading reports:
We continue to see institutional interest in DCR. Large block buyers love the concept of staking as a way to earn additional income and appreciate the stakeholder rights it affords them. Likening a DCR investment to an activist shareholdebondholder gives these institutions some comfort while dipping their toes into a burgeoning new asset class.

Marketing

Targeted advertising reports released for June and July. As usual, reach @timhebel for full versions.
Big news in June: Facebook reversed their policy on banning crypto ads. ICO ads are still banned, but we should be OK. My team filled out the appeal today, so we should hopefully hear something within a few days. (u/timhebel on reddit)
After couple weeks Facebook finally responded to the appeal and the next step is to verify the domain name via DNS.
A pack of Stakey Telegram stickers is now available. Have fun!

Events

Attended:
Upcoming:

Media

Featured articles:
Articles:
Some articles are omitted due to low quality or factual errors.
Translations:
Videos:

Community Discussions

Community stats:
Comm systems update:
Articles:
Twitter: Ari Paul debates "There can be only one" aka "highlander argument".
Reddit and Forum: how ticket pool size influences average vote time; roadmap concerns; why ticket price was volatile; ideas for using Reddit chat for dcrtrader and alternative chat systems; insette's write-up on Andrew Stone's GROUP proposal for miner-validated tokenization that is superior to current OP_RETURN-based schemes; James Liu's paper to extend atomic swaps to financial derivatives; what happens when all DCR are mined, tail emission and incentives for miners.
Chats: why tickets don't have 100% chance to vote; ideas for more straightforward marketing; long-running chat about world economy and failure modes; @brandon's thoughts on tokenizing everything, ICOs, securities, sidechains and more; challenges of staking with Trezor; ideas how to use CryptoSteel wallet with Decred; why exchange can't stake your coins, how staking can increase security, why the function to export seed from wallet is bad idea and why dcrwallet doesn't ever store the seed; ticket voting math; discussion about how GitHub workflow forces to depend on modern web browser and possible alternatives; funding marketing and education in developing markets, vetting contractors based on deliverables, "Decred contractor clearance", continued in #governance.
#dex channel continues to attract thinkers and host chats about influence of exchanges, regulation, HFT, lot sizes, liquidity, on-chain vs off-chain swaps, to name a few topics. #governance also keeps growing and hosting high quality conversations.

Markets

In July DCR was trading in USD 56-76 and BTC 0.0072-0.0109 range. A recovery started after a volume boost of up to $10.5 m on Fex around Jul 13, but once Bitcoin headed towards USD ~8,000 DCR declined along with most altcoins.
WalletInvestor posted a prediction on dcrtrader.
Decred was noticed in top 10 mineable coins on coinmarketcap.com.

Relevant External

One million PCs in China were infected via browser plugins to mine Decred, Siacoin and Digibyte.
In a Unchained podcast episode David Vorick shared why ASICs are better than GPUs even if they tend toward mining centralization and also described Obelisk's new Launchpad service. (missed in June issue)
Sia project moved to GitLab. The stated reasons are to avoid the risk of depending on centralized service, to avoid vendor lock-in, better continuous integration and testing, better access control and the general direction to support decentralized and open source projects.
Luxor explained why PPS pools are better.
@nic__carter published slides from his talk "An Overview of Governance in Blockchains" from Zcon0.
This article arguing the importance of governance systems dates back to 2007.
Bancor wallet was hacked. This reminds us about the fake feeling of decentralizaion, that custody of funds is dangerous and that smart contracts must have minimum complexity and be verifiable.
Circle announced official Poloniex mobile apps for iOS and Android.
On Jul 27 Circle announced delisting of 9 coins from Poloniex that led to a loss of 23-81% of their value same day. Sad reminder about how much a project can depend on a single centralized exchange.
DCR supply and market cap is now correct on onchainfx.com and finally, on coinmarketcap.com. Thanks to @sumiflow, @jz and others doing the tedious work to reach out the various websites.

About This Issue

This is the 4th issue of Decred Journal. It is mirrored on GitHub, Medium and Reddit. Past issues are available here.
Most information from third parties is relayed directly from source after a minimal sanity check. The authors of Decred Journal have no ability to verify all claims. Please beware of scams and do your own research.
Chat links were changed to riot.im from the static web viewer that suffered from UX issues (filed here and here). We will consider changing back to the static viewer once they are resolved because it does not require javascript to read chat logs.
In the previous issue we introduced "Featured articles". The judgement is subjective by definition, if you feel unfairness or want to debate the criteria please check this issue.
Feedback is appreciated: please comment on Reddit, GitHub or #writers_room.
Contributions are also welcome, some areas are adding content, pre-release review or translations to other languages.
Credits (Slack names, alphabetical order): bee, Haon and Richard-Red.
submitted by jet_user to decred [link] [comments]

⚡ Lightning Network Megathread ⚡

Last updated 2018-01-29
This post is a collaboration with the Bitcoin community to create a one-stop source for Lightning Network information.
There are still questions in the FAQ that are unanswered, if you know the answer and can provide a source please do so!

⚡What is the Lightning Network? ⚡

Explanations:

Image Explanations:

Specifications / White Papers

Videos

Lightning Network Experts on Reddit

  • starkbot - (Elizabeth Stark - Lightning Labs)
  • roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
  • stile65 - (Alex Akselrod - Lightning Labs)
  • cfromknecht - (Conner Fromknecht - Lightning Labs)
  • RustyReddit - (Rusty Russell - Blockstream)
  • cdecker - (Christian Decker - Blockstream)
  • Dryja - (Tadge Dryja - Digital Currency Initiative)
  • josephpoon - (Joseph Poon)
  • fdrn - (Fabrice Drouin - ACINQ )
  • pmpadiou - (Pierre-Marie Padiou - ACINQ)

Lightning Network Experts on Twitter

  • @starkness - (Elizabeth Stark - Lightning Labs)
  • @roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
  • @stile65 - (Alex Akselrod - Lightning Labs)
  • @bitconner - (Conner Fromknecht - Lightning Labs)
  • @johanth - (Johan Halseth - Lightning Labs)
  • @bvu - (Bryan Vu - Lightning Labs)
  • @rusty_twit - (Rusty Russell - Blockstream)
  • @snyke - (Christian Decker - Blockstream)
  • @JackMallers - (Jack Mallers - Zap)
  • @tdryja - (Tadge Dryja - Digital Currency Initiative)
  • @jcp - (Joseph Poon)
  • @alexbosworth - (Alex Bosworth - yalls.org)

Medium Posts

Learning Resources

Books

Desktop Interfaces

Web Interfaces

Tutorials and resources

Lightning on Testnet

Lightning Wallets

Place a testnet transaction

Altcoin Trading using Lightning

  • ZigZag - Disclaimer You must trust ZigZag to send to Target Address

Lightning on Mainnet

Warning - Testing should be done on Testnet

Atomic Swaps

Developer Documentation and Resources

Lightning implementations

  • LND - Lightning Network Daemon (Golang)
  • eclair - A Scala implementation of the Lightning Network (Scala)
  • c-lightning - A Lightning Network implementation in C
  • lit - Lightning Network node software (Golang)
  • lightning-onion - Onion Routed Micropayments for the Lightning Network (Golang)
  • lightning-integration - Lightning Integration Testing Framework
  • ptarmigan - C++ BOLT-Compliant Lightning Network Implementation [Incomplete]

Libraries

Lightning Network Visualizers/Explorers

Testnet

Mainnet

Payment Processors

  • BTCPay - Next stable version will include Lightning Network

Community

Slack

IRC

Slack Channel

Discord Channel

Miscellaneous

⚡ Lightning FAQs ⚡

If you can answer please PM me and include source if possible. Feel free to help keep these answers up to date and as brief but correct as possible
Is Lightning Bitcoin?
Yes. You pick a peer and after some setup, create a bitcoin transaction to fund the lightning channel; it’ll then take another transaction to close it and release your funds. You and your peer always hold a bitcoin transaction to get your funds whenever you want: just broadcast to the blockchain like normal. In other words, you and your peer create a shared account, and then use Lightning to securely negotiate who gets how much from that shared account, without waiting for the bitcoin blockchain.
Is the Lightning Network open source?
Yes, Lightning is open source. Anyone can review the code (in the same way as the bitcoin code)
Who owns and controls the Lightning Network?
Similar to the bitcoin network, no one will ever own or control the Lightning Network. The code is open source and free for anyone to download and review. Anyone can run a node and be part of the network.
I’ve heard that Lightning transactions are happening “off-chain”…Does that mean that my bitcoin will be removed from the blockchain?
No, your bitcoin will never leave the blockchain. Instead your bitcoin will be held in a multi-signature address as long as your channel stays open. When the channel is closed; the final transaction will be added to the blockchain. “Off-chain” is not a perfect term, but it is used due to the fact that the transfer of ownership is no longer reflected on the blockchain until the channel is closed.
Do I need a constant connection to run a lightning node?
Not necessarily,
Example: A and B have a channel. 1 BTC each. A sends B 0.5 BTC. B sends back 0.25 BTC. Balance should be A = 0.75, B = 1.25. If A gets disconnected, B can publish the first Tx where the balance was A = 0.5 and B = 1.5. If the node B does in fact attempt to cheat by publishing an old state (such as the A=0.5 and B=1.5 state), this cheat can then be detected on-chain and used to steal the cheaters funds, i.e., A can see the closing transaction, notice it's an old one and grab all funds in the channel (A=2, B=0). The time that A has in order to react to the cheating counterparty is given by the CheckLockTimeVerify (CLTV) in the cheating transaction, which is adjustable. So if A foresees that it'll be able to check in about once every 24 hours it'll require that the CLTV is at least that large, if it's once a week then that's fine too. You definitely do not need to be online and watching the chain 24/7, just make sure to check in once in a while before the CLTV expires. Alternatively you can outsource the watch duties, in order to keep the CLTV timeouts low. This can be achieved both with trusted third parties or untrusted ones (watchtowers). In the case of a unilateral close, e.g., you just go offline and never come back, the other endpoint will have to wait for that timeout to expire to get its funds back. So peers might not accept channels with extremely high CLTV timeouts. -- Source
What Are Lightning’s Advantages?
Tiny payments are possible: since fees are proportional to the payment amount, you can pay a fraction of a cent; accounting is even done in thousandths of a satoshi. Payments are settled instantly: the money is sent in the time it takes to cross the network to your destination and back, typically a fraction of a second.
Does Lightning require Segregated Witness?
Yes, but not in theory. You could make a poorer lightning network without it, which has higher risks when establishing channels (you might have to wait a month if things go wrong!), has limited channel lifetime, longer minimum payment expiry times on each hop, is less efficient and has less robust outsourcing. The entire spec as written today assumes segregated witness, as it solves all these problems.
Can I Send Funds From Lightning to a Normal Bitcoin Address?
No, for now. For the first version of the protocol, if you wanted to send a normal bitcoin transaction using your channel, you have to close it, send the funds, then reopen the channel (3 transactions). In future versions, you and your peer would agree to spend out of your lightning channel funds just like a normal bitcoin payment, allowing you to use your lightning wallet like a normal bitcoin wallet.
Can I Make Money Running a Lightning Node?
Not really. Anyone can set up a node, and so it’s a race to the bottom on fees. In practice, we may see the network use a nominal fee and not change very much, which only provides an incremental incentive to route on a node you’re going to use yourself, and not enough to run one merely for fees. Having clients use criteria other than fees (e.g. randomness, diversity) in route selection will also help this.
What is the release date for Lightning on Mainnet?
Lightning is already being tested on the Mainnet Twitter Link but as for a specific date, Jameson Lopp says it best
Would there be any KYC/AML issues with certain nodes?
Nope, because there is no custody ever involved. It's just like forwarding packets. -- Source
What is the delay time for the recipient of a transaction receiving confirmation?
Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. -- Source
How does the lightning network prevent centralization?
Bitcoin Stack Exchange Answer
What are Channel Factories and how do they work?
Bitcoin Stack Exchange Answer
How does the Lightning network work in simple terms?
Bitcoin Stack Exchange Answer
How are paths found in Lightning Network?
Bitcoin Stack Exchange Answer
How would the lightning network work between exchanges?
Each exchange will get to decide and need to implement the software into their system, but some ideas have been outlined here: Google Doc - Lightning Exchanges
Note that by virtue of the usual benefits of cost-less, instantaneous transactions, lightning will make arbitrage between exchanges much more efficient and thus lead to consistent pricing across exchange that adopt it. -- Source
How do lightning nodes find other lightning nodes?
Stack Exchange Answer
Does every user need to store the state of the complete Lightning Network?
According to Rusty's calculations we should be able to store 1 million nodes in about 100 MB, so that should work even for mobile phones. Beyond that we have some proposals ready to lighten the load on endpoints, but we'll cross that bridge when we get there. -- Source
Would I need to download the complete state every time I open the App and make a payment?
No you'd remember the information from the last time you started the app and only sync the differences. This is not yet implemented, but it shouldn't be too hard to get a preliminary protocol working if that turns out to be a problem. -- Source
What needs to happen for the Lightning Network to be deployed and what can I do as a user to help?
Lightning is based on participants in the network running lightning node software that enables them to interact with other nodes. This does not require being a full bitcoin node, but you will have to run "lnd", "eclair", or one of the other node softwares listed above.
All lightning wallets have node software integrated into them, because that is necessary to create payment channels and conduct payments on the network, but you can also intentionally run lnd or similar for public benefit - e.g. you can hold open payment channels or channels with higher volume, than you need for your own transactions. You would be compensated in modest fees by those who transact across your node with multi-hop payments. -- Source
Is there anyway for someone who isn't a developer to meaningfully contribute?
Sure, you can help write up educational material. You can learn and read more about the tech at http://dev.lightning.community/resources. You can test the various desktop and mobile apps out there (Lightning Desktop, Zap, Eclair apps). -- Source
Do I need to be a miner to be a Lightning Network node?
No -- Source
Do I need to run a full Bitcoin node to run a lightning node?
lit doesn't depend on having your own full node -- it automatically connects to full nodes on the network. -- Source
LND uses a light client mode, so it doesn't require a full node. The name of the light client it uses is called neutrino
How does the lightning network stop "Cheating" (Someone broadcasting an old transaction)?
Upon opening a channel, the two endpoints first agree on a reserve value, below which the channel balance may not drop. This is to make sure that both endpoints always have some skin in the game as rustyreddit puts it :-)
For a cheat to become worth it, the opponent has to be absolutely sure that you cannot retaliate against him during the timeout. So he has to make sure you never ever get network connectivity during that time. Having someone else also watching for channel closures and notifying you, or releasing a canned retaliation, makes this even harder for the attacker. This is because if he misjudged you being truly offline you can retaliate by grabbing all of its funds. Spotty connections, DDoS, and similar will not provide the attacker the necessary guarantees to make cheating worthwhile. Any form of uncertainty about your online status acts as a deterrent to the other endpoint. -- Source
How many times would someone need to open and close their lightning channels?
You typically want to have more than one channel open at any given time for redundancy's sake. And we imagine open and close will probably be automated for the most part. In fact we already have a feature in LND called autopilot that can automatically open channels for a user.
Frequency will depend whether the funds are needed on-chain or more useful on LN. -- Source
Will the lightning network reduce BTC Liquidity due to "locking-up" funds in channels?
Stack Exchange Answer
Can the Lightning Network work on any other cryptocurrency? How?
Stack Exchange Answer
When setting up a Lightning Network Node are fees set for the entire node, or each channel when opened?
You don't really set up a "node" in the sense that anyone with more than one channel can automatically be a node and route payments. Fees on LN can be set by the node, and can change dynamically on the network. -- Source
Can Lightning routing fees be changed dynamically, without closing channels?
Yes but it has to be implemented in the Lightning software being used. -- Source
How can you make sure that there will be routes with large enough balances to handle transactions?
You won't have to do anything. With autopilot enabled, it'll automatically open and close channels based on the availability of the network. -- Source
How does the Lightning Network stop flooding nodes (DDoS) with micro transactions? Is this even an issue?
Stack Exchange Answer

Unanswered Questions

How do on-chain fees work when opening and closing channels? Who pays the fee?
How does the Lightning Network work for mobile users?
What are the best practices for securing a lightning node?
What is a lightning "hub"?
How does lightning handle cross chain (Atomic) swaps?

Special Thanks and Notes

  • Many links found from awesome-lightning-network github
  • Everyone who submitted a question or concern!
  • I'm continuing to format for an easier Mobile experience!
submitted by codedaway to Bitcoin [link] [comments]

A (hopefully mathematically neutral) comparison of Lightning network fees to Bitcoin Cash on-chain fees.

A side note before I begin
For context, earlier today, sherlocoin made a post on this sub asking if Lightning Network transactions are cheaper than on-chain BCH transactions. This user also went on to complain on /bitcoin that his "real" numbers were getting downvoted
I was initially going to respond to his post, but after I typed some of my response, I realized it is relevant to a wider Bitcoin audience and the level of analysis done warranted a new post. This wound up being the longest post I've ever written, so I hope you agree.
I've placed the TL;DR at the top and bottom for the simple reason that you need to prepare your face... because it's about to get hit with a formidable wall of text.
TL;DR: While Lightning node payments themselves cost less than on-chain BCH payments, the associated overhead currently requires a LN channel to produce 16 transactions just to break-even under ideal 1sat/byte circumstances and substantially more as the fee rate goes up.
Further, the Lightning network can provide no guarantee in its current state to maintain/reduce fees to 1sat/byte.

Let's Begin With An Ideal World
Lightning network fees themselves are indeed cheaper than Bitcoin Cash fees, but in order to get to a state where a Lightning network fee can be made, you are required to open a channel, and to get to a state where those funds are spendable, you must close that channel.
On the Bitcoin network, the minimum accepted fee is 1sat/byte so for now, we'll assume that ideal scenario of 1sat/byte. We'll also assume the open and close is sent as a simple native Segwit transaction with a weighted size of 141 bytes. Because we have to both open and close, this 141 byte fee will be incurred twice. The total fee for an ideal open/close transaction is 1.8¢
For comparison, a simple transaction on the BCH network requires 226 bytes one time. The minimum fee accepted next-block is 1sat/byte. At the time of writing an ideal BCH transaction fee costs ~ 0.11¢
This means that under idealized circumstances, you must currently make at least 16 transactions on a LN channel to break-even with fees
Compounding Factors
Our world is not ideal, so below I've listed compounding factors, common arguments, an assessment, and whether the problem is solvable.
Problem 1: Bitcoin and Bitcoin Cash prices are asymmetrical.
Common arguments:
BTC: If Bitcoin Cash had the same price, the fees would be far higher
Yes, this is true. If Bitcoin Cash had the same market price as Bitcoin, our ideal scenario changes substantially. An open and close on Bitcoin still costs 1.8¢ while a simple Bitcoin Cash transaction now costs 1.4¢. The break-even point for a Lightning Channel is now only 2 transactions.
Is this problem solvable?
Absolutely.
Bitcoin Cash has already proposed a reduction in fees to 1sat for every 10 bytes, and that amount can be made lower by later proposals. While there is no substantial pressure to implement this now, if Bitcoin Cash had the same usage as Bitcoin currently does, it is far more likely to be implemented. If implemented at the first proposed reduction rate, under ideal circumstances, a Lightning Channel would need to produce around 13 transactions for the new break even.
But couldn't Bitcoin reduce fees similarly
The answer there is really tricky. If you reduce on-chain fees, you reduce the incentive to use the Lightning Network as the network becomes more hospitable to micropaments. This would likely increase the typical mempool state and decrease the Lightning Channel count some. The upside is that when the mempool saturates with low transaction fees, users are then re-incentivized to use the lightning network after the lowes fees are saturated with transactions. This should, in theory, produce some level of a transaction fee floor which is probably higher on average than 0.1 sat/byte on the BTC network.
Problem 2: This isn't an ideal world, we can't assume 1sat/byte fees
Common arguments:
BCH: If you tried to open a channel at peak fees, you could pay $50 each way
BTC: LN wasn't implemented which is why the fees are low now
Both sides have points here. It's true that if the mempool was in the same state as it was in December of 2017, that a user could have potentially been incentivized to pay an open and close channel fee of up to 1000 sat/byte to be accepted in a reasonable time-frame.
With that being said, two factors have resulted in a reduced mempool size of Bitcoin: Increased Segwit and Lightning Network Usage, and an overall cooling of the market.
I'm not going to speculate as to what percentage of which is due to each factor. Instead, I'm going to simply analyze mempool statistics for the last few months where both factors are present.
Let's get an idea of current typical Bitcoin network usage fees by asking Johoe quick what the mempool looks like.
For the last few months, the bitcoin mempool has followed almost the exact same pattern. Highest usage happens between 10AM and 3PM EST with a peak around noon. Weekly, usage usually peaks on Tuesday or Wednesday with enough activity to fill blocks with at least minimum fee transactions M-F during the noted hours and usually just shy of block-filling capacity on Sat and Sun.
These observations can be additionally evidenced by transaction counts on bitinfocharts. It's also easier to visualize on bitinfocharts over a longer time-frame.
Opening a channel
Under pre-planned circumstances, you can offload channel creation to off-peak hours and maintain a 1sat/byte rate. The primary issue arises in situations where either 1) LN payments are accepted and you had little prior knowledge, or 2) You had a previous LN pathway to a known payment processor and one or more previously known intermediaries are offline or otherwise unresponsive causing the payment to fail.
Your options are:
A) Create a new LN channel on-the-spot where you're likely to incur current peak fee rates of 5-20sat/byte.
B) Create an on-chain payment this time and open a LN channel when fees are more reasonable.
C) Use an alternate currency for the transaction.
There is a fundamental divide among the status of C. Some people view Bitcoin as (primarily) a storage of value, and thus as long as there are some available onramps and offramps, the currency will hold value. There are other people who believe that fungibility is what gives cryptocurrency it's value and that option C would fundamentally undermine the value of the currency.
I don't mean to dismiss either argument, but option C opens a can of worms that alone can fill economic textbooks. For the sake of simplicity, we will throw out option C as a possibility and save that debate for another day. We will simply require that payment is made in crypto.
With option B, you would absolutely need to pay the peak rate (likely higher) for a single transaction as a Point-of-Sale scenario with a full mempool would likely require at least one confirm and both parties would want that as soon as possible after payment. It would not be unlikely to pay 20-40 sat/byte on a single transaction and then pay 1sat/byte for an open and close to enable LN payments later. Even in the low end, the total cost is 20¢ for on-chain + open + close.
With present-day-statistics, your LN would have to do 182 transactions to make up for the one peak on-chain transaction you were forced to do.
With option A, you still require one confirm. Let's also give the additional leeway that in this scenario you have time to sit and wait a couple of blocks for your confirm before you order / pay. You can thus pay peak rates alone and not peak + ensure next block rates. This will most likely be in the 5-20 sat/byte range. With 5sat/byte open and 1sat/byte close, your LN would have to do 50 transactions to break even
In closing, fees are incurred by the funding channel, so there could be scenarios where the receiving party is incentivized to close in order to spend outputs and the software automatically calculates fees based on current rates. If this is the case, the receiving party could incur a higher-than-planned fee to the funding party.
With that being said, any software that allows the funding party to set the fee beforehand would avoid unplanned fees, so we'll assume low fees for closing.
Is this problem solvable?
It depends.
In order to avoid the peak-fee open/close ratio problem, the Bitcoin network either needs to have much higher LN / Segwit utilization, or increase on-chain capacity. If it gets to a point where transactions stack up, users will be required to pay more than 1sat/byte per transaction and should expect as much.
Current Bitcoin network utilization is close enough to 100% to fill blocks during peak times. I also did an export of the data available at Blockchair.com for the last 3000 blocks which is approximately the last 3 weeks of data. According to their block-weight statistics, The average Bitcoin block is 65.95% full. This means that on-chain, Bitcoin can only increase in transaction volume by around 50% and all other scaling must happen via increased Segwit and LN use.
Problem 3: You don't fully control your LN channel states.
Common arguments:
BCH: You can get into a scenario where you don't have output capacity and need to open a new channel.
BCH: A hostile actor can cause you to lose funds during a high-fee situation where a close is forced.
BTC: You can easily re-load your channel by pushing outbound to inbound.
BCH: You can't control whether nodes you connect to are online or offline.
There's a lot to digest here, but LN is essentially a 2-way contract between 2 parties. Not only does the drafting party pay the fees as of right now, but connected 3rd-parties can affect the state of this contract. There are some interesting scenarios that develop because of it and you aren't always in full control of what side.
Lack of outbound capacity
First, it's true that if you run out of outbound capacity, you either need to reload or create a new channel. This could potentially require 0, 1, or 2 additional on-chain transactions.
If a network loop exists between a low-outbound-capacity channel and yourself, you could push transactional capacity through the loop back to the output you wish to spend to. This would require 0 on-chain transactions and would only cost 1 (relatively negligible) LN fee charge. For all intents and purposes... this is actually kind of a cool scenario.
If no network loop exists from you-to-you, things get more complex. I've seen proposals like using Bitrefill to push capacity back to your node. In order to do this, you would have an account with them and they would lend custodial support based on your account. While people opting for trustless money would take issue in 3rd party custodians, I don't think this alone is a horrible solution to the LN outbound capacity problem... Although it depends on the fee that bitrefill charges to maintain an account and account charges could negate the effectiveness of using the LN. Still, we will assume this is a 0 on-chain scenario and would only cost 1 LN fee which remains relatively negligible.
If no network loop exists from you and you don't have a refill service set up, you'll need at least one on-chain payment to another LN entity in exchange for them to push LN capacity to you. Let's assume ideal fee rates. If this is the case, your refill would require an additional 7 transactions for that channel's new break-even. Multiply that by number of sat/byte if you have to pay more.
Opening a new channel is the last possibility and we go back to the dynamics of 13 transactions per LN channel in the ideal scenario.
Hostile actors
There are some potential attack vectors previously proposed. Most of these are theoretical and/or require high fee scenarios to come about. I think that everyone should be wary of them, however I'm going to ignore most of them again for the sake of succinctness.
This is not to be dismissive... it's just because my post length has already bored most casual readers half to death and I don't want to be responsible for finishing the job.
Pushing outbound to inbound
While I've discussed scenarios for this push above, there are some strange scenarios that arise where pushing outbound to inbound is not possible and even some scenarios where a 3rd party drains your outbound capacity before you can spend it.
A while back I did a testnet simulation to prove that this scenario can and will happen it was a post response that happened 2 weeks after the initial post so it flew heavily under the radar, but the proof is there.
The moral of this story is in some scenarios, you can't count on loaded network capacity to be there by the time you want to spend it.
Online vs Offline Nodes
We can't even be sure that a given computer is online to sign a channel open or push capacity until we try. Offline nodes provide a brick-wall in the pathfinding algorithm so an alternate route must be found. If we have enough channel connectivity to be statistically sure we can route around this issue, we're in good shape. If not, we're going to have issues.
Is this problem solvable?
Only if the Lightning network can provide an (effectively) infinite amount of capacity... but...
Problem 4: Lightning Network is not infinite.
Common arguments:
BTC: Lightning network can scale infinitely so there's no problem.
Unfortunately, LN is not infinitely scalable. In fact, finding a pathway from one node to another is roughly the same problem as the traveling salesman problem. Dijkstra's algorithm which is a problem that diverges polynomially. The most efficient proposals have a difficulty bound by O(n^2).
Note - in the above I confused the complexity of the traveling salesman problem with Dijkstra when they do not have the same bound. With that being said, the complexity of the LN will still diverge with size
In lay terms, what that means is every time you double the size of the Lightning Network, finding an indirect LN pathway becomes 4 times as difficult and data intensive. This means that for every doubling, the amount of traffic resulting from a single request also quadruples.
You can potentially temporarily mitigate traffic by bounding the number of hops taken, but that would encourage a greater channel-per-user ratio.
For a famous example... the game "6 degrees of Kevin Bacon" postulates that Kevin Bacon can be connected by co-stars to any movie by 6 degrees of separation. If the game is reduced to "4 degrees of Kevin Bacon," users of this network would still want as many connections to be made, so they'd be incentivized to hire Kevin Bacon to star in everything. You'd start to see ridiculous mash-ups and reboots just to get more connectivity... Just imagine hearing Coming soon - Kevin Bacon and Adam Sandlar star in "Billy Madison 2: Replace the face."
Is this problem solvable?
Signs point to no.
So technically, if the average computational power and network connectivity can handle the problem (the number of Lightning network channels needed to connect the world)2 in a trivial amount of time, Lightning Network is effectively infinite as the upper bound of a non-infinite earth would limit time-frames to those that are computationally feasible.
With that being said, BTC has discussed Lightning dev comments before that estimated a cap of 10,000 - 1,000,000 channels before problems are encountered which is far less than the required "number of channels needed to connect the world" level.
In fact SHA256 is a newer NP-hard problem than the traveling saleseman problem. That means that statistically, and based on the amount of review that has been given to each problem, it is more likely that SHA256 - the algorithm that lends security to all of bitcoin - is cracked before the traveling salesman problem is. Notions that "a dedicated dev team can suddenly solve this problem, while not technically impossible, border on statistically absurd.
Edit - While the case isn't quite as bad as the traveling salesman problem, the problem will still diverge with size and finding a more efficient algorithm is nearly as unlikely.
This upper bound shows that we cannot count on infinite scalability or connectivity for the lightning network. Thus, there will always be on-chain fee pressure and it will rise as the LN reaches it's computational upper-bound.
Because you can't count on channel states, the on-chain fee pressure will cause typical sat/byte fees to raise. The higher this rate, the more transactions you have to make for a Lightning payment open/close operation to pay for itself.
This is, of course unless it is substantially reworked or substituted for a O(log(n))-or-better solution.
Finally, I'd like to add, creating an on-chain transaction is a set non-recursive, non looping function - effectively O(1), sending this transaction over a peer-to-peer network is bounded by O(log(n)) and accepting payment is, again, O(1). This means that (as far as I can tell) on-chain transactions (very likely) scale more effectively than Lightning Network in its current state.
Additional notes:
My computational difficulty assumptions were based on a generalized, but similar problem set for both LN and on-chain instances. I may have overlooked additional steps needed for the specific implementation, and I may have overlooked reasons a problem is a simplified version requiring reduced computational difficulty.
I would appreciate review and comment on my assumptions for computational difficulty and will happily correct said assumptions if reasonable evidence is given that a problem doesn't adhere to listed computational difficulty.
TL;DR: While Lightning node payments themselves cost less than on-chain BCH payments, the associated overhead currently requires a LN channel to produce 16 transactions just to break-even under ideal 1sat/byte circumstances and substantially more as the fee rate goes up.
Further, the Lightning network can provide no guarantee in its current state to maintain/reduce fees to 1sat/byte.
submitted by CaptainPatent to btc [link] [comments]

Bitcoin GitHub History Visualized (Again) March 27 2014 A Bitcoin Blockchain Transaction Visualization + Sonification Bitcoin's Development Visualized w/ Music Bitcoin GitHub History Visualized - Jenkins Palladio Bitcoin GitHub History Visualized Sept 15 2012

Terminology. Bitcoin codebase is hosted on Github, which uses Git software to provide codebase management. Here is some basic terminology which we will use throughout this post. Github Repository — A folder hosted on Github containing the entire codebase of a project.. Commit– A commit is saving some code changes (or File changes) into Github repository. cointrol - ฿ Bitcoin trading bot with a real-time dashboard for Bitstamp. #opensource GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together. Sign up 3D Scientific Visualization using the Visual Toolkit Library Tahitian Noni: Manfaat, Cara Minum, Efek Samping, dll. 0. Search for: Our next choice for the best bitcoin miner app for Windows 10 is CGMiner, which is probably one of the best-known, as well as the most commonly used software among the members of the Bitcoin mining community.. One big reason for this is the fact that CGMiner is created on the original code of CPU Miner. Thanks to this, CGMiner is one of the most feature-rich options that you will ever find.

[index] [4054] [6966] [14082] [7645] [6819] [3289] [2107] [5219] [11090] [10376]

Bitcoin GitHub History Visualized (Again) March 27 2014

Once again, I used the open-source version control visualization software Gource (http://code.google.com/p/gource/) to visualize the history of Bitcoin from ... A Bitcoin Blockchain Transaction Visualization + Sonification "chains" at ZKM (2016) ... Developing Blockchain Software - Duration: ... Bitcoin GitHub History Visualization - Multiple Projects ... Once again, I used the open-source version control visualization software Gource (http://code.google.com/p/gource/) to visualize the history of Bitcoin from ... Bitcoin GitHub History Visualization - Multiple Projects (Jan 2015) - Duration: 5:52. Coding In My Sleep 6,916 views. 5:52. Language: English Location: United States Once again, I used the open-source version control visualization software Gource (http://code.google.com/p/gource/) to visualize the history of Bitcoin from ...