Hiya folks! Hope the shelter-at-home is treating you well. As you might know that the super cyclone Amphan struck Eastern India and Bangladesh day before yesterday. As a result, I went into radio silence for two days. Now that I am back in the grid (albeit with ultra-super slow internet; this post took 4+ hours of retries just to upload pictures), let’s get rolling with the weekly update catch-up series again. Here’s your week at Parachute + partners (17 Apr - 23 Apr'20):submitted by abhijoysarkar to ParachuteToken [link] [comments]
24 cryptocurrencies are now live on ParJar for trading with fiat in Europe, India and UK. This is massive! The new ParJar and #cryptoforeveryone masks look great Clinton! Designers in Parachute, Clinton is looking for fresh original designs for merchandise in the Parachute Shop. You can bag some cool $PAR and discount codes if your art makes it to the store. The #par4par raffle currently has a 500k $PAR prize pool. If you have 10k $PAR in your ParJar, you can claim a ticket. Get in on it! Foo hosted a Parena so that winners can get a taste of the raffle with their prize $PAR. Bose hosted a random TTR trivia this week for a 10k $PAR prize pot. Don't forget her rules: "you argue and you're wrong, you skip next question". Gamerboy's Tiproom quiz theme was a secret. Did you find out what it was? Charlotte’s Tuesday TTR trivia was fun as always. Victor hosted an animal-themed trivia for 1k $PAR in prize per question. Two-for-Tuesday continued with the ongoing series of letters. This week Gian got Parachuters to post music "featuring bands or artists whose name starts with the letters M, N, O or P". As always, super thankful for the playlist Sebastian! 136 music videos in total. Dang! Jason’s #wholesomewed prompt involved Parachuters sharing unconventional art pieces. "They can be made by you or someone else".
Visit the Parachute Shop for more epic merch like these
Uber cool #wholesomewed entries by (clockwise from top left) Fakhir, Erol, Pars, Georg, Eric, OilJam, Peace Love
Click here to track this week’s aXpire burn transaction. CEO Gary Markham wrote about Time Recording in his latest blog post. More insights into 2gether’s study about women in crypto were released. This is part of their original study report on female crypto consumers which was first published in March. $BOMB founder Zachary Dash set the ball rolling on a proposal system for brainstorming on ideas for the project. Click here for a sample proposal. For #XIOSocial discussions, Citizens talked about what interest rate would be ideal for $XIO when the dApp launches. $LINK was added to Voyager’s platform this week. Click here for the full range of available assets. Voyager also featured in MyFirstBitcoin.info's list of "Where To Buy Bitcoin". They also launched an integration with crypto trading education platform Market Rebellion this week. Switch announced that $ESH token holders will be eligible to claim John McAfee-backed $GHOST coins on 25th May. News of Ghost’s launch was shared in bitcoin.com, Cointelegraph, CoinPedia, Crypto News Flash and CryptoNewsZ. Neva Fomo’s review of SwitchDex was released this week. The winners of the #BUIDLonFantom Developer contest were announced this week. The FantomVision block explorer was upgraded to a Progressive Web App (PWA) which can be installed on your device as an application. The team hosted a monthly AMA in their Discord. This will be happening every month from now. A new technical paper on smart was contracts was published as well.
Bitcoin is a clear favourite for trading among female users
Bounty0x’s fundraiser on Republic came to a close this week with funding crossing over targeted amount by nearly three times. Founder Angelo Adam also shared a sneak peek into how the Hypedia platform could look like. Uptrennd Head of Community, Luke, started an #InfectedWithGratitude giveaway that brought 2 days of wholesome joy to the community. Founder Jeff Kirdeikis sat down for an Altcoin Buzz interview to talk all things crypto. IOST joined Uptrennd this week. Coingecko joined in the fun too. Awesome! Congratulations on onboarding 30k+ new users in 2020 alone. The team also set the ball rolling for a community-powered blockchain awards. The District0x District Weekly can be read here. Meme Factory now has a fixture inside the virtual world of Cryptovoxels. Hydro made it to the semifinal round of Ground Up Ventures’ March Madness Startup Competition. Congrats! With news of Google’s smart debit card leaking out recently, the team at Hydro discussed the implications of the tech giant entering digital banking. They also wrote at length about FinTech in Brazil and strategies to bank the unbanked. The team also made a presentation at the Canada FinTech Summit this week. For the latest Sentivate development updates click here, here, here and here. SelfKey’s $KEY token was listed on Kyber Network this week. Read more details here. The team opened up an AMA questionnaire form for the community. AMA date not decided yet. They are also hiring currently. Apply if you’re up for it. SimpleSwap listed $KEY and joined SelfKey’s Crypto Exchange Marketplace. To learn more about Constellation’s ERC20 to mainnet $DAG swap, click here. COTI crew sat down for an AMA with KuCoin this week. The KuCoin staking campaign (announced last week) reached its cap within 5 minutes of opening up. If you were hoping to be a mode operator, hope you reached out to the team on time. To read the fee policy, click here. $COTI will be listed on Coinbit next week. Main registration for Staking 2.0 was started.
The Hypedia mockups look great!
Pynk is now SEIS/EIS approved which entitles investors in its fundraise round to tax benefits. Wibson hosted an online meetup with Crypto Resources Academy for their Spanish community. This was followed by an ETHSantiago meetup to discuss data privacy. Harmony founder Stephen Tse was part of a Miami DevCon Fintech panel to talk about DeFi and blockchain in finance. Also, congratulations on becoming the top blockchain project by GitHub activity. Stake Heist was formally opened with bounties to find bugs in the Open Staking Testnet Network and build stuff on it for some sweet $ONE. Delegators were also invited to test the staking dashboard in return for $ONE prizes. Watch more about it here. $ONE got listed on WazirX. Ankr published a comprehensive Open Staking node setup guide. Another major announcement this week was that a chunk of block rewards from staking in the phase 2 testnet will be converted to mainnet $ONE. Woohoo! Click here for an early sneak peek into the new IntelliShare website. A quick introduction of the testnet Pacific Program was also released. In his latest article, GET Protocol CEO Maarten Bloemers expanded on the significance of contactless ticketing in the post-coronavirus world. The article was an excerpt from the team’s submission to the Dutch Ministry of Public Health, Welfare and Sport to explore possible opportunities. Maarten was interviewed by HKB News of Korea where talked about all things GET. Their crowd management solution was featured on Cointelegraph as well.
And with that, we have to say Bye for now. See you again with another update. Cheerio!
pip3 install -r requirements.txt python3 bip39\_gui.py
https://preview.redd.it/hml53mmh5er41.png?width=568&format=png&auto=webp&s=3f0cd662e1836bcb2ea37793cbbbfd6f8a5e9723submitted by Floris-Jan to aelfofficial [link] [comments]
It’s always great to hang out in this group. This group means a lot to the Aelf community. It is the first Aelf community and has been there through all the ups and downs in the world. I would like to start with wishing everyone is staying safe at home during the virus outbreak. It definitely has been a difficult time for all of us, but together we can pull through it.
We understand that the situation is quite striking to all of us. But I really believe that the solution to the virus outbreak is about more global coordination and collaboration.
All of you to be assured, our team in different places are all safe and working from home as normal.
The Aelf team in Beijing were among the early ones experiencing the virus outbreak. As everyone was on the way home for Lunar New Year holiday and then experienced a total city lock-down followed by a 40 days’ work from home policy. It was definitely not easy for them, but our team stayed strong, took necessary precautions and focused on work with the right morale. Mappo has recently published some tips on how to work from home effectively based on our experience. Do check it out. Despite not working in the office since February, we have achieved great progress, including launching Aelf 1.0 preview, which is an important milestone in technical delivery and also the roadmap to mainnet launch (which listed out the essential steps for the community to work together to launch a successful public network)
Let's first talk about Aelf v1.0 preview. It is the cornerstone of the mainnet launch. The product itself has all the features that the public network is needed. The codebase has been reviewed and tested rigorously by the team. And a few highlights of how the network would look like:
So how are we going to help the community launch the network:
First of all, we have launched the codes, documents about the economic system and governance model and technical features. With all the things available, you are able to understand what the system is about, as a token holder what's your benefit in the system, and being a node in the system plays a big role in the governance
Next, without yet electing the nodes, we will get all token holders to join the current Aelf network through a mapping event. That means as long as you have Aelf tokens, you will be able to get 1:1 test tokens on the public testnet. that gives you full access to all the features, and you will feel like you are already using the mainnet. You will get rewarded in making transactions, voting, etc.
Do try out the Aelf wallet and voting features, you will see how easy to transfer tokens cross-chain. and also how flexible the system allows people to make changes. For example, the community may want to adjust the block rewarding parameters or fees to use certain services on mainnet, they can initiate a discussion and then vote in the system and once voted through, it will be reflected on mainnet.
For people or organizations that want to play a bigger role in the system, we will do a dry run of node election. Take it as the real node election before mainnet launch. We will see who the active members of the community are and being trusted by the community. Among the nodes, we will form a network launch committee. The committee will be the crucial party to oversees and ensures the smooth launch of Aelf mainnet, instead of just relying on the Aelf team. This is our step towards decentralization.
The committee will agree on the actual launch process, final checking all the parameters in the system to be ready for launch and then decide when the criteria are met to launch the network. Once all that is decided. We will invite all interested nodes to apply for the election and let the community know what's their plan to grow the Aelf network. the network will initially be launched with a few nodes from the committee and gradually be replaced by the selected nodes (a bootstrap phase). Along the way, we will work with exchanges to conduct token swap (which we are also designing an innovative system to further enhance security and usability of Aelf tokens in exchanges)
Among this isolated and worrisome time, at least we all have something to look forward to: a successful launch of Aelf network! Once it is launched, we are excited to see a vibrant and technically superior network that is good for Dapps to run on top of it.
Doris Guo Q1: As a Blockchain start-up, what difficulties have you overcome when starting Aelf project? What motivates you to solve difficulties and achieve success today?
Zhuling Chen First, just like launching any start-up, its community and investors are usually regional. There is always some bias on if Asian projects are solid. It is really rare to have an Asian project to be supported by western funds and community from day 1. We were lucky to have overcome that obstacle. Having a global investor line-up from day 1. Having a global team from day 1 and also working with a global community from day 1. This benefited us to have an international perspective which is crucial in the blockchain industry.
Secondly, as a hardcore technology company, it is really hard to put in plain words what is our ambition. Our ambition is huge, achieving key innovations in multiple fronts of blockchain technology and organically combined them to serve real users for the future. Our marketing team has been working really hard to elaborate on what Aelf is. Now we have come to a point that the product is ready. Therefore, it is much easier for all of us to understand how solid Aelf is by trying out the network ourselves! That's exactly what the following events will be about - Try out all the exciting features of Aelf network before mainnet launch.
Doris Guo Q2: What critical problems do you see occurring in the blockchain industry nowadays? How does Aelf solve these problems?
Haobo Ma First, we need to distinguish the difference between BTC and ETH. One is Digital Cash and the other is the Smart Contract Platform. Aelf addresses most of the latter's problems. In short, it can be summarized as performance, end-user friendly, developer-friendly, network economy, and self-governance and upgrading. Each of these areas will probably take up a lot of space, and as a whole are the issues described in our two white papers. In short, Aelf is faster, end-users do not need to know the rules of the blockchain, developers can set up the development environment in 10 minutes, have a good economic model and can carry out proposal governance on the chain.
Doris Guo Q3: What is your long-term vision about the industry which Aelf is working at? Are you afraid someday there will be another project with more innovative technology can replace Aelf?
Haobo Ma Let's talk about where Aelf stands in the traditional Internet. It is essentially a cloud service provider, Aelf provides resources and infrastructure for developers to deploy their services, known as smart contracts. We eventually want Aelf to grow like AAA (Amazon, Azure, AliCloud). Because Aelf is a network that can be dynamically scaled, we can accept any new technology, some of the more advanced technologies we can put on a side chain.
Doris Guo Q4: Why did Aelf choose for cross-chain interaction?
Haobo Ma As I mentioned earlier, Aelf solves the Smart Contract Platform problem. However, there are other digital cash problems as well which we would need to use existing infrastructure such as Bitcoin's chain in order to interact with Bitcoin. There are a lot of infrastructures on Ethereum that we want to interact with. Multi-chain on Aelf network mainly is to isolate resources to improve network performance and network stability.
Doris Guo Q5: What difficulties do the Aelf team have now (I talk about COVID-19)? How does the Aelf team solve it? Have you changed the roadmap?
Haobo Ma There is no great impact. The teams in Singapore and Beijing are communicating with each other remotely on a regular basis. The only change is that most of us are now working from home which has no impact and in fact, it seems conducive to the acceptance of more community developers in the future to come. From the internal working schedule and development timeline, there is no great impact. We do not publish specific timeline as we do not want short term holders (traders) to create too much negative pressure on product development.
Doris Guo Q6: Aelf is an open-source blockchain, and there's the common problem of taking a substantial amount of time for the different participants to agree on strategic decisions. What types of governance models do you use in Aelf to address this issue???
Haobo Ma The issue is about public blockchain network, and who can decide the direction of the network. Our answer is long-term holders. For the short-term holders (traders), we refuse to allow them to participate in any discussion of the direction of Aelf because the short-term holders are likely to make a profit and sell quickly, which is essentially the same example of a person who cheats the President and then runs away for his personal gain. We defined a number of proposal processes, including the logic of the two-party system in the United States, and the participation in the referendum to ensure that the final proposal represents the majority. At the same time, we are looking for some legal solutions to avoid bifurcation, such as prohibiting exchanges from intervening in bifurcated new tokens. While we cannot limit a community, we should be able to find ways to limit a centralized organization. This restriction is akin to a ban on national secession.
Doris Guo Q7: How will Aelf empower Investors, Companies, Developers, Platform Users to deliver impactful solutions and bring value to people all over the world?
Haobo Ma We will learn from the operational experience of successful foundations such as the LINUX foundation and license some commercial companies to use Aelf solutions to solve business problems. At the same time, Aelf is an open-source product under the MIT License, and we accept any use that does not violate this open-source principle.
Zhuling Chen Let me add on to Haobo’s statement: to incentivize and empower the community, we are also exploring ways to let the community decide how to use the funds for Aelf (allocate to where it matters to our community) once mainnet is launched. This means you guys can decide what are the projects to be funded on Aelf, etc
Doris Guo Q8：When will the node campaign start? How will Aelf attract users to participate in nodes election?
Haobo Ma According to our published roadmap, the timeline can be dynamic, but I don't think it will be too long. The main idea is to let everyone understand what we envision Aelf to be like, and what are the rights and benefits of being a node in the future. We hope to find nodes that fully recognize the efforts of Aelf at the present stage and are willing to participate in the future development of Aelf. We will run a simulation of the node campaign on the testnet and set up a temporary mainnet launch committee. Please follow our official Twitter for more upcoming details!
Doris Guo Q9: Token swap form 2 is some kind of cross-chain transfer? It will be handled by a smart contract?
Haobo Ma It is handled by the smart contract, we define an asset cross-chain transfer protocol, but it may be opened after a snapshot.
Doris Guo Q10: Which Exchanges will support token swap? Do you have any plan to list Aelf in some big exchange like Binance, Houbi, Kucoin, .......?
Haobo Ma We are already in talks with some exchanges, there is still competition between exchanges, and many are still hoping to attract more users by getting access to mainnet token swap early.
Doris Guo Q11: Aside conversion of the current tokens to mainnet tokens, what other main features will be accomplished with the mainnet launch?
Haobo Ma We have a documentation file that has been published, which has listed some features: https://Aelf.io/gridcn/Aelf_public_testnet_and_supporting_features_introduction_en_v1.0.pdf
Doris Guo Q12: Do you have any plan to burn or buyback your coin?
Haobo Ma We have plans for the community to govern through DAO, we have no interest in short-term price incentive adjustment as we would prefer to drive the project to higher adoption. After mainnet starts operation, there will be a part of network revenue get destroyed automatically.
Doris Guo Q13: Often, as a newbie developer, I face difficulties on most blockchains. How easy and convenient is it for me on Aelf, and what programming language and tools are needed??
Haobo Ma We set up staging for DAPP developers on GitHub and configured CI. Develop a smart contract using C# with React Native on the front end. So, in fact, developers can fork the source code without setting up the environment locally, and you can conduct unit testing with the help of CI. You can also release the smart contract and generate the installation package of iOS and android online. https://github.com/AElfProject/Aelf-boilerplate
Doris Guo Q14: What is the progress of business development and what are some of your commercial partnerships? How will Aelf rapidly develop the number & performance of DAPP?
Haobo Ma First of all, the blockchain industry is still fairly small and users with ETH and EOS wallets are considered a very small group and its not effective to even promote within these groups. What we need to consider is how to enable users who have never been exposed to blockchain to use DAPP. The competitiveness of Aelf is to make it easier for Aelf developers to promote their DAPP to ordinary users, rather than to teach ordinary users a lot on blockchain knowledge. The average user doesn't like to hear about private keys, mnemonic, Gas Price, RAM, CPU, etc. Only until we solve such problems, companies that need to solve problems through blockchain will be more inclined to use Aelf in technology selection. Therefore, our main work is to explain the competitive advantages of Aelf, ETH and EOS to everyone. We have some business cooperation’s, but we also believe that simply through case-by-case business cooperation will not be able to gain adoption so quickly, therefore we still need to put our products to stay ahead of the next generation.
Doris Guo Q15: What other activities can encourage more people to be confident about Aelf?
Haobo Ma We are only going to state the truth by having those that have faith in us to stay and those that don't to leave. The development of Aelf is not driven by a single foundation, but by a steady stream of contributions from the community. In the future, we will also place the activities in the DAO for on-chain governance, and let the community make decisions by itself.
Kun Aguero As you know that in the present market situation many new coins or either dying or thriving for liquidity? How will you manage this liquidity problem?
Zhuling Chen Aelf started in 2017. we have gone through a few cycles in the market, still, remember the big down period in 2018-2019. Aelf is financially solid and the team has always been working hard. if you are referring to liquidity in exchanges, we are among the lucky ones that are listed in all major exchanges
Xinshu Dong Hello, great discussions! I would like to ask what are the criteria to join the committee for launching the mainnet? Would love to participate
Zhuling Chen Hi xinshu, great to see you here. The committee will be chosen among the nodes elected during the testnet dry run. Which means, it is really important to participate in the testnet dry run and also start to establish your reputation in the community so that people will elect you as a node. The detailed criteria will include what is your plan to help Aelf to grow, tech competency and reputation.
An Da What are Aelf’s achievements in 2019? Who had supported you to get those things?
Zhuling Chen To name a few, in 2019, Aelf is one of the most active projects on GitHub. This means Aelf is evolving and improving fast in this space and our team has the tech strength. In addition, we have also successfully listed on all major cloud service providers, such as AWS, Azure, Google. So large companies can easily launch Aelf side chains in their organization with minimum hassle.
John How does the voting for master nodes candidates occur? And why is the development of this system important for your project?
Zhuling Chen Voting is going to be pretty simple. All token holders can vote for the nodes they support on our block explorer.
Miha After mainnet lunch, how will you assure that transactional fees will stay low? We know what sometimes happens to fees on ETH blockchain.
Zhuling Chen First of all, due to the fact that is Aelf is scalability, this will reduce transaction fee. Secondly, all transaction fees will be voted by the nodes (which will be elected by you). So they will represent your interest
Bobbyfernandito Currently, as we see All projects are concerned with the speed and security. So, tell us here - what are the facilities Aelf provide to their user and investors?
Haobo Ma Security: we have an automated smart contract code audit. During contract deployment, production nodes and the community audit participation are required. On the other hand, we are also planning to provide a standardized model of centralized exchange access for 100% asset certification and emergency measures to deal with exchange attacks, which we will be released later. Speed: Aelf has been working on improving performance, which is transparent to users which they can also experience by themselves.
An Da What effect does Aelf token have on the Aelf ecosystem? Holding Aelf, what benefits will users receive?
Zhuling Chen Holding ELF enables you to use all the services on the Aelf network. ELF has a deflating system where the total amount will reduce as the network grows. token holders can also vote for the nodes to run the network and also vote for big decisions in the network. part of the fees in the system will also be distributed to token holders via a smart contract
ahihi132 Which companies do you view them as potential partners and that they are somewhat also beneficial for both the user base and Aelf itself?
Zhuling Chen Great question, if I could write a wish list, that will be: let medium-sized financial institutions to use Aelf to challenge the big boys. Let telecommunication companies use Aelf for micro-payment and other innovative business models. We also would like to try out a few public sector projects, which blockchain will is still more transparency and trust
Misun Q1: Which programming languages are you using in your project? And why? Q2-What are another big MILESTONES you have planned for 2020 roadmap and how are they supposed to benefit your costumers? Will it be an exciting year?
Haobo Ma For Q1: We mainly use C# for development, I personally like it. Performance is good, development environment IDEs are strong, and C# creators are influential in the industry. We believe in the right thing, though it may take a while to develop. The smart contract will then add support for multiple languages, such as WebAssembly, depending on the needs of the community. Now it seems that C# is enough.
Hambi crypto Which platforms are your competitors? How will you soar above them, and what better things do you offer than them? So, What’s your outlook on the future of cryptocurrencies in this year and next few years?
Haobo Ma As I have already mentioned this before, Eth and Eos. We provide better performance, cross-chain support (already implemented), end-users do not need to know the details of the blockchain, developer’s payment models and so on.
Floris-Jan What plans is Aelf making to prevent centralized exchange to take over the DPoS algorithm like what happened to Steem? Are we talking about blacklisting exchange wallets, or having the foundation say "No", or putting all trust in the community?
Zhuling Chen Great question, Floris. I’m not going to give away all the details of what Haobo has proposed to work on this, but in a nutshell, in Aelf system, exchange wallets will not be allowed to vote, but only the sub-wallets for each individual can vote. This will also help exchanges to prevent hacking and theft in the future
Alex What your plans in place for global expansion, are Aelf wallet focusing on the only market at this time? Or focus on building and developing or getting customers and users, or partnerships? Can you explain this?
Haobo Ma Our core focus will be through the developers to promote, developers will help Aelf to attract more users. So our product has to be attractive to developers. Just like AWS, they only focus on getting their service right, their developers will think about how to promote it. We don't want to burden them in their promotion process.
Ellkay What do you think are the major threats and barriers that could face the development and adoption of Aelf?
Haobo Ma If I'm a DAPP developer and I need to promote my APP to people who don't recognize blockchain, then I'd like to choose a platform that doesn't have to explain a lot of blockchain details to the end-user, so they can use it easily. We've provided some options in the Boilerplate that allow you to log-in simply via QR code + Password, and our recommended Dapp is an independent wallet and a separate iOS/Android application.
ahihi132 Give me some important reasons why we need to hold Aelf token where in fact hundreds of projects failed and it went to bankruptcy or even developers run when they collect millions/billions of funds?
Haobo Ma First of all, we will not give any suggestions as we only describe the fact that the long-term token holder will be able to govern the Aelf network, get Aelf mining reward and Aelf network profit. At the same time, Aelf network is a deflation model, Aelf network received transaction fees, profit dividends will immediately destroy 10% etc. All investments are risky, and we don't judge the behaviour of other developers. There are so many things in this world that cannot be understood and unfair. It is important to do our job well. I cannot explain these things.
胖 见愁 I remember that boss Ma mentioned to only find those truly innovative applications and enterprises with blockchain, how to find and win partners in these aspects?
Haobo Ma When Linus was developing Linux, I did not think he would find a lot of collaboration when the code was not good. The response we can give is that we already have a lot of interest in cooperation, including what we have announced, what we have not announced, etc.
胖 见愁 How interested are cloud computing providers in participating nodes?
Haobo Ma The vast majority of our nodes should be using cloud services, and as long as a large number of our 17 nodes and other candidate nodes are based on cloud services, our network robustness is determined by these cloud computing providers. Of course, in the expansion, we can also use cloud computing services.
So I'm Steve Shadders and at nChain I am the director of solutions in engineering and specifically for Bitcoin SV I am the technical director of the project which means that I'm a bit less hands-on than Daniel but I handle a lot of the liaison with the miners - that's the conditional project.Daniel:
Hi I’m Daniel I’m the lead developer for Bitcoin SV. As the team's grown that means that I do less actual coding myself but more organizing the team and organizing what we’re working on.Connor 03:23.07,0:04:15.98
I mean yes well we’ve been in touch with the developer teams for quite some time - I think a bi-weekly meeting of Bitcoin Cash developers across all implementations started around November last year. I myself joined those in January or February of this year and Daniel a few months later. So we communicate with all of those teams and I think, you know, it's not been without its challenges. It's well known that there's a lot of disagreements around it, but some what I do look forward to in the near future is a day when the consensus issues themselves are all rather settled, and if we get to that point then there's not going to be much reason for the different developer teams to disagree on stuff. They might disagree on non-consensus related stuff but that's not the end of the world because, you know, Bitcoin Unlimited is free to go and implement whatever they want in the back end of a Bitcoin Unlimited and Bitcoin SV is free to do whatever they want in the backend, and if they interoperate on a non-consensus level great. If they don't not such a big problem there will obviously be bridges between the two, so, yeah I think going forward the complications of having so many personalities with wildly different ideas are going to get less and less.Cory: 0:06:00.59,0:06:19.59
Sure yeah so our release will be concentrated on the stability, right, with the first release of Bitcoin SV and that involved doing a large amount of additional testing particularly not so much at the unit test level but at the more system test so setting up test networks, performing tests, and making sure that the software behaved as we expected, right. Confirming the changes we made, making sure that there aren’t any other side effects. Because of, you know, it was quite a rush to release the first version so we've got our test results documented, but not in a way that we can really release them. We're thinking about doing that but we’re not there yet.Steve: 0:07:50.25,0:09:50.87
Just to tidy that up - we've spent a lot of our time developing really robust test processes and the reporting is something that we can read on our internal systems easily, but we need to tidy that up to give it out for public release. The priority for us was making sure that the software was safe to use. We've established a test framework that involves a progression of code changes through multiple test environments - I think it's five different test environments before it gets the QA stamp of approval - and as for the question about the testnet, yeah, we've got four of them. We've got Testnet One and Testnet Two. A slightly different numbering scheme to the testnet three that everyone's probably used to – that’s just how we reference them internally. They're [1 and 2] both forks of Testnet Three. [Testnet] One we used for activation testing, so we would test things before and after activation - that one’s set to reset every couple of days. The other one [Testnet Two] was set to post activation so that we can test all of the consensus changes. The third one was a performance test network which I think most people have probably have heard us refer to before as Gigablock Testnet. I get my tongue tied every time I try to say that word so I've started calling it the Performance test network and I think we're planning on having two of those: one that we can just do our own stuff with and experiment without having to worry about external unknown factors going on and having other people joining it and doing stuff that we don't know about that affects our ability to baseline performance tests, but the other one (which I think might still be a work in progress so Daniel might be able to answer that one) is one of them where basically everyone will be able to join and they can try and mess stuff up as bad as they want.Daniel: 0:09:45.02,0:10:20.93
Yeah, so we so we recently shared the details of Testnet One and Two with the with the other BCH developer groups. The Gigablock test network we've shared up with one group so far but yeah we're building it as Steve pointed out to be publicly accessible.Connor: 0:10:18.88,0:10:44.00
That's what did the Gigablock test network is. So the Gigablock test network was first set up by Bitcoin Unlimited with nChain’s help and they did some great work on that, and we wanted to revive it. So we wanted to bring it back and do some large-scale testing on it. It's a flexible network - at one point we had we had eight different large nodes spread across the globe, sort of mirroring the old one. Right now we scaled back because we're not using it at the moment so they'll notice I think three. We have produced some large blocks there and it's helped us a lot in our research and into the scaling capabilities of Bitcoin SV, so it's guided the work that the team’s been doing for the last month or two on the improvements that we need for scalability.Steve: 0:11:56.48,0:13:34.25
I think that's actually a good point to kind of frame where our priorities have been in kind of two separate stages. I think, as Daniel mentioned before, because of the time constraints we kept the change set for the October 15 release as minimal as possible - it was just the consensus changes. We didn't do any work on performance at all and we put all our focus and energy into establishing the QA process and making sure that that change was safe and that was a good process for us to go through. It highlighted what we were missing in our team – we got our recruiters very busy recruiting of a Test Manager and more QA people. The second stage after that is performance related work which, as Daniel mentioned, the results of our performance testing fed into what tasks we were gonna start working on for the performance related stuff. Now that work is still in progress - some of the items that we identified the code is done and that's going through the QA process but it’s not quite there yet. That's basically the two-stage process that we've been through so far. We have a roadmap that goes further into the future that outlines more stuff, but primarily it’s been QA first, performance second. The performance enhancements are close and on the horizon but some of that work should be ongoing for quite some time.Daniel: 0:13:37.49,0:14:35.14
Some of the changes we need for the performance are really quite large and really get down into the base level view of the software. There's kind of two groups of them mainly. One that are internal to the software – to Bitcoin SV itself - improving the way it works inside. And then there's other ones that interface it with the outside world. One of those in particular we're working closely with another group to make a compatible change - it's not consensus changing or anything like that - but having the same interface on multiple different implementations will be very helpful right, so we're working closely with them to make improvements for scalability.Connor: 0:14:32.60,0:15:26.45
I'm often quoted on Twitter and Reddit - I've said before the infinite block attack is bullshit. Now, that's a statement that I suppose is easy to take out of context, but I think the 128 MB limit is something where there’s probably two schools of thought about. There are some people who think that you shouldn't increase the limit to 128 MB until the software can handle it, and there are others who think that it's fine to do it now so that the limit is increased when the software can handle it and you don’t run into the limit when this when the software improves and can handle it. Obviously we’re from the latter school of thought. As I said before we've got a bunch of performance increases, performance enhancements, in the pipeline. If we wait till May to increase the block size limit to 128 MB then those performance enhancements will go in, but we won't be able to actually demonstrate it on mainnet. As for the infinitive block attack itself, I mean there are a number of mitigations that you can put in place. I mean firstly, you know, going down to a bit of the tech detail - when you send a block message or send any peer to peer message there's a header which has the size of the message. If someone says they're sending you a 30MB message and you're receiving it and it gets to 33MB then obviously you know something's wrong so you can drop the connection. If someone sends you a message that's 129 MB and you know the block size limit is 128 you know it’s kind of pointless to download that message. So I mean these are just some of the mitigations that you can put in place. When I say the attack is bullshit, I mean I mean it is bullshit from the sense that it's really quite trivial to prevent it from happening. I think there is a bit of a school of thought in the Bitcoin world that if it's not in the software right now then it kind of doesn't exist. I disagree with that, because there are small changes that can be made to work around problems like this. One other aspect of the infinite block attack, and let’s not call it the infinite block attack, let's just call it the large block attack - it takes a lot of time to validate that we gotten around by having parallel pipelines for blocks to come in, so you've got a block that's coming in it's got a unknown stuck on it for two hours or whatever downloading and validating it. At some point another block is going to get mined b someone else and as long as those two blocks aren't stuck in a serial pipeline then you know the problem kind of goes away.Cory: 0:18:26.55,0:18:48.27
Yes, there have been concerns raised about it. I think what people forget is that compact blocks and xThin exist, so if a 32MB block is not send 32MB of data in most cases, almost all cases. The concern here that I think I do find legitimate is the Great Firewall of China. Very early on in Bitcoin SV we started talking with miners on the other side of the firewall and that was one of their primary concerns. We had anecdotal reports of people who were having trouble getting a stable connection any faster than 200 kilobits per second and even with compact blocks you still need to get the transactions across the firewall. So we've done a lot of research into that - we tested our own links across the firewall, rather CoinGeeks links across the firewall as they’ve given us access to some of their servers so that we can play around, and we were able to get sustained rates of 50 to 90 megabits per second which pushes that problem quite a long way down the road into the future. I don't know the maths off the top of my head, but the size of the blocks that can sustain is pretty large. So we're looking at a couple of options - it may well be the chattiness of the peer-to-peer protocol causes some of these issues with the Great Firewall, so we have someone building a bridge concept/tool where you basically just have one kind of TX vacuum on either side of the firewall that collects them all up and sends them off every one or two seconds as a single big chunk to eliminate some of that chattiness. The other is we're looking at building a multiplexer that will sit and send stuff up to the peer-to-peer network on one side and send it over splitters, to send it over multiple links, reassemble it on the other side so we can sort of transition the great Firewall without too much trouble, but I mean getting back to the core of your question - yes there is a theoretical limit to block size propagation time and that's kind of where Moore's Law comes in. Putting faster links and you kick that can further down the road and you just keep on putting in faster links. I don't think 128 main blocks are going to be an issue though with the speed of the internet that we have nowadays.Connor: 0:21:34.99,0:22:17.84
It's interesting the decision - we were initially planning on removing that cap altogether and the next cap that comes into play after that (next effective cap is a 10,000 byte limit on the size of the script). We took a more conservative route and decided to wind that back to 500 - it's interesting that we got some criticism for that when the primary criticism I think that was leveled against us was it’s dangerous to increase that limit to unlimited. We did that because we’re being conservative. We did some research into these log n squared bugs, sorry – attacks, that people have referred to. We identified a few of them and we had a hard think about it and thought - look if we can find this many in a short time we can fix them all (the whack-a-mole approach) but it does suggest that there may well be more unknown ones. So we thought about putting, you know, taking the whack-a-mole approach, but that doesn't really give us any certainty. We will fix all of those individually but a more global approach is to make sure that if anyone does discover one of these scripts it doesn't bring the node to a screaming halt, so the problem here is because the Bitcoin node is essentially single-threaded, if you get one of these scripts that locks up the script engine for a long time everything that's behind it in the queue has to stop and wait. So what we wanted to do, and this is something we've got an engineer actively working on right now, is once that script validation goad path is properly paralyzed (parts of it already are), then we’ll basically assign a few threads for well-known transaction templates, and a few threads for any any type of script. So if you get a few scripts that are nasty and lock up a thread for a while that's not going to stop the node from working because you've got these other kind of lanes of the highway that are exclusively reserved for well-known script templates and they'll just keep on passing through. Once you've got that in place, and I think we're in a much better position to get rid of that limit entirely because the worst that's going to happen is your non-standard script pipelines get clogged up but everything else will keep keep ticking along - there are other mitigations for this as well I mean I know you could always put a time limit on script execution if they wanted to, and that would be something that would be up to individual miners. Bitcoin SV's job I think is to provide the tools for the miners and the miners can then choose, you know, how to make use of them - if they want to set time limits on script execution then that's a choice for them.Daniel: 0:25:34.82,0:26:15.85
Yeah, I'd like to point out that a node here, when it receives a transaction through the peer to peer network, it doesn't have to accept that transaction, you can reject it. If it looks suspicious to the node it can just say you know we're not going to deal with that, or if it takes more than five minutes to execute, or more than a minute even, it can just abort and discard that transaction, right. The only time we can’t do that is when it's in a block already, but then it could decide to reject the block as well. It's all possibilities there could be in the software.Steve: 0:26:13.08,0:26:20.64
Yeah, and if it's in a block already it means someone else was able to validate it so…Cory: 0,0:26:21.21,0:26:43.60
Well I mean one of one of the most significant things is other than two, which are minor variants of DUP and MUL, they represent almost the complete set of original op codes. I think that's not necessarily a technical issue, but it's an important milestone. MUL is one that's that I've heard some interesting comments about. People ask me why are you putting OP_MUL back in if you're planning on changing them to big number operations instead of the 32-bit limit that they're currently imposed upon. The simple answer to that question is that we currently have all of the other arithmetic operations except for OP_MUL. We’ve got add divide, subtract, modulo – it’s odd to have a script system that's got all the mathematical primitives except for multiplication. The other answer to that question is that they're useful - we've talked about a Rabin signature solution that basically replicates the function of DATASIGVERIFY. That's just one example of a use case for this - most cryptographic primitive operations require mathematical operations and bit shifts are useful for a whole ton of things. So it's really just about completing that work and completing the script engine, or rather not completing it, but putting it back the way that it was it was meant to be.Connor 0:28:20.42,0:29:22.62
Yeah there's two parts there - the big number one and the L shift being a logical shift instead of arithmetic. so when we re-enabled these opcodes we've looked at them carefully and have adjusted them slightly as we did in the past with OP_SPLIT. So the new LSHIFT and RSHIFT are bitwise operators. They can be used to implement arithmetic based shifts - I think I've posted a short script that did that, but we can't do it the other way around, right. You couldn't use an arithmetic shift operator to implement a bitwise one. It's because of the ordering of the bytes in the arithmetic values, so the values that represent numbers. The little endian which means they're swapped around to what many other systems - what I've considered normal - or big-endian. And if you start shifting that properly as a number then then shifting sequence in the bytes is a bit strange, so it couldn't go the other way around - you couldn't implement bitwise shift with arithmetic, so we chose to make them bitwise operators - that's what we proposed.Steve: 0:31:10.57,0:31:51.51
That was essentially a decision that was actually made in May, or rather a consequence of decisions that were made in May. So in May we reintroduced OP_AND, OP_OR, and OP_XOR, and that was also another decision to replace three different string operators with OP_SPLIT was also made. So that was not a decision that we've made unilaterally, it was a decision that was made collectively with all of the BCH developers - well not all of them were actually in all of the meetings, but they were all invited.Daniel: 0:31:48.24,0:32:23.13
Another example of that is that we originally proposed OP_2DIV and OP_2MUL was it, I think, and this is a single operator that multiplies the value by two, right, but it was pointed out that that can very easily be achieved by just doing multiply by two instead of having a separate operator for it, so we scrapped those, we took them back out, because we wanted to keep the number of operators minimum yeah.Steve: 0:32:17.59,0:33:47.20
There was an appetite around for keeping the operators minimal. I mean the decision about the idea to replace OP_SUBSTR, OP_LEFT, OP_RIGHT with OP_SPLIT operator actually came from Gavin Andresen. He made a brief appearance in the Telegram workgroups while we were working out what to do with May opcodes and obviously Gavin's word kind of carries a lot of weight and we listen to him. But because we had chosen to implement the May opcodes (the bitwise opcodes) and treat the data as big-endian data streams (well, sorry big-endian not really applicable just plain data strings) it would have been completely inconsistent to implement LSHIFT and RSHIFT as integer operators because then you would have had a set of bitwise operators that operated on two different kinds of data, which would have just been nonsensical and very difficult for anyone to work with, so yeah. I mean it's a bit like P2SH - it wasn't a part of the original Satoshi protocol that once some things are done they're done and you know if you want to want to make forward progress you've got to work within that that framework that exists.Daniel: 0:33:45.85,0:34:48.97
When we get to the big number ones then it gets really complicated, you know, number implementations because then you can't change the behavior of the existing opcodes, and I don't mean OP_MUL, I mean the other ones that have been there for a while. You can't suddenly make them big number ones without seriously looking at what scripts there might be out there and the impact of that change on those existing scripts, right. The other the other point is you don't know what scripts are out there because of P2SH - there could be scripts that you don't know the content of and you don't know what effect changing the behavior of these operators would mean. The big number thing is tricky, so another option might be, yeah, I don't know what the options for though it needs some serious thought.Steve: 0:34:43.27,0:35:24.23
That’s something we've reached out to the other implementation teams about - actually really would like their input on the best ways to go about restoring big number operations. It has to be done extremely carefully and I don't know if we'll get there by May next year, or when, but we’re certainly willing to put a lot of resources into it and we're more than happy to work with BU or XT or whoever wants to work with us on getting that done and getting it done safely.Connor: 0:35:19.30,0:35:57.49
I’d actually like to repurpose the concept. I think I mentioned before multi-threaded script validation and having some dedicated well-known script templates - when you say the word well-known script template there’s already a check in Bitcoin that kind of tells you if it's well-known or not and that's IsStandard. I'm generally in favor of getting rid of the notion of standard transactions, but it's actually a decision for miners, and it's really more of a behavioral change than it is a technical change. There's a whole bunch of configuration options that miners can set that affect what they do what they consider to be standard and not standard, but the reality is not too many miners are using those configuration options. So I mean standard transactions as a concept is meaningful to an arbitrary degree I suppose, but yeah I would like to make it easier for people to get non-standard scripts into Bitcoin so that they can experiment, and from discussions of I’ve had with CoinGeek they’re quite keen on making their miners accept, you know, at least initially a wider variety of transactions eventually.Daniel: 0:37:32.85,0:38:07.95
So I think IsStandard will remain important within the implementation itself for efficiency purposes, right - you want to streamline base use case of cash payments through them and prioritizing. That's where it will remain important but on the interfaces from the node to the rest of the network, yeah I could easily see it being removed.Cory: 0,0:38:06.24,0:38:35.46
Well in November there's going to be a divergence of consensus rules regardless of whether we implement these new op codes or not. Bitcoin ABC released their spec for the November Hard fork change I think on August 16th or 17th something like that and their client as well and it included CTOR and it included DSV. Now for the miners that commissioned the SV project, CTOR and DSV are controversial changes and once they're in they're in. They can't be reversed - I mean CTOR maybe you could reverse it at a later date, but DSV once someone's put a P2SH transaction into the project or even a non P2SH transaction in the blockchain using that opcode it's irreversible. So it's interesting that some people refer to the Bitcoin SV project as causing a split - we're not proposing to do anything that anyone disagrees with - there might be some contention about changing the opcode limit but what we're doing, I mean Bitcoin ABC already published their spec for May and it is our spec for the new opcodes, so in terms of urgency - should we wait? Well the fact is that we can't - come November you know it's bit like Segwit - once Segwit was in, yes you arguably could get it out by spending everyone's anyone can spend transactions but in reality it's never going to be that easy and it's going to cause a lot of economic disruption, so yeah that's it. We're putting out changes in because it's not gonna make a difference either way in terms of whether there's going to be a divergence of consensus rules - there's going to be a divergence whether whatever our changes are. Our changes are not controversial at all.Daniel: 0:40:39.79,0:41:03.08
If we didn't include these changes in the November upgrade we'd be pushing ahead with a no-change, right, but the November upgrade is there so we should use it while we can. Adding these non-controversial changes to it.Connor: 0:41:01.55,0:41:35.61
Can I say one or two things about this – there’s different ways to look at that, right. I'm an engineer - my specialization is software, so the economics of it I hear different opinions. I trust some more than others but I am NOT an economist. I kind of agree with the ones with my limited expertise on that it's a subsidy it looks very much like it to me, but yeah that's not my area. What I can talk about is the software - so adding DSV adds really quite a lot of complexity to the code right, and it's a big change to add that. And what are we going to do - every time someone comes up with an idea we’re going to add a new opcode? How many opcodes are we going to add? I saw reports that Jihan was talking about hundreds of opcodes or something like that and it's like how big is this client going to become - how big is this node - is it going to have to handle every kind of weird opcode that that's out there? The software is just going to get unmanageable and DSV - that was my main consideration at the beginning was the, you know, if you can implement it in script you should do it, because that way it keeps the node software simple, it keeps it stable, and you know it's easier to test that it works properly and correctly. It's almost like adding (?) code from a microprocessor you know why would you do that if you can if you can implement it already in the script that is there.Steve: 0:43:36.16,0:46:09.71
It’s actually an interesting inconsistency because when we were talking about adding the opcodes in May, the philosophy that seemed to drive the decisions that we were able to form a consensus around was to simplify and keep the opcodes as minimal as possible (ie where you could replicate a function by using a couple of primitive opcodes in combination, that was preferable to adding a new opcode that replaced) OP_SUBSTR is an interesting example - it's a combination of SPLIT, and SWAP and DROP opcodes to achieve it. So at really primitive script level we've got this philosophy of let's keep it minimal and at this sort of (?) philosophy it’s all let's just add a new opcode for every primitive function and Daniel's right - it's a question of opening the floodgates. Where does it end? If we're just going to go down this road, it almost opens up the argument why have a scripting language at all? Why not just add a hard code all of these functions in one at a time? You know, pay to public key hash is a well-known construct (?) and not bother executing a script at all but once we've done that we take away with all of the flexibility for people to innovate, so it's a philosophical difference, I think, but I think it's one where the position of keeping it simple does make sense. All of the primitives are there to do what people need to do. The things that people don't feel like they can't do are because of the limits that exist. If we had no opcode limit at all, if you could make a gigabyte transaction so a gigabyte script, then you can do any kind of crypto that you wanted even with 32-bit integer operations, Once you get rid of the 32-bit limit of course, a lot of those a lot of those scripts come up a lot smaller, so a Rabin signature script shrinks from 100MB to a couple hundred bytes.Daniel: 0:46:06.77,0:47:36.65
I lost a good six months of my life diving into script, right. Once you start getting into the language and what it can do, it is really pretty impressive how much you can achieve within script. Bitcoin was designed, was released originally, with script. I mean it didn't have to be – it could just be instead of having a transaction with script you could have accounts and you could say trust, you know, so many BTC from this public key to this one - but that's not the way it was done. It was done using script, and script provides so many capabilities if you start exploring it properly. If you start really digging into what it can do, yeah, it's really amazing what you can do with script. I'm really looking forward to seeing some some very interesting applications from that. I mean it was Awemany his zero-conf script was really interesting, right. I mean it relies on DSV which is a problem (and some other things that I don't like about it), but him diving in and using script to solve this problem was really cool, it was really good to see that.Steve: 0:47:32.78,0:48:16.44
I asked a question to a couple of people in our research team that have been working on the Rabin signature stuff this morning actually and I wasn't sure where they are up to with this, but they're actually working on a proof of concept (which I believe is pretty close to done) which is a Rabin signature script - it will use smaller signatures so that it can fit within the current limits, but it will be, you know, effectively the same algorithm (as DSV) so I can't give you an exact date on when that will happen, but it looks like we'll have a Rabin signature in the blockchain soon (a mini-Rabin signature).Cory: 0:48:13.61,0:48:57.63
I think you've got a factor in what I said before about the philosophical differences. I think new functionality can be introduced just fine. Having said that - yes there is a place for new opcodes but it's probably a limited place and in my opinion the cryptographic primitive functions for example CHECKSIG uses ECDSA with a specific elliptic curve, hash 256 uses SHA256 - at some point in the future those are going to no longer be as secure as we would like them to be and we'll replace them with different hash functions, verification functions, at some point, but I think that's a long way down the track.Daniel: 0:49:42.47,0:50:30.3
I'd like to see more data too. I'd like to see evidence that these things are needed, and the way I could imagine that happening is that, you know, that with the full scripting language some solution is implemented and we discover that this is really useful, and over a period of, like, you know measured in years not days, we find a lot of transactions are using this feature, then maybe, you know, maybe we should look at introducing an opcode to optimize it, but optimizing before we even know if it's going to be useful, yeah, that's the wrong approach.Steve: 0:50:28.19,0:51:45.29
I think that optimization is actually going to become an economic decision for the miners. From the miner’s point of view is if it'll make more sense for them to be able to optimize a particular process - does it reduce costs for them such that they can offer a better service to everyone else? Yeah, so ultimately these decisions are going to be miner’s main decisions, not developer decisions. Developers of course can offer their input - I wouldn't expect every miner to be an expert on script, but as we're already seeing miners are actually starting to employ their own developers. I’m not just talking about us - there are other miners in China that I know have got some really bright people on their staff that question and challenge all of the changes - study them and produce their own reports. We've been lucky with actually being able to talk to some of those people and have some really fascinating technical discussions with them.
" And by the way, I think we can successfully make Zcash too traceable for criminals like WannaCry, but still completely private & fungible. …"Ethereum's track record of immutability is also poor. Ethereum was supposed to be an immutable blockchain ledger, however after the DAO hack this proved to not be the case. A 2016 article on Saintly Law summarised the problematic nature of Ethereum's leadership and blockchain intervention:
" Many ethereum and blockchain advocates believe that the intervention was the wrong move to make in this situation. Smart contracts are meant to be self-executing, immutable and free from disturbance by organisations and intermediaries. Yet the building block of all smart contracts, the code, is inherently imperfect. This means that the technology is vulnerable to the same malicious hackers that are targeting businesses and governments. It is also clear that the large scale intervention after the DAO hack could not and would not likely be taken in smaller transactions, as they greatly undermine the viability of the cryptocurrency and the technology."Monero provides Fungibility and Privacy in a Cashless World
"Imagine you sell cupcakes and receive Bitcoin as payment. It turns out that someone who owned that Bitcoin before you was involved in criminal activity. Now you are worried that you have become a suspect in a criminal case, because the movement of funds to you is a matter of public record. You are also worried that certain Bitcoins that you thought you owned will be considered ‘tainted’ and that others will refuse to accept them as payment."This lack of fungibility means that certain businesses will be obligated to avoid accepting BTC that have been previously used for purposes which are illegal, or simply run afoul of their Terms of Service. Currently some large Bitcoin companies are blocking, suspending, or closing accounts that have received Bitcoin used in online gambling or other purposes deemed unsavory by said companies. Monero has been built specifically to address the problem of traceability and non-fungibility inherent in other cryptocurrencies. By having completely private transactions Monero is truly fungible and there can be no blacklisting of certain XMR, while at the same time providing all the benefits of a secure, decentralized, permanent blockchain.
"A lack of fungibility means that when sending or receiving funds, if the other person personally knows you during a transaction, or can get any sort of information on you, or if you provide a residential address for shipping etc. – you could quite potentially have them use this against you for personal gain"For those that wish to seek more information about why Monero is a superior form of money, read The Merits of Monero: Why Monero Vs Bitcoin over on the Monero.how website.
All private transactions, More tested privacy tech, No tax on miners to pay investors, No high inflation... better investment.John McAfee, arguably cryptocurrency's most controversial character at the moment, has publicly supported Monero numerous times over the last twelve months(before he started shilling ICOs), and has even claimed it will overtake Bitcoin.
"Monero is a really good one. Monero is an incredible currency, it's completely private."There is a common belief that most of the money in cryptocurrency is still chasing the quick pump and dumps, however as the market matures, more money will flow into legitimate projects such as Monero. Monero's organic growth in price is evidence smart money is aware of Monero and gradually filtering in.
"In Bitcoin, the main chain is constrained and fees are ludicrous. This results in users being pushed to second layer stuff (e.g. sidechains, lightning network). Users do not have optionality in Bitcoin. In Monero, the goal is to make the main-chain accessible to everyone by keeping fees reasonable. We want users to have optionality, i.e., let them choose whether they'd like to use the main chain or second layer stuff. We don't want to take that optionality away from them."When the Spagni CNBC video was recently linked to the Monero subreddit, it was met with lengthy debate and discussion from both users and developers. u/ferretinjapan summarised the issue explaining:
"Monero has all the mechanisms it needs to find the balance between transaction load, and offsetting the costs of miner infrastructure/profits, while making sure the network is useful for users. But like the interviewer said, the question is directed at "right now", and Fluffys right to a certain extent, Monero's transactions are huge, and compromises in blockchain security will help facilitate less burdensome transactional activity in the future. But to compare Monero to Bitcoin's transaction sizes is somewhat silly as Bitcoin is nowhere near as useful as monero, and utility will facilitate infrastructure building that may eventually utterly dwarf Bitcoin. And to equate scaling based on a node being run on a desktop being the only option for what classifies as "scalable" is also an incredibly narrow interpretation of the network being able to scale, or not. Given the extremely narrow definition of scaling people love to (incorrectly) use, I consider that a pretty crap question to put to Fluffy in the first place, but... ¯_(ツ)_/¯"u/xmrusher also contributed to the discussion, comparing Bitcoin to Monero using this analogous description:
"While John is much heavier than Henry, he's still able to run faster, because, unlike Henry, he didn't chop off his own legs just so the local wheelchair manufacturer can make money. While Morono has much larger transactions then Bitcoin, it still scales better, because, unlike Bitcoin, it hasn't limited itself to a cripplingly tiny blocksize just to allow Blockstream to make money."Setting up a wallet can still be time consuming
r/btc: /r/btc was created to foster and support free and open Bitcoin discussion, Bitcoin news, and exclusive AMA (Ask Me Anything) interviews from … Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcuts. r/btc. log in sign up. User account menu. 82. BitcoinABC blockexplorer (currently on testnet) Close. 82. Posted by. u/HostFat. 2 years ago. Archived ... The official block explorer is back up and running:. It emphasizes the importance of the network at this stage towards the ETH2 launch. As of January the size of the data on disk was 14GB, containing data for about 6 years worth of testnet activity. Blockchain size: Bitcoin is the currency of the Internet. Ethereum: Driven by Different Purposes. This leaves the private key open to attack and ... Help build the user-owned internet by testing the latest builds for Stacks nodes, Stacks mining, Clarity smart contracts, and more. How Blockstack works. Developers. Documentation GitHub Papers Discord. Testnet. Discover apps. Developers. Documentation. GitHub. Testnet. Discord. Run a node. Discover apps. Stacks 2.0 Testnet. Help build the user owned internet by testing the latest builds for ... The most popular and trusted block explorer and crypto transaction search engine. The most popular and trusted block explorer and crypto transaction search engine.
[index]          
This is the tenth open call coordinating the creation of quality open source EVM block explorers, Click "SHOW MORE" to find SOOOOO MANY LINKS: This call cove... - show you an Ethereum testnet block explorer - what a Bitcoin testnet address looks like - what a faucet is In this video series different topics will be explained which will help you to ... We are building technology for both today and tomorrow - a collective super-intelligence on top of decentralized economic internet built with a highly scalable next-generation distributed ledger ... Open Source Live and Testnet Block Explorer https://mousexplore.com GitHub Repository: https://github.com/norestlabs/mousexplore Working on a blockchain pr... Ravencoin Testnet Faucet and Block Explorer https://testnet.ravencoin.network/ Nothing on this channel is financial advice. My Mining Rig Parts Motherboard: https://amzn.to/2rwd5pf Processor ...