Generating Bitcoin Wallet Address from Extended Public Key ...
How to create Bitcoin Address in PHP? Edureka Community
An improved ESP8266 and Bitcoin price ticker example
Bitcoin Payment Gateway - Bitcoin API PHP. White Label ...
Why Osana takes so long? (Programmer's point of view on current situation)
I decided to write a comment about «Why Osana takes so long?» somewhere and what can be done to shorten this time. It turned into a long essay. Here's TL;DR of it:
The cost of never paying down this technical debt is clear; eventually the cost to deliver functionality will become so slow that it is easy for a well-designed competitive software product to overtake the badly-designed software in terms of features. In my experience, badly designed software can also lead to a more stressed engineering workforce, in turn leading higher staff churn (which in turn affects costs and productivity when delivering features). Additionally, due to the complexity in a given codebase, the ability to accurately estimate work will also disappear. Junade Ali, Mastering PHP Design Patterns (2016)
Longer version: I am not sure if people here wanted an explanation from a real developer who works with C and with relatively large projects, but I am going to do it nonetheless. I am not much interested in Yandere Simulator nor in this genre in general, but this particular development has a lot to learn from for any fellow programmers and software engineers to ensure that they'll never end up in Alex's situation, especially considering that he is definitely not the first one to got himself knee-deep in the development hell (do you remember Star Citizen?) and he is definitely not the last one. On the one hand, people see that Alex works incredibly slowly, equivalent of, like, one hour per day, comparing it with, say, Papers, Please, the game that was developed in nine months from start to finish by one guy. On the other hand, Alex himself most likely thinks that he works until complete exhaustion each day. In fact, I highly suspect that both those sentences are correct! Because of the mistakes made during early development stages, which are highly unlikely to be fixed due to the pressure put on the developer right now and due to his overall approach to coding, cost to add any relatively large feature (e.g. Osana) can be pretty much comparable to the cost of creating a fan game from start to finish. Trust me, I've seen his leaked source code (don't tell anybody about that) and I know what I am talking about. The largest problem in Yandere Simulator right now is its super slow development. So, without further ado, let's talk about how «implementing the low hanging fruit» crippled the development and, more importantly, what would have been an ideal course of action from my point of view to get out. I'll try to explain things in the easiest terms possible.
else if's and lack any sort of refactoring in general
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. Antoine de Saint-Exupéry
This is why refactoring — activity of rewriting your old code so it does the same thing, but does it quicker, in a more generic way, in less lines or simpler — is so powerful. In my experience, you can only keep one module/class/whatever in your brain if it does not exceed ~1000 lines, maybe ~1500. Splitting 17000-line-long class into smaller classes probably won't improve performance at all, but it will make working with parts of this class way easier. Is it too late now to start refactoring? Of course NO: better late than never.
If you think that you wrote this code, so you'll always easily remember it, I have some bad news for you: you won't. In my experience, one week and that's it. That's why comments are so crucial. It is not necessary to put a ton of comments everywhere, but just a general idea will help you out in the future. Even if you think that It Just Works™ and you'll never ever need to fix it. Time spent to write and debug one line of code almost always exceeds time to write one comment in large-scale projects. Moreover, the best code is the code that is self-evident. In the example above, what the hell does (float) 6 mean? Why not wrap it around into the constant with a good, self-descriptive name? Again, it won't affect performance, since C# compiler is smart enough to silently remove this constant from the real code and place its value into the method invocation directly. Such constants are here for you. I rewrote my code above a little bit to illustrate this. With those comments, you don't have to remember your code at all, since its functionality is outlined in two tiny lines of comments above it. Moreover, even a person with zero knowledge in programming will figure out the purpose of this code. It took me less than half a minute to write those comments, but it'll probably save me quite a lot of time of figuring out «what was I thinking back then» one day. Is it too late now to start adding comments? Again, of course NO. Don't be lazy and redirect all your typing from «debunk» page (which pretty much does the opposite of debunking, but who am I to judge you here?) into some useful comments.
This is often neglected, but consider the following. You wrote some code, you ran your game, you saw a new bug. Was it introduced right now? Is it a problem in your older code which has shown up just because you have never actually used it until now? Where should you search for it? You have no idea, and you have one painful debugging session ahead. Just imagine how easier it would be if you've had some routines which automatically execute after each build and check that environment is still sane and nothing broke on a fundamental level. This is called unit testing, and yes, unit tests won't be able to catch all your bugs, but even getting 20% of bugs identified at the earlier stage is a huge boon to development speed. Is it too late now to start adding unit tests? Kinda YES and NO at the same time. Unit testing works best if it covers the majority of project's code. On the other side, a journey of a thousand miles begins with a single step. If you decide to start refactoring your code, writing a unit test before refactoring will help you to prove to yourself that you have not broken anything without the need of running the game at all.
This is basically pretty self-explanatory. You set this thing once, you forget about it. Static code analyzer is another «free estate» to speed up the development process by finding tiny little errors, mostly silly typos (do you think that you are good enough in finding them? Well, good luck catching x << 4; in place of x <<= 4; buried deep in C code by eye!). Again, this is not a silver bullet, it is another tool which will help you out with debugging a little bit along with the debugger, unit tests and other things. You need every little bit of help here. Is it too late now to hook up static code analyzer? Obviously NO.
Say, you want to build Osana, but then you decided to implement some feature, e.g. Snap Mode. By doing this you have maybe made your game a little bit better, but what you have just essentially done is complicated your life, because now you should also write Osana code for Snap Mode. The way game architecture is done right now, easter eggs code is deeply interleaved with game logic, which leads to code «spaghettifying», which in turn slows down the addition of new features, because one has to consider how this feature would work alongside each and every old feature and easter egg. Even if it is just gazing over one line per easter egg, it adds up to the mess, slowly but surely. A lot of people mention that developer should have been doing it in object-oritented way. However, there is no silver bullet in programming. It does not matter that much if you are doing it object-oriented way or usual procedural way; you can theoretically write, say, AI routines on functional (e.g. LISP)) or even logical language if you are brave enough (e.g. Prolog). You can even invent your own tiny programming language! The only thing that matters is code quality and avoiding the so-called shotgun surgery situation, which plagues Yandere Simulator from top to bottom right now. Is there a way of adding a new feature without interfering with your older code (e.g. by creating a child class which will encapsulate all the things you need, for example)? Go for it, this feature is basically «free» for you. Otherwise you'd better think twice before doing this, because you are going into the «technical debt» territory, borrowing your time from the future by saying «I'll maybe optimize it later» and «a thousand more lines probably won't slow me down in the future that much, right?». Technical debt will incur interest on its own that you'll have to pay. Basically, the entire situation around Osana right now is just a huge tale about how just «interest» incurred by technical debt can control the entire project, like the tail wiggling the dog. I won't elaborate here further, since it'll take me an even larger post to fully describe what's wrong about Yandere Simulator's code architecture. Is it too late to rebuild code architecture? Sadly, YES, although it should be possible to split Student class into descendants by using hooks for individual students. However, code architecture can be improved by a vast margin if you start removing easter eggs and features like Snap Mode that currently bloat Yandere Simulator. I know it is going to be painful, but it is the only way to improve code quality here and now. This will simplify the code, and this will make it easier for you to add the «real» features, like Osana or whatever you'd like to accomplish. If you'll ever want them back, you can track them down in Git history and re-implement them one by one, hopefully without performing the shotgun surgery this time.
Again, I won't be talking about the performance, since you can debug your game on 20 FPS as well as on 60 FPS, but this is a very different story. Yandere Simulator is huge. Once you fixed a bug, you want to test it, right? And your workflow right now probably looks like this:
Fix the code (unavoidable time loss)
Rebuild the project (can take a loooong time)
Load your game (can take a loooong time)
Test it (unavoidable time loss, unless another bug has popped up via unit testing, code analyzer etc.)
And you can fix it. For instance, I know that Yandere Simulator makes all the students' photos during loading. Why should that be done there? Why not either move it to project building stage by adding build hook so Unity does that for you during full project rebuild, or, even better, why not disable it completely or replace with «PLACEHOLDER» text for debug builds? Each second spent watching the loading screen will be rightfully interpreted as «son is not coding» by the community. Is it too late to reduce loading times? Hell NO.
Or any other continuous integration tool. «Rebuild a project» can take a long time too, and what can we do about that? Let me give you an idea. Buy a new PC. Get a 32-core Threadripper, 32 GB of fastest RAM you can afford and a cool motherboard which would support all of that (of course, Ryzen/i5/Celeron/i386/Raspberry Pi is fine too, but the faster, the better). The rest is not necessary, e.g. a barely functional second hand video card burned out by bitcoin mining is fine. You set up another PC in your room. You connect it to your network. You set up ramdisk to speed things up even more. You properly set up Jenkins) on this PC. From now on, Jenkins cares about the rest: tracking your Git repository, (re)building process, large and time-consuming unit tests, invoking static code analyzer, profiling, generating reports and whatever else you can and want to hook up. More importantly, you can fix another bug while Jenkins is rebuilding the project for the previous one et cetera. In general, continuous integration is a great technology to quickly track down errors that were introduced in previous versions, attempting to avoid those kinds of bug hunting sessions. I am highly unsure if continuous integration is needed for 10000-20000 source lines long projects, but things can be different as soon as we step into the 100k+ territory, and Yandere Simulator by now has approximately 150k+ source lines of code. I think that probably continuous integration might be well worth it for Yandere Simulator. Is it too late to add continuous integration?NO, albeit it is going to take some time and skills to set up.
Stop caring about the criticism
Stop comparing Alex to Scott Cawton. IMO Alex is very similar to the person known as SgtMarkIV, the developer of Brutal Doom, who is also a notorious edgelord who, for example, also once told somebody to kill himself, just like… However, being a horrible person, SgtMarkIV does his job. He simply does not care much about public opinion. That's the difference.
New England New England 6 States Songs: https://www.reddit.com/newengland/comments/er8wxd/new_england_6_states_songs/ NewEnglandcoin Symbol: NENG NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones. Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt. 1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377 NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number Bitcoin Fork - Suitable for Home Hobbyists NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs. The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity. MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018) https://www.youtube.com/playlist?list=PLUl4u3cNGP63UUkfL0onkxF6MYgVa04Fn CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software. Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%. NENG v1.4.0 release enabled CPU mining inside android phones. Youtube Video Tutorial How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 https://www.youtube.com/watch?v=sdOoPvAjzlE How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2 https://www.youtube.com/watch?v=nHnRJvJRzZg How to CPU Mine NewEnglandcoin (NENG) in macOS https://www.youtube.com/watch?v=Zj7NLMeNSOQ Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG. We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange. Twitter Airdrop Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners Graphic Redesign Bounty Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at: https://discord.gg/UPeBwgs Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form. Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues. Twitter Airdrop/Graphic Redesign bounty sign up: https://goo.gl/forms/L0vcwmVi8c76cR7m1 Milestones
Sep 3, 2018 - Genesis block was mined, NewEnglandcoin created
Sep 8, 2018 - github source uploaded, Window wallet development work started
Sep 11,2018 - Window Qt Graphic wallet completed
Sep 12,2018 - NewEnglandcoin Launched in both Bitcointalk forum and Marinecoin forum
Sep 14,2018 - NewEnglandcoin is listed at ShorelineCrypto Exchange
Sep 17,2018 - Block Explorer is up
Nov 23,2018 - New Source/Wallet Release v1.1.1 - Enabled Dynamic Addjustment on Mining Hashing Difficulty
Nov 28,2018 - NewEnglandcoin became CPU minable coin
Nov 30,2018 - First Retail Real Life usage for NewEnglandcoin Announced
Dec 28,2018 - Cheetah_Cpuminer under Linux is released
Dec 31,2018 - NENG Technical Whitepaper is released
Jan 2,2019 - Cheetah_Cpuminer under Windows is released
Jan 12,2019 - NENG v1.1.2 is released to support MacOS GUI CLI Wallet
Jan 13,2019 - Cheetah_CpuMiner under Mac is released
Feb 11,2019 - NewEnglandcoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork
Mar 16,2019 - NewEnglandcoin v22.214.171.124 Released - Ubuntu 18.04 Wallet Binary Files
Apr 7, 2019 - NENG Report on Security, Decentralization, Valuation
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto
Sep 1, 2019 - Shoreline Tradingbot project is Launched by ShorelineCrypto
Dec 19, 2019 - Shoreline Tradingbot v1.0 is Released by ShorelineCrypto
Jan 30, 2020 - Scrypt RandomSpike - NENG v1.3.0 Hardfork Proposed
Feb 24, 2020 - Scrypt RandomSpike - NENG core v1.3.0 Released
Jun 19, 2020 - Linux scripts for Futurebit Moonlander2 USB ASIC on solo mining Released
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining and Ubuntu 20.04 support
Jul 21, 2020 - NENG v126.96.36.199 Released for MacOS Wallet Upgrade with Catalina
Jul 30, 2020 - NENG v188.8.131.52 Released for Linux Wallet Upgrade with 8 Distros
Aug 11, 2020 - NENG v184.108.40.206 Released for Android arm64 Upgrade, Chromebook Support
Aug 30, 2020 - NENG v220.127.116.11 Released for Android/Chromebook with armhf, better hardware support
2018 Q3 - Birth of NewEnglandcoin, window/linux wallet - Done
2018 Q4 - Decentralization Phase I
Blockchain Upgrade - Dynamic hashing algorithm I - Done
Cheetah Version I- CPU Mining Automation Tool on Linux - Done
2019 Q1 - Decentralization Phase II
Cheetah Version II- CPU Mining Automation Tool on Window/Linux - Done
Blockchain Upgrade Dynamic hashing algorithm II - Done
2019 Q2 - Fiat Phase I
Assessment of Risk of 51% Attack on NENG - done
Launch of Fiat USD/NENG offering for U.S. residents - done
Initiation of Mobile Miner Project - Done
2019 Q3 - Shoreline Tradingbot, Mobile Project
Evaluation and planning of Mobile Miner Project - on Hold
Initiation of Trading Bot Project - Done
2019 Q4 - Shoreline Tradingbot
Shoreline tradingbot Release v1.0 - Done
2020 Q1 - Evaluate NENG core, Mobile Wallet Phase I
NENG core Decentralization Security Evaluation for v1.3.x - Done
Light Mobile Wallet Project Initiation, Evaluation
2020 Q2 - NENG Core, Mobile Wallet Phase II
NENG core Decentralization Security Hardfork on v1.3.x - Scrypt RandomSpike
Light Mobile Wallet Project Design, Coding
2020 Q3 - NENG core, NENG Mobile Wallet Phase II
Review on results of v1.3.x, NENG core Dev Decision on v1.4.x, Hardfork If needed
Light Mobile Wallet Project testing, alpha Release
2020 Q4 - Mobile Wallet Phase III
Light Mobile Wallet Project Beta Release
Light Mobile Wallet Server Deployment Evaluation and Decision
How To End The Cryptocurrency Exchange "Wild West" Without Crippling Innovation
In case you haven't noticed the consultation paper, staff notice, and report on Quadriga, regulators are now clamping down on Canadian cryptocurrency exchanges. The OSC and other regulatory bodies are still interested in industry feedback. They have not put forward any official regulation yet. Below are some ideas/insights and a proposed framework.
Typical securities frameworks will cost Canadians millions of dollars (ie Sarbanes-Oxley estimated at $5m USD/yr per firm). Implementation costs of this proposal are significantly cheaper.
Canadians can maintain a diverse set of exchanges, multiple viable business models are still fully supported, and innovation is encouraged while keeping Canadians safe.
Many of you have limited time to read the full proposal, so here are the highlights:
Effective standards to prevent both internal and external theft. Exchange operators are trained and certified, and have a legal responsibility to users.
Regular Transparent Audits
Provides visibility to Canadians that their funds are fully backed on the exchange, while protecting privacy and sensitive platform information.
Establishment of basic insurance standards/strategy, to expand over time. Removing risk to exchange users of any hot wallet theft.
Background and Justifications
Cold Storage Custody/Management After reviewing close to 100 cases, all thefts tend to break down into more or less the same set of problems: • Funds stored online or in a smart contract, • Access controlled by one person or one system, • 51% attacks (rare), • Funds sent to the wrong address (also rare), or • Some combination of the above. For the first two cases, practical solutions exist and are widely implemented on exchanges already. Offline multi-signature solutions are already industry standard. No cases studied found an external theft or exit scam involving an offline multi-signature wallet implementation. Security can be further improved through minimum numbers of signatories, background checks, providing autonomy and legal protections to each signatory, establishing best practices, and a training/certification program. The last two transaction risks occur more rarely, and have never resulted in a loss affecting the actual users of the exchange. In all cases to date where operators made the mistake, they've been fully covered by the exchange platforms. • 51% attacks generally only occur on blockchains with less security. The most prominent cases have been Bitcoin Gold and Ethereum Classic. The simple solution is to enforce deposit limits and block delays such that a 51% attack is not cost-effective. • The risk of transactions to incorrect addresses can be eliminated by a simple test transaction policy on large transactions. By sending a small amount of funds prior to any large withdrawals/transfers as a standard practice, the accuracy of the wallet address can be validated. The proposal covers all loss cases and goes beyond, while avoiding significant additional costs, risks, and limitations which may be associated with other frameworks like SOC II. On The Subject of Third Party Custodians Many Canadian platforms are currently experimenting with third party custody. From the standpoint of the exchange operator, they can liberate themselves from some responsibility of custody, passing that off to someone else. For regulators, it puts crypto in similar categorization to oil, gold, and other commodities, with some common standards. Platform users would likely feel greater confidence if the custodian was a brand they recognized. If the custodian was knowledgeable and had a decent team that employed multi-sig, they could keep assets safe from internal theft. With the right protections in place, this could be a great solution for many exchanges, particularly those that lack the relevant experience or human resources for their own custody systems. However, this system is vulnerable to anyone able to impersonate the exchange operators. You may have a situation where different employees who don't know each other that well are interacting between different companies (both the custodian and all their customers which presumably isn't just one exchange). A case study of what can go wrong in this type of environment might be Bitpay, where the CEO was tricked out of 5000 bitcoins over 3 separate payments by a series of emails sent legitimately from a breached computer of another company CEO. It's also still vulnerable to the platform being compromised, as in the really large $70M Bitfinex hack, where the third party Bitgo held one key in a multi-sig wallet. The hacker simply authorized the withdrawal using the same credentials as Bitfinex (requesting Bitgo to sign multiple withdrawal transactions). This succeeded even with the use of multi-sig and two heavily security-focused companies, due to the lack of human oversight (basically, hot wallet). Of course, you can learn from these cases and improve the security, but so can hackers improve their deception and at the end of the day, both of these would have been stopped by the much simpler solution of a qualified team who knew each other and employed multi-sig with properly protected keys. It's pretty hard to beat a human being who knows the business and the typical customer behaviour (or even knows their customers personally) at spotting fraud, and the proposed multi-sig means any hacker has to get through the scrutiny of 3 (or more) separate people, all of whom would have proper training including historical case studies. There are strong arguments both for and against using use of third party custodians. The proposal sets mandatory minimum custody standards would apply regardless if the cold wallet signatories are exchange operators, independent custodians, or a mix of both. On The Subject Of Insurance ShakePay has taken the first steps into this new realm (congratulations). There is no question that crypto users could be better protected by the right insurance policies, and it certainly feels better to transact with insured platforms. The steps required to obtain insurance generally place attention in valuable security areas, and in this case included a review from CipherTrace. One of the key solutions in traditional finance comes from insurance from entities such as the CDIC. However, historically, there wasn't found any actual insurance payout to any cryptocurrency exchange, and there are notable cases where insurance has not paid. With Bitpay, for example, the insurance agent refused because the issue happened to the third party CEO's computer instead of anything to do with Bitpay itself. With the Youbit exchange in South Korea, their insurance claim was denied, and the exchange ultimately ended up instead going bankrupt with all user's funds lost. To quote Matt Johnson in the original Lloyd's article: “You can create an insurance policy that protects no one – you know there are so many caveats to the policy that it’s not super protective.” ShakePay's insurance was only reported to cover their cold storage, and “physical theft of the media where the private keys are held”. Physical theft has never, in the history of cryptocurrency exchange cases reviewed, been reported as the cause of loss. From the limited information of the article, ShakePay made it clear their funds are in the hands of a single US custodian, and at least part of their security strategy is to "decline to confirm the custodian’s name on the record". While this prevents scrutiny of the custodian, it's pretty silly to speculate that a reasonably competent hacking group couldn't determine who the custodian is. A far more common infiltration strategy historically would be social engineering, which has succeeded repeatedly. A hacker could trick their way into ShakePay's systems and request a fraudulent withdrawal, impersonate ShakePay and request the custodian to move funds, or socially engineer their way into the custodian to initiate the withdrawal of multiple accounts (a payout much larger than ShakePay) exploiting the standard procedures (for example, fraudulently initiating or override the wallet addresses of a real transfer). In each case, nothing was physically stolen and the loss is therefore not covered by insurance. In order for any insurance to be effective, clear policies have to be established about what needs to be covered. Anything short of that gives Canadians false confidence that they are protected when they aren't in any meaningful way. At this time, the third party insurance market does not appear to provide adequate options or coverage, and effort is necessary to standardize custody standards, which is a likely first step in ultimately setting up an insurance framework. A better solution compared to third party insurance providers might be for Canadian exchange operators to create their own collective insurance fund, or a specific federal organization similar to the CDIC. Such an organization would have a greater interest or obligation in paying out actual cases, and that would be it's purpose rather than maximizing it's own profit. This would be similar to the SAFU which Binance has launched, except it would cover multiple exchanges. There is little question whether the SAFU would pay out given a breach of Binance, and a similar argument could be made for a insurance fund managed by a collective of exchange operators or a government organization. While a third party insurance provider has the strong market incentive to provide the absolute minimum coverage and no market incentive to payout, an entity managed by exchange operators would have incentive to protect the reputation of exchange operators/the industry, and the government should have the interest of protecting Canadians. On The Subject of Fractional Reserve There is a long history of fractional reserve failures, from the first banks in ancient times, through the great depression (where hundreds of fractional reserve banks failed), right through to the 2008 banking collapse referenced in the first bitcoin block. The fractional reserve system allows banks to multiply the money supply far beyond the actual cash (or other assets) in existence, backed only by a system of debt obligations of others. Safely supporting a fractional reserve system is a topic of far greater complexity than can be addressed by a simple policy, and when it comes to cryptocurrency, there is presently no entity reasonably able to bail anyone out in the event of failure. Therefore, this framework is addressed around entities that aim to maintain 100% backing of funds. There may be some firms that desire but have failed to maintain 100% backing. In this case, there are multiple solutions, including outside investment, merging with other exchanges, or enforcing a gradual restoration plan. All of these solutions are typically far better than shutting down the exchange, and there are multiple cases where they've been used successfully in the past. Proof of Reserves/Transparency/Accountability Canadians need to have visibility into the backing on an ongoing basis. The best solution for crypto-assets is a Proof of Reserve. Such ideas go back all the way to 2013, before even Mt. Gox. However, no Canadian exchange has yet implemented such a system, and only a few international exchanges (CoinFloor in the UK being an example) have. Many firms like Kraken, BitBuy, and now ShakePay use the Proof of Reserve term to refer to lesser proofs which do not actually cryptographically prove the full backing of all user assets on the blockchain. In order for a Proof of Reserve to be effective, it must actually be a complete proof, and it needs to be understood by the public that is expected to use it. Many firms have expressed reservations about the level of transparency required in a complete Proof of Reserve (for example Kraken here). While a complete Proof of Reserves should be encouraged, and there are some solutions in the works (ie TxQuick), this is unlikely to be suitable universally for all exchange operators and users. Given the limitations, and that firms also manage fiat assets, a more traditional audit process makes more sense. Some Canadian exchanges (CoinSquare, CoinBerry) have already subjected themselves to annual audits. However, these results are not presently shared publicly, and there is no guarantee over the process including all user assets or the integrity and independence of the auditor. The auditor has been typically not known, and in some cases, the identity of the auditor is protected by a NDA. Only in one case (BitBuy) was an actual report generated and publicly shared. There has been no attempt made to validate that user accounts provided during these audits have been complete or accurate. A fraudulent fractional exchange, or one which had suffered a breach they were unwilling to publicly accept (see CoinBene), could easily maintain a second set of books for auditors or simply exclude key accounts to pass an individual audit. The proposed solution would see a reporting standard which includes at a minimum - percentage of backing for each asset relative to account balances and the nature of how those assets are stored, with ownership proven by the auditor. The auditor would also publicly provide a "hash list", which they independently generate from the accounts provided by the exchange. Every exchange user can then check their information against this public "hash list". A hash is a one-way form of encryption, which fully protects the private information, yet allows anyone who knows that information already to validate that it was included. Less experienced users can take advantage of public tools to calculate the hash from their information (provided by the exchange), and thus have certainty that the auditor received their full balance information. Easy instructions can be provided. Auditors should be impartial, their identities and process public, and they should be rotated so that the same auditor is never used twice in a row. Balancing the cost of auditing against the needs for regular updates, a 6 month cycle likely makes the most sense. Hot Wallet Management The best solution for hot wallets is not to use them. CoinBerry reportedly uses multi-sig on all withdrawals, and Bitmex is an international example known for their structure devoid of hot wallets. However, many platforms and customers desire fast withdrawal processes, and human validation has a cost of time and delay in this process. A model of self-insurance or separate funds for hot wallets may be used in these cases. Under this model, a platform still has 100% of their client balance in cold storage and holds additional funds in hot wallets for quick withdrawal. Thus, the risk of those hot wallets is 100% on exchange operators and not affecting the exchange users. Since most platforms typically only have 1%-5% in hot wallets at any given time, it shouldn't be unreasonable to build/maintain these additional reserves over time using exchange fees or additional investment. Larger withdrawals would still be handled at regular intervals from the cold storage. Hot wallet risks have historically posed a large risk and there is no established standard to guarantee secure hot wallets. When the government of South Korea dispatched security inspections to multiple exchanges, the results were still that 3 of them got hacked after the inspections. If standards develop such that an organization in the market is willing to insure the hot wallets, this could provide an acceptable alternative. Another option may be for multiple exchange operators to pool funds aside for a hot wallet insurance fund. Comprehensive coverage standards must be established and maintained for all hot wallet balances to make sure Canadians are adequately protected.
Current Draft Proposal
(1) Proper multi-signature cold wallet storage. (a) Each private key is the personal and legal responsibility of one person - the “signatory”. Signatories have special rights and responsibilities to protect user assets. Signatories are trained and certified through a course covering (1) past hacking and fraud cases, (2) proper and secure key generation, and (3) proper safekeeping of private keys. All private keys must be generated and stored 100% offline by the signatory. If even one private keys is ever breached or suspected to be breached, the wallet must be regenerated and all funds relocated to a new wallet. (b) All signatories must be separate background-checked individuals free of past criminal conviction. Canadians should have a right to know who holds their funds. All signing of transactions must take place with all signatories on Canadian soil or on the soil of a country with a solid legal system which agrees to uphold and support these rules (from an established white-list of countries which expands over time). (c) 3-5 independent signatures are required for any withdrawal. There must be 1-3 spare signatories, and a maximum of 7 total signatories. The following are all valid combinations: 3of4, 3of5, 3of6, 4of5, 4of6, 4of7, 5of6, or 5of7. (d) A security audit should be conducted to validate the cold wallet is set up correctly and provide any additional pertinent information. The primary purpose is to ensure that all signatories are acting independently and using best practices for private key storage. A report summarizing all steps taken and who did the audit will be made public. Canadians must be able to validate the right measures are in place to protect their funds. (e) There is a simple approval process if signatories wish to visit any country outside Canada, with a potential whitelist of exempt countries. At most 2 signatories can be outside of aligned jurisdiction at any given time. All exchanges would be required to keep a compliant cold wallet for Canadian funds and have a Canadian office if they wish to serve Canadian customers. (2) Regular and transparent solvency audits. (a) An audit must be conducted at founding, after 3 months of operation, and at least once every 6 months to compare customer balances against all stored cryptocurrency and fiat balances. The auditor must be known, independent, and never the same twice in a row. (b) An audit report will be published featuring the steps conducted in a readable format. This should be made available to all Canadians on the exchange website and on a government website. The report must include what percentage of each customer asset is backed on the exchange, and how those funds are stored. (c) The auditor will independently produce a hash of each customer's identifying information and balance as they perform the audit. This will be made publicly available on the exchange and government website, along with simplified instructions that each customer can use to verify that their balance was included in the audit process. (d) The audit needs to include a proof of ownership for any cryptocurrency wallets included. A satoshi test (spending a small amount) or partially signed transaction both qualify. (e) Any platform without 100% reserves should be assessed on a regular basis by a government or industry watchdog. This entity should work to prevent any further drop, support any private investor to come in, or facilitate a merger so that 100% backing can be obtained as soon as possible. (3) Protections for hot wallets and transactions. (a) A standardized list of approved coins and procedures will be established to constitute valid cold storage wallets. Where a multi-sig process is not natively available, efforts will be undertaken to establish a suitable and stable smart contract standard. This list will be expanded and improved over time. Coins and procedures not on the list are considered hot wallets. (b) Hot wallets can be backed by additional funds in cold storage or an acceptable third-party insurance provider with a comprehensive coverage policy. (c) Exchanges are required to cover the full balance of all user funds as denominated in the same currency, or double the balance as denominated in bitcoin or CAD using an established trading rate. If the balance is ever insufficient due to market movements, the firm must rectify this within 24 hours by moving assets to cold storage or increasing insurance coverage. (d) Any large transactions (above a set threshold) from cold storage to any new wallet addresses (not previously transacted with) must be tested with a smaller transaction first. Deposits of cryptocurrency must be limited to prevent economic 51% attacks. Any issues are to be covered by the exchange. (e) Exchange platforms must provide suitable authentication for users, including making available approved forms of two-factor authentication. SMS-based authentication is not to be supported. Withdrawals must be blocked for 48 hours in the event of any account password change. Disputes on the negligence of exchanges should be governed by case law.
Continued review of existing OSC feedback is still underway. More feedback and opinions on the framework and ideas as presented here are extremely valuable. The above is a draft and not finalized. The process of further developing and bringing a suitable framework to protect Canadians will require the support of exchange operators, legal experts, and many others in the community. The costs of not doing such are tremendous. A large and convoluted framework, one based on flawed ideas or implementation, or one which fails to properly safeguard Canadians is not just extremely expensive and risky for all Canadians, severely limiting to the credibility and reputation of the industry, but an existential risk to many exchanges. The responsibility falls to all of us to provide our insight and make our opinions heard on this critical matter. Please take the time to give your thoughts.
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:
HTML (HyperText Markup Language) - it's what almost all websites use as a foundation. This is not a programming language, but it is a markup language. If you want to build websites, you pretty much have to know this language. Don't worry though, it is easy. Not so much to learn. You can learn all about it in a few weeks.
CSS (Cascading Style Sheets) - it's what will add colors and shapes to your website. If you want to focus more on design (also known as front end development) then this is where you want to gain a lot of knowledge.
Python - A very simple language to learn. This language is very often the first programming language that developers start using. You can use it for a lot of things. This language is used in the back of a lot of websites. Google has been using Python for years and still is. It's great for web scraping and making web requests. If you want a language to practice your algorithms, then this language is awesome.
PHP - This used to be a very popular language, but not so much these days. However, it is very good to know how this works because it's very simple to learn and also very functional in some cases. If you want to transmit or withdraw information from a database to your website, then this (in combination with SQL) is a great way to do so. Whenever you make a login system or a contact form, the data must be sent somehow to a recipient or a database. PHP will help you do that. It is a server-side language, which means it will run in the back of the website.
SQL - To be able to communicate with databases (for example: save data, update data, or insert data) you can use different languages for that. But SQL is probably the most widely used language for this. It is basically just a bunch of commands that you tell your website or app to do. If you have a web shop for example, you will need a database to store all your product information in. You can for example use MySQL as your database and then use the SQL language to extract data from your database and publish it as a list of products on your website.
Java - This is pretty much 90% identical to C# as I wrote above. Widely used, relatively easy to learn the basics and there's plenty of jobs. If you like making android apps, this language is for you.
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.
Text editor: Visual Studio Code, Atom, Sublime Text, Brackets - There are many different text editors but at the moment, I highly recommend Visual Studio Code. It has so many built-in features it's honestly the only thing you may need.Don't forget to install Notepad++ as well - this very basic editor is so handy when you just quickly need to edit some files.
File archiving: WinRar, 7-Zip - You need some way of archiving projects and send it to your customer or employer. These are basic tools anyone should use. I personally use Winrar.
FTP (File Transfer Protocol): FileZilla - This tool will allow you to connect to your website's file manager and upload your files to it. There are many tools for connecting to an FTP server but this is the most popular one, it's simple and it works great.
VPS (Virtual Private Server): Amazon Web Services, Google Cloud - If you want to practice building web applications or want to host your own website as a fun project, it's great to use a VPS for that. Both Amazon and Google offers 365 days of free VPS usage. All you need is a credit card. However, they will not charge you, as long as you stay below the free tier limit. A VPS is basically a remote computer that you can connect to. I highly recommend that, if you have a slow internet connection. Those VPS-servers (by Amazon and Google) usually have 500mbit/s internet speed, which is faster than most countries in the world. You simply connect to them via Remote Desktop, or by SSH. Depending on what type of server you are using (Windows or Linux).
SSH (Secure Shell): Solar-PuTTY, PuTTY - If you for example have a web server where you store applications and files, a great way to connect to it is by using SSH. PuTTY is pretty much the standard when it comes to SSH clients. But I really love the version created by SolarWinds. When you download that one, do not enter your personal details. Their sales people will call you and haunt you! Haha.
File Searching: Agent Ransack - When you have many files and try to locate a specific document or file, you may want to use something like Agent Ransack. Much faster than the traditional search feature in Windows and it is much more accurate.
IDE / Code Editor: Visual Studio - Great tool to use when you want to create applications in C# for example. Do not confuse this with Visual Studio Code. These are two very different tools. This tool (Visual Studio) is more designed for Windows applications. Not just websites. I only recommend getting it if you plan to make programs for Windows.
Web host & domain: NameCheap, Epik, SiteGround - If you develop websites on your own, or maybe want to create a portfolio website, you will need a domain name and web hosting. I have personally used all of these 3 and they are very cheap. NameCheap has some of the cheapest domains and great web hosting for a low price. Their support is also great. Same with SiteGround. And if you want to buy a domain anonymously (with Bitcoin for example), then you can use Epik. Low prices and great customer service on all these 3 websites.
Web Browser: Mozilla Firefox, Microsoft Edge Insider, Google Chrome - You need one of the latest web browsers to create websites these days. Since I prefer privacy over functionality, I've always loved Firefox. But recently, Microsoft has been improving its new version of Edge a lot (based on Chromium) and it's also very popular. If you want all your personal details to be saved and have good tools for web development, then use Google Chrome. Don't forget to utilize the built-in developer tools. You can access it in any of these browsers by pressing F12.
Other things you may want to look into:
Web services, SSL certificates, Search Engine Optimization, Databases, API, Algorithms, Data Structures
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.
Thai Nhat Minh | Stably: First of all, can you have a brief introduction about yourself as well as about Chromia? Henrik_hjelte, Sergelubkin Henrik Hjelte: Hello. My name is Henrik Hjelte. I am Co-Founder and CEO of Chromia. I have more than 30 years of experience in programming and a degree in Economics from Uppsala University. BTW economics and computers = blockchain, so finally found a job that fits me. I was introduced to the blockchain by the leader of the colored-coins project Alex Mizrahi in 2013 Colored coins project was a very influential thing It was the first way for user created tokens bolted on to the only blockchain at the time (almost) bitcoin We started ChromaWay 2014, with Or Perelman too, to explore if the world was interested in “tokens” and those kind of applications We worked with enterprise blockchain for some time, but now we are focused on Chromia, a new public platform for mainstream decentralized applications using relational blockchain technology. Ok, maybe I should tell something about Chromia and not myself too. Chromia is a better blockchain for building decentralized Apps. better because it follows the “normal worlds” way of managing data. A little history: I found a text/description to paste: Chromia is a brainchild of ChromaWay. ChromaWay has a long record of delivering pioneering projects around the world. We issued Euros on the Bitcoin blockchain with LHV bank, allowed investors to invest in startups in a wholly decentralized way with Funderbeam, digitized the title transfer process with the Swedish land registry, and mediated the green bond market. ChromaWay’s core team created the world’s first protocol to issue tokens already in 2012, when blockchain was called “bitcoin 2.0”. Then ChromaWay introduced the relational model to enterprise blockchains with a consortium database called Postchain. Now Postchain is going public as the foundation for Chromia, a better blockchain for building decentralised Apps. Chromia is a new public blockchain based on the idea of integrating traditional databases, Relational databases with blockchain security. Chromia is a general purpose blockchain with full smart contract capabilities, just that it is a lot easier to code, even complex applications. You code with an easy to learn new programming language that combines the power of SQL and normal languages but makes it secure in a blockchain context. Up to 1/10 the code-lines vs other blockchains. If you don’t believe me, check this blog (later, stay in the chat): https://blog.chromia.com/reasons-for-rell-compactness/ The aim of Chromia is to combine relational databases, which exist in every kind of organization, with blockchains. We want to provide a platform for our users to develop totally decentralized apps securely. Our goal is for Chromia to be seen as the number one infrastructure for decentralized applications. Think about it: blockchain is about managing data (in a shared context). And… What do we use to manage data? A Database! Serge: Sure! My name is Serge! And I work in Chromia marketing department. Also, I help coordinate various projects inside the company My background is in Economics and Marketing Thai Nhat Minh | Stably: Question 1️⃣ DApp is currently mainly concentrated in the field of games, and its life cycle is basically short, just like the Crypto Kitty is only hot for a while, how to dig the application of DApp in more fields and how to improve the utilization rate of DApp? u/henrik_hjelteu/sergelubkin Serge: Good one, let me answer Gaming is quite a challenging target because good UX is expected, it needs to be fast, responsive, etc. If we can do that, then we can also do all sorts of other stuff. Also, it lets us experiment with things without a lot of hassle, it’s easier to get users, and so on. It’s also a growing niche within blockchain. You can check our latest game, Mines of Dalarnia https://www.minesofdalarnia.com We also have Enterprise projects already, for example Green Assets Wallet https://greenassetswallet.org/about that already launched on the first Mainnet version called Bootstrap Net,we also have https://capchap.se built on our tech, more projects like non-profit review platform Impactoria, public land registries, medical projects and so on Also don’t forget about our fully decentralized social network/forum that is live already on the testnet https://testnet.chromunity.com. Thai Nhat Minh | Stably: Question 2️⃣ How will dapp face the world change after the epidemic? u/henrik_hjelteu/sergelubkin Henrik Hjelte: Nobody can say for sure, but maybe people will tend to be online more than offline, so demand on online products and dapps as well will increase. I just came in from an internal demo of a secret project we do, and it can be seen as a way to hang out online (a bit cryptic answer) There are also interesting use cases of dapps in the medical field. For example, we participated in the world-wide hackathon Hack for Sweden. Where our submission was to create an app on Chromia blockchain that increases the coordination between countries and hospitals especially during the hard time and COVID19. Chromia wants to help the European Union (and the world, but we saw problems in the EU…) and its citizens to provide transparency over the necessary medical and protective devices and appliances of which we see shortage during this emergency crisis. You can watch our promo here https://twitter.com/chromaway/status/1247557274337447938?s=20. For me it was a fun Hackathon too because for once I got the opportunity to code… I told everyone else I will not do any bossing… We try to continue this path on medical applications a bit. Thai Nhat Minh | Stably: Question 3️⃣ DApps are still not directly embedded in mobile phones like Apps at this moment, and DApps have also been flooded with bet content. How can guests increase the use of DApps and lower the threshold for using DApps? u/henrik_hjelteu/sergelubkin Serge: The answer is — better User Experience. We believe that in order for a DApp to be usable and become more widely accepted it has to feel like a normal App. A DApp needs to have quick transactions, scale well & shouldn’t require users to pay for each transaction. This is something that is possible now with using Chromia. It’s an extremely exciting time since we are going to see a new generation of DApps. On top of that, we think that we might have an ace coming up. We have built a game to demonstrate the powers and possibilities of Chromia. A little bit about the game: In Mines of Dalarnia (https://www.minesofdalarnia.com), players get to explore the vast expanses of interplanetary treasure mines. With an innovative Dalarnia Token system, players can purchase virtual mining plots, and put them up for rent into the community, allowing for real-estate tycoons to earn more Tokens. Mining plots can also undergo their own upgrades, making them more lucrative to explore, as well as a hot property for rental by miners. The game takes advantage of these NFT-based tokens to securely track exchanges, and provide a sense of ownership and wealth to players as they grow their mining and resource empire. Watch our trailer https://youtu.be/bDXKOp1Asqw and sign-up for the TestNet on the website! Thai Nhat Minh | Stably: Question 4️⃣ Many practitioners think that the main reason for restricting the development of DApp is “incomplete infrastructure”. How effective is the current “cross-chain” and “side-chain” solution? u/henrik_hjelteu/sergelubkin Serge: Our infrastructure resembles Alibaba Cloud, so a DApp developer just goes and deploys his DApp’s blockchain into it, it’s easy. Also our language Rell https://rell.chromia.com/en/maste is more robust than any other blockchain programming language.Or Azure or AWS Rell combines the following features:
Relational data modeling and queries similar to SQL. People familiar with SQL should feel at home once they learn the new syntax.
Normal programming constructs: variables, loops, functions, collections, etc.
Constructs which specifically target application backends and, in particular, blockchain-style programming including request routing, authorization, etc.
We want people to join our channels such as telegram, twitter, email also our decentralized forum https://testnet.chromunity.com and participate in discussions
We want people to try our dapps such as Mines of Dalarnia
We want to get feedback and understand the most important issues people care about Chromia and the blockchain industry in general
We want to get more developers building on top of Chromia
LBTS: What was your motivation for creating RELL and not use other languages? What benefits? Why name it RELL also? Henrik Hjelte: We have a private/federated relational blockchain called Postchain, and it allows SQL. But that can work in a small environment when you know all parties, and if you are really careful in checking code. But not for a more secure, distributed on the web setup, so we had to make it more secure (Deterministic, statically typed). In the process, we also took the opportunity to make it cool and nice. Also: it is simply not possibly to use evm, jvm, or web assembly. We need/want a database in the bottom. Postgresql is our virtual machine. You do not reimplement that…. 10+ years codebase…. Lee: Being part of the gamer community, I would like to know what you would think about collaborating with a MOBA, RPG or Arcade game or some kind of project? Henrik Hjelte: We are already collaborating with some smaller studios. For bigger fish, we want to show them what is completely unique and visionary with Chromia, and we think we need various examples. So, first arcade game MoD (linked above) is one example, it is not the full potential or anything but a start. In this summer, krystopia 2 a puzzle game from Antler Interactive will be released. What is even cooler is the “demo project” we do together with them, where we will show how a mutliplayer game with real blockchain features will work. I just saw it an hour ago and was blown away OH, and there is another studio releasing something very cool. Full logic on chain strategy game. Chain of Alliance. oyibo pepper: Do you encourage HACKATHON programs for intending Developers to test their skills and build on RELL Can you explain more about CHROMIA AMBASSADORS PROGRAM, CAN I BECOME AN AMBASSADOR Serge: Yes, you can, but you will need to change your avatar 🤣 Seriously, we are growing our Chromians community if you want to become one please ping our admins in Chromia telegram group. Also, we are planning virtual hackathons soon, please subscribe to stay updated Infinite Crypto: Since the Chromia project is currently working on the Ethereum blockchain ERC20 standard! But we know that there are a lot of scalability issues with Ethereum, so why would you choose the Ethereum blockchain over other scalable blockchains? Do you have any plans for Mainnet launch of Chromia? Henrik Hjelte: ETH is just used in a pre-phase for tokens. We will have our own mainnet tokens interchangable with ETH. Oyinbo pepper What’s CHROMIA SSO and SDK, how can I get started Henrik Hjelte Both are 3 letters. That is what they have in common. SDK = software development kit, check docs on https://rell.chromia.com SSO = single sign on. A unique UX improvement. You approve an app in your wallet (vault) with super ease. no need to remember codes sso: https://blog.chromia.com/chromia-sso-the-whys-and-the-whats/ We have a fundamentally different model from bitcoin and ethereum and the likes. The blockchain is not run by anonymous computers in basement and student dorms across the world. We have more of known identities, so 51% attacks is protected not by PoW/PoS but other consensus. Please see our whitepaper. Note that we are not noobs when it comes to this, our CTO Alex has published papers in academic journals on consensus etc. from 2013, and done several important ideas for blockchain. Sidechains we think he was first with, tokens too. Sheron Fernando: Is there any plan to makes partnership with local cryptocurrency developers from each country to make $CHR usage more worldwide? Serge: Yes, we are looking for cooperation with more external developers. Send me a message if you are interested in developing something on Chromia. Stella: What are the underlying problems in the Dapps today that can be solved with the Chromia protocol? Serge:
Scalability — on Chromia your dapp can have unlimited numbers of users thanks to parallel scaling
Easiness of use — you don’t need external wallets, no need to buy crypto to pay for gas etc
Cost — in general to deploy the dapp and to use the dapp
Marcel Lagacé: Why build this platform? What is Chromia mission? What are the most prominent features of the platform? Can you clarify the use case for this feature? Henrik Hjelte: We build the platform to fix the problems with blockchains, that we ourselves have experienced since 2014 (before ethereum existed). LBTS: Can you tell us about Chromia developers? How motivated and experienced are they to always deliver the best products? Henrik Hjelte: I can tell you that we recruit developers that are really good, from all parts of the world. Vietnam has been a hub because we found many good, so in Ukraine. How can we say “we have so good developers”? First one thing that is a bit different is that we are pretty experienced in leadership team of development. I do not code much anymore since I’m a CEO. But I do have now over 30 years of experience. Got published and was payed when I was 15. First full-time professional developer job at 18. Have released open-source projects used by 10: s of thousand developers. And Alex, our CTO is Extremely good. That is why I recruited him to my old startup 2006 or so… So: we have experience to sort out good developers from bad. Marcel Lagacé: Does Chromia staking model is different from other staking platform?? What are the beneficial advantages of chromia staking system? Serge: The main difference is that we have independent Providers, entities that are not connected. These serious players are exchanges, data centres, professional staking companies. They provide a backbone of the ecosystem and host dapps. Like Amazon servers in the cloud. They cannot have stake bigger than the maximum thus they can’t control the network. This is probably the main difference with classic DPoS networks Nguyen Duy Bao: A lot of people will want to know what the strength of Chromia is but I want to know the weaknesses and problems Chromia faces ? How do you plan to solve it? Henrik Hjelte: A weakness I guess is weak compared to “competition”. And there are some blockchain projects that got crazy amount of funding. So how can we compete with that, when they can hire more developers for example? Well here is what experience comes into play: More developers does not always increase productivity a lot, it is diminishing returns. You can see many large projects, with 100 of developers fail miserably with no results. And actually, sometimes true with marketing spend too. It is generally good with money, but if you are a bit clever you can compete also on marketing with less money than your competition. Please follow Chromia on Social Media: Website: https://www.chromia.com Twitter: https://twitter.com/chromia FaceBook: https://www.facebook.com/teamchromia LinkedIn: https://www.linkedin.com/company/chromia Telegram: https://t.me/hellochromia Decentralized Social network Chromunity: https://testnet.chromunity.com Free-to-Play Blockchain Game Mines of Dalarnia: https://www.minesofdalarnia.com
HEX is the principal endorsement of store on the blockchain! HEX pays Trustless Interest with no counterparty chance. Given programmable cash the principal program ought to be premium. Pays holders rather than diggers. Staking HEX resembles getting free mining equipment and power. Bitcoin and HEX correlation No Satoshi (on the off chance that he doesn't guarantee in 50 weeks) or Mt.Gox dumping on you. No swelling bug conceivable like bitcoin has had. Unit predisposition fixed. Progressively disseminated mining environment. Whale punishment which gives whales coins to stakers, and so forth. Around 12 million or more of the 18 million all out BTC worth of HEX cases will be given to the stakers on day 353 by shares. What's more, It gets duplicated by the Viral and CriticalMass selection extra multipliers which can build it up to 3x. The offer cost just goes up. Stakers that end stake early or late compensation faithful stakers. Longer stake submit pays 20% more every year, up to 3x shares, (halfway years are fine). Lower charges, lower swelling. Referral program. Organizer is a showcasing master with a crowd of people. Early adopters get paid amazingly well. 20% Speed reward tumbling to 0% during the fifty weeks. Unclaimed coins paid to stakers 2% every week for 50 weeks. Consistently you don't guarantee, another person gets your coins. Minimum amount and Virality rewards increment payouts to stakers so they make progressively HEX the more individuals that guarantee, than if less individuals asserted, despite the fact that they get unclaimed coins on day 353. Each pumpamental to bolt up supply, increment reception and cost. Hex has a lower expansion rate than Bitcoin, much after the rate was sliced down the middle twice in its 10 years. The swelling is additionally deferred, in light of the fact that it's just paid on finished stakes, and stakes can most recent 10 years. Failure to exchange staked coins builds the estimation of unstaked coins, and chance that some will early endstake and take care of punishments to faithful stakers. Trustless Interest. Suppose you need to make more bitcoin on your bitcoin. What are your alternatives? You could loan your coins out and face the challenge they're not returned, or you could have a go at selling your coins for mining equipment and want to get more coins back later. Bunches of individuals have lost cash attempting either. Counterparty hazard in Bitcoin ventures. To acquire enthusiasm on their Bitcoin, most clients send them to a brought together outsider, for example, a trade. There, coins can be acquired to "short" the market. Merchants acquire the coins to sell, in the expectations that they can rebuy them less expensive before they need to return them, along these lines benefitting from value diminishes. These brought together gatherings are security openings that are frequently hacked, annihilate protection, or acquaint expenses on the off chance that you need with get your assets out. Billions of dollars in coins sent to trades or loan specialists have been taken. Not your keys, not your coins. These concentrated outsiders and brokers are so essential to clients looking for yield (making interest) that the organizations themselves have made more benefit on Bitcoin than its originator. A huge number of dollars of significant worth has moved into the pockets of brokers. HEX fixes this. This replaces these outsiders with a trustless distributed to framework. Rather than sending your HEX to a trade so they can loan it out for your sake to procure enthusiasm for you, you simply lock it in same brilliant agreement that stamped all the HEX in any case, and it credits you intrigue. In case you're given programmable cash, the principal thing you should program is premium. HEX pays enthusiasm to stakers rather than excavators. A few clients take a stab at mining to make more digital money. Rather than sending your cash to a remote super corp to purchase mining gear which appears late, utilized, or never by any stretch of the imagination, you can avoid the deteriorating resource and power bills and simply stake your coins. HEX is the primary digital currency with a graph of future sellable stockpile (lapsing stakes after some time.) This makes sure about purchasers trust in future estimation of their speculation. HEX has Speculative Stickiness. Typical cryptographic forms of money have: Price, hash rate. HEX has: HEX value, Share cost, Directly influences staker benefit per share: % of supply staking, Average stake length, Average stake size, stake termination diagram after some time, early and late end stake punishments. HEX links: Website: https://hex.win/ Twitter page: https://twitter.com/HEXCrypto Facebook page: https://www.facebook.com/HEXcrypto Telegram page: https://t.me/HEXcrypto Github: https://github.com/bitcoinHEX Reddit page: https://hexcrypto.reddit.com/ Medium page: https://medium.com/hex-crypto/ Ann: https://bitcointalk.org/index.php?topic=4523610.0 Author information; Bitcointalk username: TridentHorn Bitcointalk profile: https://bitcointalk.org/index.php?topic=4523610.0
AMA Recap of CEO and Co-founder of Chromia, Henrik Hjelte in the @binancenigeria Telegram group on 03/05/2020.
This is similar to our previous ESP8266 bitcoin example – Basic ESP8266 and bitcoin price example. We used the same Wemos board as in the previous example. In this example we use ArduinoJson library to parse the json response from coindesk. A better approach than the previous example Bitcoin mining is a transaction record process with bitcoins to blockchain – the public database of all the operations with Bitcoin, which is responsible for the transaction confirmation. Network nodes use blockchain to differ the real transactions from the attempt to spend the same facilities twice. The main mining objective is reaching a consensus between network nodes on which ... You have three choices to display bitcoin payment box/data on your webpage/applications - By Using html Iframe bitcoin payment box. Example below »; By using JSON data Client Side (jquery ajax) - Customize box / black & white themes / generate php code here (bottom of page). Instruction here; JSON Server Side (php curl method) - Alternatively, you can receive JSON values through curl on ... Anyone can use bitcoin without paying any process fees. If you are handling Bitcoin, the sender and receiver transact directly without using a third party. BlockChain and Bitcoin: The blockchain is the technology behind Bitcoin. Bitcoin is the digital token, and blockchain is the ledger that keeps track of who owns the digital tokens. PHP program to BITCOIN, PEER TO PEER DONATION, TWINKAS, PAYARENA, GETHELP, PONZI SCRIPTwe are provide a PHP program tutorial with example.Implement BITCOIN, PEER TO PEER DONATION, TWINKAS, PAYARENA, GETHELP, PONZI SCRIPT program in PHP.Download BITCOIN, PEER TO PEER DONATION, TWINKAS, PAYARENA, GETHELP, PONZI SCRIPT web application project in PHP with source code .BITCOIN, PEER TO PEER ...
Tutorial - Building Bitcoin Websites - How to Get The Price 1 of 2
Ethereum, for example, enables users to store code snippets called 'smart contracts' in their blockchain. In this video, we'll build a simple blockchain in Python that uses proof-of-work consensus ... Creating a Local Bitcoin Testnet / Regtest - Programming Bitcoin - Duration: 23:19. Programming Bitcoin 19,454 views. 23:19. Understanding Shoulder Pain and How To Fix It - Duration: 13:48. This is the first part of a more technical talk where Andreas explores Bitcoin script, with examples from the 2nd edition of Mastering Bitcoin, focusing on the use of conditional statements, flow ... How to integrate the bitcoin trading api in php TechiesBadi. ... for example if you want the trade the bitcoin in USD ... Programming in Visual Basic .Net How to Connect Access Database to VB ... With bitcoin, however, it is used to secure the blockchain, requiring that someone must re-do large amounts of computer processing to fake things in the blockchain.