[gentoo-x86] Contents of /net-p2p/bitcoin-qt/bitcoin-qt-0 ...
[gentoo-x86] Contents of /net-p2p/bitcoin-qt/bitcoin-qt-0 ...
guix: Enable building for `x86_64-w64-mingw32` target by ...
Download - Bitcoin - Bitcoin Core :: Bitcoin
Run Your Own Node for Bitcoin Testnet (For Blockchain ...
How to Install Bitcoin Core - Beginners Guide - Blockgeeks
Dragonchain Great Reddit Scaling Bake-Off Public Proposal
Dragonchain Public Proposal TL;DR:
Dragonchain has demonstrated twice Reddit’s entire total daily volume (votes, comments, and postsper Reddit 2019 Year in Review) in a 24-hour demo on an operational network. Every single transaction on Dragonchain is decentralized immediately through 5 levels of Dragon Net, and then secured with combined proof on Bitcoin, Ethereum, Ethereum Classic, and Binance Chain, via Interchain. At the time, in January 2020, the entire cost of the demo was approximately $25K on a single system (transaction fees locked at $0.0001/txn). With current fees (lowest fee $0.0000025/txn), this would cost as little as $625. Watch Joe walk through the entire proposal and answer questions onYouTube. This proposal is also available on the Dragonchain blog.
Hello Reddit and Ethereum community!
I’m Joe Roets, Founder & CEO of Dragonchain. When the team and I first heard about The Great Reddit Scaling Bake-Off we were intrigued. We believe we have the solutions Reddit seeks for its community points system and we have them at scale. For your consideration, we have submitted our proposal below. The team at Dragonchain and I welcome and look forward to your technical questions, philosophical feedback, and fair criticism, to build a scaling solution for Reddit that will empower its users. Because our architecture is unlike other blockchain platforms out there today, we expect to receive many questions while people try to grasp our project. I will answer all questions here in this thread on Reddit, and I've answered some questions in the stream on YouTube. We have seen good discussions so far in the competition. We hope that Reddit’s scaling solution will emerge from The Great Reddit Scaling Bake-Off and that Reddit will have great success with the implementation.
Dragonchain is a robust open source hybrid blockchain platform that has proven to withstand the passing of time since our inception in 2014. We have continued to evolve to harness the scalability of private nodes, yet take full advantage of the security of public decentralized networks, like Ethereum. We have a live, operational, and fully functional Interchain network integrating Bitcoin, Ethereum, Ethereum Classic, and ~700 independent Dragonchain nodes. Every transaction is secured to Ethereum, Bitcoin, and Ethereum Classic. Transactions are immediately usable on chain, and the first decentralization is seen within 20 seconds on Dragon Net. Security increases further to public networks ETH, BTC, and ETC within 10 minutes to 2 hours. Smart contracts can be written in any executable language, offering full freedom to existing developers. We invite any developer to watch the demo, play with our SDK’s, review open source code, and to help us move forward. Dragonchain specializes in scalable loyalty & rewards solutions and has built a decentralized social network on chain, with very affordable transaction costs. This experience can be combined with the insights Reddit and the Ethereum community have gained in the past couple of months to roll out the solution at a rapid pace.
Response and PoC
In The Great Reddit Scaling Bake-Off post, Reddit has asked for a series of demonstrations, requirements, and other considerations. In this section, we will attempt to answer all of these requests.
A live proof of concept showing hundreds of thousands of transactions
On Jan 7, 2020, Dragonchain hosted a 24-hour live demonstration during which a quarter of a billion (250 million+) transactions executed fully on an operational network. Every single transaction on Dragonchain is decentralized immediately through 5 levels of Dragon Net, and then secured with combined proof on Bitcoin, Ethereum, Ethereum Classic, and Binance Chain, via Interchain. This means that every single transaction is secured by, and traceable to these networks. An attack on this system would require a simultaneous attack on all of the Interchained networks. 24 hours in 4 minutes (YouTube): 24 hours in 4 minutes The demonstration was of a single business system, and any user is able to scale this further, by running multiple systems simultaneously. Our goals for the event were to demonstrate a consistent capacity greater than that of Visa over an extended time period. Tooling to reproduce our demo is available here: https://github.com/dragonchain/spirit-bomb
Source code (for on & off-chain components as well tooling used for the PoC). The source code does not have to be shared publicly, but if Reddit decides to use a particular solution it will need to be shared with Reddit at some point.
Dragonchain’s architecture attacks the scalability issue from multiple angles. Dragonchain is a hybrid blockchain platform, wherein every transaction is protected on a business node to the requirements of that business or purpose. A business node may be held completely private or may be exposed or replicated to any level of exposure desired. Every node has its own blockchain and is independently scalable. Dragonchain established Context Based Verification as its consensus model. Every transaction is immediately usable on a trust basis, and in time is provable to an increasing level of decentralized consensus. A transaction will have a level of decentralization to independently owned and deployed Dragonchain nodes (~700 nodes) within seconds, and full decentralization to BTC and ETH within minutes or hours. Level 5 nodes (Interchain nodes) function to secure all transactions to public or otherwise external chains such as Bitcoin and Ethereum. These nodes scale the system by aggregating multiple blocks into a single Interchain transaction on a cadence. This timing is configurable based upon average fees for each respective chain. For detailed information about Dragonchain’s architecture, and Context Based Verification, please refer to the Dragonchain Architecture Document.
An interesting feature of Dragonchain’s network consensus is its economics and scarcity model. Since Dragon Net nodes (L2-L4) are independent staking nodes, deployment to cloud platforms would allow any of these nodes to scale to take on a large percentage of the verification work. This is great for scalability, but not good for the economy, because there is no scarcity, and pricing would develop a downward spiral and result in fewer verification nodes. For this reason, Dragonchain uses TIME as scarcity. TIME is calculated as the number of Dragons held, multiplied by the number of days held. TIME influences the user’s access to features within the Dragonchain ecosystem. It takes into account both the Dragon balance and length of time each Dragon is held. TIME is staked by users against every verification node and dictates how much of the transaction fees are awarded to each participating node for every block. TIME also dictates the transaction fee itself for the business node. TIME is staked against a business node to set a deterministic transaction fee level (see transaction fee table below in Cost section). This is very interesting in a discussion about scaling because it guarantees independence for business implementation. No matter how much traffic appears on the entire network, a business is guaranteed to not see an increased transaction fee rate.
Dragonchain uses Docker and Kubernetes to allow the use of best practices traditional system scaling. Dragonchain offers managed nodes with an easy to use web based console interface. The user may also deploy a Dragonchain node within their own datacenter or favorite cloud platform. Users have deployed Dragonchain nodes on-prem on Amazon AWS, Google Cloud, MS Azure, and other hosting platforms around the world. Any executable code, anything you can write, can be written into a smart contract. This flexibility is what allows us to say that developers with no blockchain experience can use any code language to access the benefits of blockchain. Customers have used NodeJS, Python, Java, and even BASH shell script to write smart contracts on Dragonchain. With Docker containers, we achieve better separation of concerns, faster deployment, higher reliability, and lower response times. We chose Kubernetes for its self-healing features, ability to run multiple services on one server, and its large and thriving development community. It is resilient, scalable, and automated. OpenFaaS allows us to package smart contracts as Docker images for easy deployment. Contract deployment time is now bounded only by the size of the Docker image being deployed but remains fast even for reasonably large images. We also take advantage of Docker’s flexibility and its ability to support any language that can run on x86 architecture. Any image, public or private, can be run as a smart contract using Dragonchain.
Flexibility in Scaling
Dragonchain’s architecture considers interoperability and integration as key features. From inception, we had a goal to increase adoption via integration with real business use cases and traditional systems. We envision the ability for Reddit, in the future, to be able to integrate alternate content storage platforms or other financial services along with the token.
LBRY - To allow users to deploy content natively to LBRY
MakerDAO to allow users to lend small amounts backed by their Reddit community points.
STORJ/SIA to allow decentralized on chain storage of portions of content. These integrations or any other are relatively easy to integrate on Dragonchain with an Interchain implementation.
Cost estimates (on-chain and off-chain) For the purpose of this proposal, we assume that all transactions are on chain (posts, replies, and votes).
On the Dragonchain network, transaction costs are deterministic/predictable. By staking TIME on the business node (as described above) Reddit can reduce transaction costs to as low as $0.0000025 per transaction. Dragonchain Fees Table
How to run it
Building on Dragonchain is simple and requires no blockchain experience. Spin up a business node (L1) in our managed environment (AWS), run it in your own cloud environment, or on-prem in your own datacenter. Clear documentation will walk you through the steps of spinning up your first Dragonchain Level 1 Business node. Getting started is easy...
Download Dragonchain’s dctl
Input three commands into a terminal
Build an image
More information can be found in our Get started documents.
Dragonchain is an open source hybrid platform. Through Dragon Net, each chain combines the power of a public blockchain (like Ethereum) with the privacy of a private blockchain. Dragonchain organizes its network into five separate levels. A Level 1, or business node, is a totally private blockchain only accessible through the use of public/private keypairs. All business logic, including smart contracts, can be executed on this node directly and added to the chain. After creating a block, the Level 1 business node broadcasts a version stripped of sensitive private data to Dragon Net. Three Level 2 Validating nodes validate the transaction based on guidelines determined from the business. A Level 3 Diversity node checks that the level 2 nodes are from a diverse array of locations. A Level 4 Notary node, hosted by a KYC partner, then signs the validation record received from the Level 3 node. The transaction hash is ledgered to the Level 5 public chain to take advantage of the hash power of massive public networks. Dragon Net can be thought of as a “blockchain of blockchains”, where every level is a complete private blockchain. Because an L1 can send to multiple nodes on a single level, proof of existence is distributed among many places in the network. Eventually, proof of existence reaches level 5 and is published on a public network.
Dragonchain is open source and even though the platform is easy enough for developers to code in any language they are comfortable with, we do not have so large a developer community as Ethereum. We would like to see the Ethereum developer community (and any other communities) become familiar with our SDK’s, our solutions, and our platform, to unlock the full potential of our Ethereum Interchain. Long ago we decided to prioritize both Bitcoin and Ethereum Interchains. We envision an ecosystem that encompasses different projects to give developers the ability to take full advantage of all the opportunities blockchain offers to create decentralized solutions not only for Reddit but for all of our current platforms and systems. We believe that together we will take the adoption of blockchain further. We currently have additional Interchain with Ethereum Classic. We look forward to Interchain with other blockchains in the future. We invite all blockchains projects who believe in decentralization and security to Interchain with Dragonchain.
While we only have 700 nodes compared to 8,000 Ethereum and 10,000 Bitcoin nodes. We harness those 18,000 nodes to scale to extremely high levels of security. See Dragonchain metrics.
Some may consider the centralization of Dragonchain’s business nodes as an issue at first glance, however, the model is by design to protect business data. We do not consider this a drawback as these nodes can make any, none, or all data public. Depending upon the implementation, every subreddit could have control of its own business node, for potential business and enterprise offerings, bringing new alternative revenue streams to Reddit.
Costs and resources
Summary of cost & resource information for both on-chain & off-chain components used in the PoC, as well as cost & resource estimates for further scaling. If your PoC is not on mainnet, make note of any mainnet caveats (such as congestion issues).
Every transaction on the PoC system had a transaction fee of $0.0001 (one-hundredth of a cent USD). At 256MM transactions, the demo cost $25,600. With current operational fees, the same demonstration would cost $640 USD. For the demonstration, to achieve throughput to mimic a worldwide payments network, we modeled several clients in AWS and 4-5 business nodes to handle the traffic. The business nodes were tuned to handle higher throughput by adjusting memory and machine footprint on AWS. This flexibility is valuable to implementing a system such as envisioned by Reddit. Given that Reddit’s daily traffic (posts, replies, and votes) is less than half that of our demo, we would expect that the entire Reddit system could be handled on 2-5 business nodes using right-sized containers on AWS or similar environments. Verification was accomplished on the operational Dragon Net network with over 700 independently owned verification nodes running around the world at no cost to the business other than paid transaction fees.
This PoC should scale to the numbers below with minimal costs (both on & off-chain). There should also be a clear path to supporting hundreds of millions of users. Over a 5 day period, your scaling PoC should be able to handle: *100,000 point claims (minting & distributing points) *25,000 subscriptions *75,000 one-off points burning *100,000 transfers
During Dragonchain’s 24 hour demo, the above required numbers were reached within the first few minutes. Reddit’s total activity is 9000% more than Ethereum’s total transaction level. Even if you do not include votes, it is still 700% more than Ethereum’s current volume. Dragonchain has demonstrated that it can handle 250 million transactions a day, and it’s architecture allows for multiple systems to work at that level simultaneously. In our PoC, we demonstrate double the full capacity of Reddit, and every transaction was proven all the way to Bitcoin and Ethereum. Reddit Scaling on Ethereum
Solutions should not depend on any single third-party provider. We prefer solutions that do not depend on specific entities such as Reddit or another provider, and solutions with no single point of control or failure in off-chain components but recognize there are numerous trade-offs to consider
Dragonchain’s architecture calls for a hybrid approach. Private business nodes hold the sensitive data while the validation and verification of transactions for the business are decentralized within seconds and secured to public blockchains within 10 minutes to 2 hours. Nodes could potentially be controlled by owners of individual subreddits for more organic decentralization.
Billing is currently centralized - there is a path to federation and decentralization of a scaled billing solution.
Operational on-premises capabilities
Operational deployment to any datacenter
Over 700 independent Community Verification Nodes with proof of ownership
Operational Interchain (Interoperable to Bitcoin, Ethereum, and Ethereum Classic, open to more)
Usability Scaling solutions should have a simple end user experience.
Users shouldn't have to maintain any extra state/proofs, regularly monitor activity, keep track of extra keys, or sign anything other than their normal transactions
Dragonchain and its customers have demonstrated extraordinary usability as a feature in many applications, where users do not need to know that the system is backed by a live blockchain. Lyceum is one of these examples, where the progress of academy courses is being tracked, and successful completion of courses is rewarded with certificates on chain. Our @Save_The_Tweet bot is popular on Twitter. When used with one of the following hashtags - #please, #blockchain, #ThankYou, or #eternalize the tweet is saved through Eternal to multiple blockchains. A proof report is available for future reference. Other examples in use are DEN, our decentralized social media platform, and our console, where users can track their node rewards, view their TIME, and operate a business node. Examples:
Transactions complete in a reasonable amount of time (seconds or minutes, not hours or days)
All transactions are immediately usable on chain by the system. A transaction begins the path to decentralization at the conclusion of a 5-second block when it gets distributed across 5 separate community run nodes. Full decentralization occurs within 10 minutes to 2 hours depending on which interchain (Bitcoin, Ethereum, or Ethereum Classic) the transaction hits first. Within approximately 2 hours, the combined hash power of all interchained blockchains secures the transaction.
Free to use for end users (no gas fees, or fixed/minimal fees that Reddit can pay on their behalf)
With transaction pricing as low as $0.0000025 per transaction, it may be considered reasonable for Reddit to cover transaction fees for users. All of Reddit's Transactions on Blockchain (month) Community points can be earned by users and distributed directly to their Reddit account in batch (as per Reddit minting plan), and allow users to withdraw rewards to their Ethereum wallet whenever they wish. Withdrawal fees can be paid by either user or Reddit. This model has been operating inside the Dragonchain system since 2018, and many security and financial compliance features can be optionally added. We feel that this capability greatly enhances user experience because it is seamless to a regular user without cryptocurrency experience, yet flexible to a tech savvy user. With regard to currency or token transactions, these would occur on the Reddit network, verified to BTC and ETH. These transactions would incur the $0.0000025 transaction fee. To estimate this fee we use the monthly active Reddit users statista with a 60% adoption rate and an estimated 10 transactions per month average resulting in an approximate $720 cost across the system. Reddit could feasibly incur all associated internal network charges (mining/minting, transfer, burn) as these are very low and controllable fees. Reddit Internal Token Transaction Fees Reddit Ethereum Token Transaction Fees When we consider further the Ethereum fees that might be incurred, we have a few choices for a solution.
Offload all Ethereum transaction fees (user withdrawals) to interested users as they wish to withdraw tokens for external use or sale.
Cover Ethereum transaction fees by aggregating them on a timed schedule. Users would request withdrawal (from Reddit or individual subreddits), and they would be transacted on the Ethereum network every hour (or some other schedule).
In a combination of the above, customers could cover aggregated fees.
Integrate with alternate Ethereum roll up solutions or other proposals to aggregate minting and distribution transactions onto Ethereum.
Users should be able to view their balances & transactions via a blockchain explorer-style interface
From interfaces for users who have no knowledge of blockchain technology to users who are well versed in blockchain terms such as those present in a typical block explorer, a system powered by Dragonchain has flexibility on how to provide balances and transaction data to users. Transactions can be made viewable in an Eternal Proof Report, which displays raw data along with TIME staking information and traceability all the way to Bitcoin, Ethereum, and every other Interchained network. The report shows fields such as transaction ID, timestamp, block ID, multiple verifications, and Interchain proof. See example here. Node payouts within the Dragonchain console are listed in chronological order and can be further seen in either Dragons or USD. See example here. In our social media platform, Dragon Den, users can see, in real-time, their NRG and MTR balances. See example here. A new influencer app powered by Dragonchain, Raiinmaker, breaks down data into a user friendly interface that shows coin portfolio, redeemed rewards, and social scores per campaign. See example here.
Exiting is fast & simple
Withdrawing funds on Dragonchain’s console requires three clicks, however, withdrawal scenarios with more enhanced security features per Reddit’s discretion are obtainable.
Interoperability Compatibility with third party apps (wallets/contracts/etc) is necessary.
Proven interoperability at scale that surpasses the required specifications. Our entire platform consists of interoperable blockchains connected to each other and traditional systems. APIs are well documented. Third party permissions are possible with a simple smart contract without the end user being aware. No need to learn any specialized proprietary language. Any code base (not subsets) is usable within a Docker container. Interoperable with any blockchain or traditional APIs. We’ve witnessed relatively complex systems built by engineers with no blockchain or cryptocurrency experience. We’ve also demonstrated the creation of smart contracts within minutes built with BASH shell and Node.js. Please see our source code and API documentation.
Scaling solutions should be extensible and allow third parties to build on top of it Open source and extensible APIs should be well documented and stable
Third-party permissionless integrations should be possible & straightforward Smart contracts are Docker based, can be written in any language, use full language (not subsets), and can therefore be integrated with any system including traditional system APIs. Simple is better. Learning an uncommon or proprietary language should not be necessary.
Advanced knowledge of mathematics, cryptography, or L2 scaling should not be required. Compatibility with common utilities & toolchains is expected. Dragonchain business nodes and smart contracts leverage Docker to allow the use of literally any language or executable code. No proprietary language is necessary. We’ve witnessed relatively complex systems built by engineers with no blockchain or cryptocurrency experience. We’ve also demonstrated the creation of smart contracts within minutes built with BASH shell and Node.js.
Bonus Points: Show us how it works. Do you have an idea for a cool new use case for Community Points? Build it!
Community points could be awarded to Reddit users based upon TIME too, whereas the longer someone is part of a subreddit, the more community points someone naturally gained, even if not actively commenting or sharing new posts. A daily login could be required for these community points to be credited. This grants awards to readers too and incentivizes readers to create an account on Reddit if they browse the website often. This concept could also be leveraged to provide some level of reputation based upon duration and consistency of contribution to a community subreddit.
Dragonchain has already built a social media platform that harnesses community involvement. Dragon Den is a decentralized community built on the Dragonchain blockchain platform. Dragon Den is Dragonchain’s answer to fake news, trolling, and censorship. It incentivizes the creation and evaluation of quality content within communities. It could be described as being a shareholder of a subreddit or Reddit in its entirety. The more your subreddit is thriving, the more rewarding it will be. Den is currently in a public beta and in active development, though the real token economy is not live yet. There are different tokens for various purposes. Two tokens are Lair Ownership Rights (LOR) and Lair Ownership Tokens (LOT). LOT is a non-fungible token for ownership of a specific Lair. LOT will only be created and converted from LOR. Energy (NRG) and Matter (MTR) work jointly. Your MTR determines how much NRG you receive in a 24-hour period. Providing quality content, or evaluating content will earn MTR.
Security. Users have full ownership & control of their points.
All community points awarded based upon any type of activity or gift, are secured and provable to all Interchain networks (currently BTC, ETH, ETC). Users are free to spend and withdraw their points as they please, depending on the features Reddit wants to bring into production.
Balances and transactions cannot be forged, manipulated, or blocked by Reddit or anyone else
Users can withdraw their balance to their ERC20 wallet, directly through Reddit. Reddit can cover the fees on their behalf, or the user covers this with a portion of their balance.
Users should own their points and be able to get on-chain ERC20 tokens without permission from anyone else
Through our console users can withdraw their ERC20 rewards. This can be achieved on Reddit too. Here is a walkthrough of our console, though this does not show the quick withdrawal functionality, a user can withdraw at any time. https://www.youtube.com/watch?v=aNlTMxnfVHw
Points should be recoverable to on-chain ERC20 tokens even if all third-parties involved go offline
If necessary, signed transactions from the Reddit system (e.g. Reddit + Subreddit) can be sent to the Ethereum smart contract for minting.
A public, third-party review attesting to the soundness of the design should be available
To our knowledge, at least two large corporations, including a top 3 accounting firm, have conducted positive reviews. These reviews have never been made public, as Dragonchain did not pay or contract for these studies to be released.
Bonus points Public, third-party implementation review available or in progress
Compatibility with HSMs & hardware wallets
For the purpose of this proposal, all tokenization would be on the Ethereum network using standard token contracts and as such, would be able to leverage all hardware wallet and Ethereum ecosystem services.
Minting/distributing tokens is not performed by Reddit directly
This operation can be automated by smart contract on Ethereum. Subreddits can if desired have a role to play.
One off point burning, as well as recurring, non-interactive point burning (for subreddit memberships) should be possible and scalable
This is possible and scalable with interaction between Dragonchain Reddit system and Ethereum token contract(s).
Fully open-source solutions are strongly preferred
Dragonchain is fully open source (see section on Disney release after conclusion).
Whether it is today, or in the future, we would like to work together to bring secure flexibility to the highest standards. It is our hope to be considered by Ethereum, Reddit, and other integrative solutions so we may further discuss the possibilities of implementation. In our public demonstration, 256 million transactions were handled in our operational network on chain in 24 hours, for the low cost of $25K, which if run today would cost $625. Dragonchain’s interoperable foundation provides the atmosphere necessary to implement a frictionless community points system. Thank you for your consideration of our proposal. We look forward to working with the community to make something great!
Disney Releases Blockchain Platform as Open Source
The team at Disney created the Disney Private Blockchain Platform. The system was a hybrid interoperable blockchain platform for ledgering and smart contract development geared toward solving problems with blockchain adoption and usability. All objective evaluation would consider the team’s output a success. We released a list of use cases that we explored in some capacity at Disney, and our input on blockchain standardization as part of our participation in the W3C Blockchain Community Group. https://lists.w3.org/Archives/Public/public-blockchain/2016May/0052.html
In 2016, Roets proposed to release the platform as open source to spread the technology outside of Disney, as others within the W3C group were interested in the solutions that had been created inside of Disney. Following a long process, step by step, the team met requirements for release. Among the requirements, the team had to:
Obtain VP support and approval for the release
Verify ownership of the software to be released
Verify that no proprietary content would be released
Convince the organization that there was a value to the open source community
Convince the organization that there was a value to Disney
Offer the plan for ongoing maintenance of the project outside of Disney
Itemize competing projects
Verify no conflict of interest
Change the project name to not use the name Disney, any Disney character, or any other associated IP - proposed Dragonchain - approved
Obtain legal approval
Approval from corporate, parks, and other business units
Approval from multiple Disney patent groups Copyright holder defined by Disney (Disney Connected and Advanced Technologies)
Trademark searches conducted for the selected name Dragonchain
Obtain IT security approval
Manual review of OSS components conducted
OWASP Dependency and Vulnerability Check Conducted
Obtain technical (software) approval
Offer management, process, and financial plans for the maintenance of the project.
Meet list of items to be addressed before release
Remove all Disney project references and scripts
Create a public distribution list for email communications
Remove Roets’ direct and internal contact information
Create public Slack channel and move from Disney slack channels
Create proper labels for issue tracking
Rename internal private Github repository
Add informative description to Github page
Expand README.md with more specific information
Add information beyond current “Blockchains are Magic”
Add getting started sections and info on cloning/forking the project
Add installation details
Add uninstall process
Add unit, functional, and integration test information
Detail how to contribute and get involved
Describe the git workflow that the project will use
Move to public, non-Disney git repository (Github or Bitbucket)
Obtain Disney Open Source Committee approval for release
On top of meeting the above criteria, as part of the process, the maintainer of the project had to receive the codebase on their own personal email and create accounts for maintenance (e.g. Github) with non-Disney accounts. Given the fact that the project spanned multiple business units, Roets was individually responsible for its ongoing maintenance. Because of this, he proposed in the open source application to create a non-profit organization to hold the IP and maintain the project. This was approved by Disney. The Disney Open Source Committee approved the application known as OSSRELEASE-10, and the code was released on October 2, 2016. Disney decided to not issue a press release. Original OSSRELASE-10 document
im testing the latest version of electrum that let you connect to bitcoin-core using a plugin. Everything goes fine until i press save and connect:
ERROR bwt » JSON-RPC error: JSON decode error: EOF while parsing a value at line 1 column 0
if i enable the trace option:
INFO bwt » DEBUG bitcoincore_rpc > JSON-RPC failed parsing reply of getnetworkinfo: sonRpc(Json(Error("EOF while parsing a value", line: 1, column: 0)))
im using bitcoin-core 0.19.1 and electrum 3.3.8 and the plugin version bwt-plugin 0.1.1 and 0.1.2 amd_x86_64 edit: finally it worked!!! electrum is conected to 1 node, that is my node, now im gonna try to connect a cold wallet!!
06-16 12:55 - 'boss linux' (self.linux) by /u/bossdevelopers removed from /r/linux within 437-447min
''' -BOSS PROJECT: Standing for Blockchain Operative System Series is a new Linux distribution based on ubuntu core with important changes, highly improved security and the default incorporation of blockchain services and support for cryptocurrencies.We have modified the original standards to transform it into a very useful tool for the entire bitcoin community consisting of an interesting combination of security, manageability, speed and performance. It can be used on any x64 X86 machine simply after installation. .-BLOCKCHAIN FULLY DEDICATED: It has been more than a decade since the physical birth of cryptocurrencies, although the idea is over 50 years old. The future will undoubtedly be governed by blockchain systems and governments, banks and corporations are already taking positions in this regard. BOSS is not far behind. Now it is possible to mine even if it has not been done previously. For even more in-depth development of the blockchain applications included in BOSS operating systems, you have your own version of bitcoin PoW PoS mining: BitcoinBOSS. Our own blockchain that is enhanced with BOSS token erc20. -BOSS SECURITY & PRIVACY FEATURES: A weak point of easy access for hacker attacks, such as automatic updates, has been modified so that the user can carry out his updates when he deems necessary and under monitoring. The elevated privileges allow you not only to modify the system, they also allow you to quickly act on files that are prohibited from accessing other operating systems. BOSS has installed active-passive security measures -MAC ADDRESS DEFAULT SPOOFING: MAC address Spoofing privacy + from BOSS. Every time you log in to your BOSS computer, you are doing so with a different MAC address. Privacy thus reaches its highest degrees by making MAC-TRACK impossible -LIGHTWEIGHT RECORD: BOSS has achieved maximum performance in a really small space. BOSS takes up very little space and can be downloaded via torrent or direct download through our mirrors. BOSS has concentrated a large operating system in a super small space of less than 1 GB, which puts us at the forefront among the lightest and safest distributions as leaders in relation to gb-installed applications. -INSTALLATION PROCESS: BOSS installation is simple and guided using the ubiquity installer and depending on the performance of your system it can take between 15-30 minutes in normal circumstances. Download BOSS now and enjoy a high level of performance, security and privacy in an enviable small space. BOSS can be tested after installation, fully or partially installed on your system, together with windows or your favorite operating system. .-POWERFUL RECOVERY TOOL: BOSS is an excellent file recovery tool. The combination of BOSS tools and its elevated privileges allow you to access areas hidden or inaccessible. Simply use BOSS live to freely rescue files from the laptop where the BOSS USB is inserted. Recover Bitcoin paraphrase or .DAT files easier and faster than other recovery programs simply by acceding to the file system where BOSS usb is inserted. -STABLE RELEASES: BOSS V01-LTS Available now for download at sourceforge. [**[link]2 FEATURING -UNITY DESKTOP-BRAVE BROWSER-ATOMIC WALLET-COMMON UTILITIES-ELEVATED PRIVILEGES ENABLED.-MAC ADDRESS SPOOFING-FILE SYSTEM RECOVERY TOOL -WE DELIVER BOSS: Using BOSS as removable OS is recommended if you do not want to install the system. For this our team recommends the use of persistent USB where your session is recorded and ready for the next login, find everything as you left it. BOSS makes available to its users the delivery of these persistent USB devices worldwide via regular mail or messaging. The flat rate of our installation on the USB and shipping to the user is USD 20 to which we must add the shipping costs in the options selected by the user. Please check with our team to process your shipment while this process is automated on our website. Order now your BOSS or a even more customized BOSS with your company requirements, logo etc. We deliver in CD, USB or SD card in your selected size from minimal 4GB, however 16GB and above are recommended. [link]3 [link]4 [link]5 ''' boss linux Go1dfish undelete link unreddit undelete link Author: bossdevelopers 1: *ourcef*r*e.**t/proj*cts/*oss-min*mi*al*ed**ion/ 2: sourceforge.net/pr*j*cts*****-mi*im**al-editio****]^*1 3: pr*vie*.*edd.it/2j0i*g*tk755*.p*g*wid*h*1*00&form*t*png&**uto*w**p*a*p;s=57745a79590667**059****948ab*84e*1*693*7 4: *revi*w.red*.it*9l8yh7ag*7551*png?wi*th=160*&a*p;fo*m**=png*amp;a*to=***p&s=acd*6e9**8d2*a**4d*b*14737cf**72**dcc2*5 5: pr**ie**re*d.it*3*qyxtw*k755*.*ng?wid**=*600*amp**ormat=p*g&am*;au*o=webp&am*;s=02b*905*4cb**f770b77*13a3*6**90fc*6*0d3b Unknown links are censored to prevent spreading illicit content.
Public CodeValley/Emergent Consensus questioning and investigation Thread. Ask your hard questions and dispel your doubts here.
What is going on here? I am asking some hard questions for the CodeValley Company, which recently proposed a new revolutionary software development paradigm called Emergent Coding at the latest big Bitcoin Cash conference in Australia. I am asking these questions because, as I (and ~150 people who agreed with me) noticed, there are stunning similarities between CodeValley and the companies who have tried and succeeded in crippling Peer-To-Peer Electronic Cash: nChain and Blockstream. According to me, as it looks now, similarities between these 3 companies (nChain, Blockstream, CodeValley) are the following: }- Sources of funding are extremely unclear or openly hostile to Bitcoin }- At first and even second glance, there is no product, no way to make money }- Whitepaper & Documentation is missing, hollow or total abstract bullshit, company has no logical sense of existence }- Detailed specifications or proofs of operation are not available }- Main products are closed-source patented blobs (BSV, Liquid, Emergent Coding) }- They have huge influences in the industry or try to establish themselves in such position to have the infuences I am here (and you are here, I assume) because we want to find out the truth, whatever the truth is. The point of this topic is to ask the hardest possible questions in order to estimate the probability of CodeValley company being legit. But this is also a chance for CodeValley to clear their name by providing sufficient information that proves that (after 4 years of having working company and 10+ years of having patents [Archived]) they actually have a working product and are a legit company, and not an infiltrator designed and paid by banks/TPTB in order to cripple and destroy Bitcoin Cash. Also if they truly are what they claim and they truly have such a revolutionary technology, this is a great opportunity for promotion. To show the world that the tech actually works. I will ask my questions and you can ask your questions as well. Don't make them easy. Don't have mercy (but these things work better when you are polite). Let's begin the trial by fire! Calling nlovisa My Questions/Tasks for CodeValley: [Of course you actually don't have to answer any of them or you can give us bullshit answers again, but in such case the community may conclude that you actually are next nChain/Blockstream and an enemy infiltrator, reject you and shoot down all your efforts. So the choice is yours] @@@@ 1. Please upload your actual businessplan which you presented to the people in power who gave you funding(VCs? Government?) to create $50 Million BCH tech park. A businessplan which is supposed to explain spending of $50 million AUD should have at least 7 pages (but more probably 20+). Some names and unimportant details (but NOT money/financial numbers) can be redacted. -- You have 6 hours to complete this task -- @@@@ 2. Please list your current VCs and >%5 shareholders, with CEO names and HQ locations of each of them. -- You have 4 hours to complete this task -- @@@@ 3. Few days ago you promised to upload freely-accessible documentation to https://codevalley.com/docs subpage which would describe emergent coding in greater details. @ - What happened to that promise? @@@@ 4. After I accused that your company is bullshit and your product is hollow, you immediately started to praise me and offered me a trip to Australia [Archived]. @ - So, do you always praise and offer a paid trip across the world to Australia to all people on the Internet who heavily criticize you? Is this a common practice in your company? @@@@ 5. A travel from Poland to Australia and back would cost something under $2000 AUD, counting buses, with hotels that would make something close to $2500 AUD even for few days. Based on this, I estimate your "invite random people from the internet to Australia in order to show them the product" budget has to consist of at least $50.000 AUD yearly (but $100.000 - $200.000 is more probable of course). @ A) In your financial books, what exactly is called the Excel position of your budget expenses under which would your secretary put my trip's expenses? @ B) How do you maintain such a large budget for such frivolous spending and how do you explain it to your shareholders/VCs? @@@@ 6. Few days ago you answered somebody a question: "The trust model is also different. The bulk of the testing happens before the project is designed not after. Emergent Coding produces a binary with very high integrity and arguably far more testing is done in emergent coding than in incumbent methods you are used to.". @ A) Who EXACTLY does the testing? People? Software? AI? Non-bullshit answer, please. @ B) Why exactly is there "more testing" in Emergent Coding than in normal software creation paradigm? Why is emergent coding different? Do the developers who work in this paradigm are somehow special? Are the programming languages magical? @ C) What are the specific software tools used for this "testing"? "Agents" is a non-answer, so don't even try. @@@@ 7. Please provide a simple demo binary of a simple program created completely using your "Emergent Coding" and also provide all the binary sub-component files that make up the final binary. Requirements: There has to be a minimum of 3 sub - binaries making up the final big binary for this to be valid. 2 or less does not count. None of the binaries can be obfuscated, they have to be clean X86/X86_64 machine code binaries. Notes: It should be incredibily simple, quick and easy task for you, since designing such a complex and apparently breakthough system must have required thousands, tens of thousands if not hundereds of thousands tests. All of these tests produced working binaries - after all you wouldn't claim you have a working marvellous revolutionary product without extensive testing, right? -- You have 18 hours for this task -- Of course, If you are saying the truth and have truly developed this revolutionary "emergent coding" binary-on-the-fly-merging technology, this should normally take you under 18 minutes to just find the test samples and upload them. @@@@ 8. Please construct a simple (binary or source) single-use-compiler demo that will combine 3 or more sub-binaries into final working product. Please upload the sub-binaries and the "single-use compiler" to publicly available site so people in our community can verify that your product is actually working. The single-use-compiler binary can be obfuscated with proper tool in order to hide your precious intellectual property. The 3 sample sub-binaries cannot be obfuscated. They have to be pure, clean, binary X86/X86_64 machine code. Everything has to be working and verifable of course. -- You have 72 hours to complete this task -- I understand all your technologies are patented with patents that basically predate Bitcoin and you are giving us obfuscated binaries, so you don't have to worry about anybody stealing your company's intellectual property, right? @@@@ 9. You mentioned the only application I need to create programs using Emergent Coding is the pilot app. @ - What programming language(s) is the pilot app written in? @@@@ 10. When you developed the Emerging Coding, before it started existing, you couldn't have used emergent coding to create the first (test & development) applications because it is a chicken and egg problem. @ - What programming language did you use to create first client/serveapi/daemon/tool used to merge multiple binaries into one in Emergent Coding? @@@@ 11. Please list all of your current programmers and programming language each of them is using next to their name. Also provide LinkedIn profiles if applicable. -- You have 18 hours to complete this task -- @@@@ 12. Please also list all Development Environments (IDEs) used by your current programmers next to their name. -- You have 18 hours to complete this task -- @@@@ 13. Please list all compilers used by your current programmers next to their name. -- You have 18 hours to complete this task -- @@@@ 14. So if I understand correctly CodeValley will be the company who runs $50 million BCH tech park and the tech will house multiple Bitcoin Cash-related startup and companies. Let's say I have a BCH startup and I would like to rent a loft/spot in your "tech park". A) Please provide a PDF of sample basic contract you have (hopefully) prepared for such startups. -- You have 4 hours to complete this task -- B) How much does the rent cost per a room (or m2/sqft) for a month and for a year? @@@@ 15. Please submit the list of compilers that produce X86/X86_64/ARM binaries compatibile with Emergent Coding "mash-it-together" "binary compiler". -- You have 4 hours to complete this task -- @@@@ 16. Is it possible for Emergent Coding to merge multiple non-binary applications (like Python or PHP programs) together? Or is it just binaries? Who are you? I am a freedom thinker and individual independent from all infuences who just does what he finds appropriate at the moment. Disclaimer to preempt questions: }- I do not work for anybody }- I do not have any hidden agenda }- I am only doing what I think is right }- I am a born revolutionist, this is why I am in Bitcoin Why are you doing this? }- Because I believe in truth above all. Truth will save us. }- Because I believe in Satoshi's peer-to-peer cash for the world vision and I will not stray from this path. }- Because most people are apparently missing psychological immune system which is why attempts like Blockstream, nChain appear and are repetedly [at least partially] successful. I have an anti-bullshit immune system that works great against this type of attacks. I was actually one of the first to be banned in /Bitcoin sub for pointing out their lies with manipulations and to spot Craig Wright's attempt to infiltrate and bend /btc sub to his will.. }- Because I was fooled twice by entities similar to CodeValley before (namingly nChain and Blockstream) and I will not be fooled again. Bitcoin Cash will not be co-opted easily as long as I am here. }- Because if Bitcoin Cash community is an organism, then I became a B lymphocyte cell. I produce antibodies. I show you how to defend yourself from bullshit, lies and manipulation. This is my basic function. }- Because I am here to kill the bank
Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything. The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years. In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.
UPDATED - Groestlcoin Core 2.18.2
This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables. NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.
Builds are now done through Gitian
Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
deriveaddresses returns one or more addresses corresponding to an output descriptor.
getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
If a blockhash is provided, check the corresponding block.
If no blockhash is provided, check the mempool.
If no blockhash is provided but txindex is enabled, also check txindex.
unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
addwitnessaddress is removed after being deprecated in version 2.16.0.
generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
How to Upgrade?
Windows If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer. OSX If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications. Ubuntu http://groestlcoin.org/forum/index.php?topic=441.0
ALL NEW - Groestlcoin Moonshine iOS/Android Wallet
Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network. GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.
Groestlcoin Mainnet & Testnet supported
Multiple wallet support
Electrum - Support for both random and custom peers
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled. HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user. Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.
Simplified payment verification for fast mobile performance
Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases. This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats. To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.
If a word is wrong, the tool will try to suggest the closest option.
If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator. VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline. If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address. VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase. VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).
Fixed size arithmetic
Fast Modular Inversion (Delayed Right Shift 62 bits)
SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
Use some properties of elliptic curve to generate more keys
SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet. If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).
Ability to continue finding keys after first one is found
Includes warning on start-up if connected to the internet
Ability to output keys to a text file (And shows button to open that directory)
Show and hide the private key with a simple toggle switch
Show full output of commands
Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
Features both a Light and Dark Material Design-Style Themes
Free software - MIT. Anyone can audit the code.
Written in C# - The code is short, and easy to review.
Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode. This wallet was previously deprecated but has been brought back to life with modern standards.
Works via TOR or SOCKS5 proxy
Can use bootstrap.dat format as blockchain database
Import/Export blockchain to/from bootstrap.dat
Import wallet.dat from Groestlcoin-qt wallet
Export wallet to wallet.dat
Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
Rescan blockchain with a simple mouse click
Works as a full node and listens to port 1331 (listening port can be changed)
Fast Block verifying, parallel processing on multi-core CPUs
Mine Groestlcoins with your CPU by a simple mouse click
All private keys are kept encrypted on your local machine (or on a USB stick)
Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
Free and decentralised - Open Source under GNU license
Fixed Import/Export to wallet.dat
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node. It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node. Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine. Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in. Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet. Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.
Use your own node
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
UPDATED – Android Wallet 7.38.1 - Main Net + Test Net
The app allows you to send and receive Groestlcoin on your device using QR codes and URI links. When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.
Add confidence messages, helping users to understand the confidence state of their payments.
Handle edge case when restoring via an external app.
Count devices with a memory class of 128 MB as low ram.
Introduce dark mode on Android 10 devices.
Reduce memory usage of PIN-protected wallets.
Tapping on the app's version will reveal a checksum of the APK that was installed.
Fix issue with confirmation of transactions that empty your wallet.
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets). Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet. Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.
Groestlcoin September 2019 Development Release/Update!
For a more interactive view of changes, click here In our current world; bordering on financial chaos, with tariff wars, Brexit and hyperinflation rife, you can count on Groestlcoin to consistently produce innovation that strikes to take the power away from the few and into the many, even after a full five and a half years of solid development. Here is what the team has already announced in the last 3 months since the last development update:
Groestl Nodes aims to map out and compare the status of the Groestlcoin mainnet and testnet networks. Even though these networks share the same protocol, there is currently no way to directly compare these coins in a single location. These statistics are essential to evaluate the relative health of both networks.
Shows Onion (Tor) nodes
Shows IPv6 nodes
Supports both main net and test net
Node Checker – Check the status of a remote node
Ability to download node data by CSV, JSON or TXT format
Ability to download unique address data by CSV, JSON or TXT format
This is a tool for creating unsigned raw Groestlcoin transactions and also to verify existing transactions by entering in the transaction hex and converting this to a human-readable format to verify that a transaction is correct before it is signed.
Create Raw Unsigned Groestlcoin transactions
Generates a QR code for the transaction
Compatible with most Groestlcoin wallets including but not restricted to Groestlcoin Core and Electrum-GRS
Estimates final signed transaction size
Taking a raw transaction format and shows its Transaction ID, Transaction Inputs and Outputs
AGCore is an Android app designed to make it easier to run a Groestlcoin Core node on always-on Android appliances such as set-top boxes, Android TVs and repurposed tablets/phones. If you are a non-technical user of Groestlcoin and want an Android app that makes it easy to run a Groestlcoin Core node by acting as a wrapper, then AG Core is the right choice for you.
Update to Groestlcoin Core 2.17.2
Switched to native builds via NDK for Groestlcoin Core resulting in a smaller footprint.
Added embedded tor
Added tor pairing support
TOR upgrade bug fixes
Improved blockchain Sync progress using getblockchaininfo verificationprogress
Improved package download progress bar
Added support for external storage access > Android M
Added support for Android Oreo, including new notification mechanism
Bump Fee (RBF) improvements – Implemented a new fee-bump strategy that can add new inputs, so now any transaction can be fee-bumped. The old strategy was to decrease the value of outputs (starting with change). We will now try the new strategy first, and only use the old as a fallback.
Coin Choser improvements
More likely to construct transactions without change (where possible)
Less likely to construct transactions with really small change
Only spend negative effective value coins when beneficial for privacy
Fix long-standing bug that broke wallets with >65k addresses
Windows binaries: Now build the PyInstaller bootloader ourselves, as this seems to reduce anti-virus false positives
Fix performance regression for large wallets
Fix high-DPI issues related to text fields
Trezor – Allow bypassing 'too old firmware' error
Trezor – Use only the Bridge to scan devices if it is available
Hardware wallets – On Win10-1903, some hardware devices with U2F functionality can only be detected with Administrator privileges. A workaround is to run as Admin, or for Trezor to install the Bridge.
The AppImage Linux x86_64 binary and the Windows setup.exe are now built reproducibly.
Fix watch-only wallets that could not bump fee in some scenarios
Faster transaction signing for segwit inputs or really large transactions.
Groestlwallet is designed to protect you from malware, browser security holes, even physical theft. With AES hardware encryption, app sandboxing, keychain and code signatures, groestlwallet represents a significant security advance over web and desktop wallets, and other mobile platforms. Simplicity is groestlwallet's core design principle. Because groestlwallet is "deterministic", your balance and entire transaction history can be restored from just your recovery phrase.
iOS 0.7.3 Changes
Fix BIP70 payments
Updated QR Scanner
Lowered spending limit
Updated DNS Seeds
Fixed URL Scheme
Fixed GRS Name in mailing
Fixed crash upon starting in some scenarios
Android v89 Changes
Use default fee
Republished on Google Play by removing send_sms permissions
Quick Intro to Gemini's API: Learn Some Python, Save on Fees (0.35%)
There's been recent Gemini news with their new platform rollout and increased fee schedule. I know many users are unhappy and looking for new exchanges. It can take awhile to get verified somewhere else, so in the meantime, this prompted me to learn a bit about using API's as I've never done so before. This is also coupled with my desire to eventually learn python. I took an afternoon and figured it out for myself and saved some money on fees. I'll share what I have so far with the Disclaimer that I am NOT a programmer; however, the code is pretty basic and somewhat self-explanatory.
I'm on Windows 7 x64 Ultimate. I installed the latest Python for Windows binary first. It installed x86 version of python; that is fine. Now you need two additional packages: requests and pywin32. Open a command prompt, also called cmd.exe, by finding it in accessories or searching for it. You can also hit Windows Key + R, type cmd then hit Enter. From here, try pip install requests or try python -m pip install requests Next install the pywin32 package pip install pywin32 or python -m pip install pywin32 You can also install its binary from here. You want to grab the version that matches your Python install not your OS bit. Mine was the last one, Win32 Py3.7. Take a read through Gemini's API reference page. It's okay if you don't understand everything. For placing orders, we're using the API private client, which requires you to generate a key and assign it a role. This can be done in Settings, API Settings. I assigned mine a role of Trader. I can still deposit/withdrawal on the web interface and don't need the API for that as there's no benefit really, for me at least. The API Key is akin to a public key, and the API Secret is akin to a private key. Instead of having my API secret sitting in plain text on my computer, I decided to keep it in my Trezor's password manager. The script that I edited/made, pulls the secret from the clipboard, submits the order, then clears the clipboard. This isn't as secure as my Bitcoin private keys, but to me, it reduces risk drastically and also prevents accidental buy orders.
Python scripts possess the extension, .py and if your computer is configured correctly, are directly executable by double-clicking them. For this use, I would recommend having a bit more control and running them through command prompt. In your main Windows user folder, create a folder called Gemini and put the two scripts there. There is a Test Secret script and a Buy Order Example script. You need to give these files the .py extension either by renaming them or opening in Notepad, resaving ending in .py with All Files as file type. Now, read through the scripts and paste in the required info. I would start with the Test Secret script to test your Python setup and see if you can pull a secret correctly from the clipboard. Go into the script and copy the practice secret. From the command prompt, navigate to this folder. My prompt starts in my user folder, so I can do cd Gemini and it should take you there. Now you can run the script by typing with the quotes "Test Secret.py" or python "Test Secret.py" You should see your secret twice, with the second one looking like b'some string of characters'. If you get a TypeError / Clipboard error, try copying the text again. If this is successful, edit the Buy Order Example script to create a new order, save the script. Copy your actual secret to the clipboard and run in command prompt in the same way. "Buy Order 1.py" Remember the Buy Order script is runnable, so once you copy your actual secret, it's locked and loaded. Be careful! I want to give a nod to mtusman who created the gemini-python client, link to github. This provides a more streamlined Python approach and covers all of the API's functionality. Let me know how it goes.
Hashrate: went from 54 to 76 PH/s, the low was 50 and the new all-time high is 100 PH/s. BeePool share rose to ~50% while F2Pool shrank to 30%, followed by coinmine.pl at 5% and Luxor at 3%. Staking: 30-day average ticket price is 95.6 DCR (+3.0) as of Sep 3. During the month, ticket price fluctuated between a low of 92.2 and high of 100.5 DCR. Locked DCR represented between 3.8 and 3.9 million or 46.3-46.9% of the supply. Nodes: there are 217 public listening and 281 normal nodes per dcred.eu. Version distribution: 2% at v1.4.0(pre) (dev builds), 5% on v1.3.0 (RC1), 62% on v1.2.0 (-5%), 22% on v1.1.2 (-2%), 6% on v1.1.0 (-1%). Almost 69% of nodes are v.1.2.0 and higher and support client filters. Data snapshot of Aug 31.
Obelisk posted 3 email updates in August. DCR1 units are reportedly shipping with 1 TH/s hashrate and will be upgraded with firmware to 1.5 TH/s. Batch 1 customers will receive compensation for missed shipment dates, but only after Batch 5 ships. Batch 2-5 customers will be receiving the updated slim design. Innosilicon announced the new D9+ DecredMaster: 2.8 TH/s at 1,230 W priced $1,499. Specified shipping date was Aug 10-15. FFMiner DS19 claims 3.1 TH/s for Blake256R14 at 680 W and simultaneously 1.55 TH/s for Blake2B at 410 W, the price is $1,299. Shipping Aug 20-25. Another newly noticed miner offer is this unit that does 46 TH/s at 2,150 W at the price of $4,720. It is shipping Nov 2018 and the stats look very close to Pangolin Whatsminer DCR (which has now a page on asicminervalue).
www.d1pool.com joined the list of stakepools for a total of 16. Australian CoinTreeadded DCR trading. The platform supports fiat, there are some limitations during the upgrade to a new system but also no fees in the "Early access mode". On a related note, CoinTree is working on a feature to pay household bills with cryptocurrencies it supports. Three new OTC desks were added to exchanges page at decred.org. Two mobile wallets integrated Decred:
Coinomiadded Decred to their Android and iOS wallets. In addition to the Apple App Store and Google Play you can download the APK directly. Coinomi features an integrated cryptocurrency exchange and is the first company to offer a mobile Decred wallet.
Reminder: do your best to understand the security and privacy model before using any wallet software. Points to consider: who controls the seed, does the wallet talk to the nodes directly or via middlemen, is it open source or not?
Bit Dialsannounced DCR support via GloBee at their bitdials.eu luxury boutique. Their separate supercar and classic car shop bitcars.eu also accepts DCR, either via GloBee or with manual invoicing in case of privacy concerns.
Targeted advertising report for August was posted by @timhebel. Facebook appeal is pending, some Google and Twitter campaigns were paused and some updated. Read more here. Contribution to the @decredproject Twitter account has evolved over the past few months. A #twitter_ops channel is being used on Matrix to collaboratively draft and execute project account tweets (including retweets). Anyone with an interest in contributing to the Twitter account can ask for an invitation to the channel and can start contributing content and ideas there for evaluation by the Twitter group. As a result, no minority or unilateral veto over tweets is possible. (from GitHub)
Meetup in Puebla City, Mexico, organized by @elian. (photo, slides, missed in July issue)
@joshuam discussed Decred and decentralized organizations with Craig Laundy, Federal Minister for Small Business, the Workplace, and Deregulation with the Australian Government, at @YBFVentures. (photos)
Meetup at @TheBlockCafe in Lisbon, Portugal. @mm presented "Decred 101 - Governance with Skin in the Game" and @moo31337 talked about Decred's 2018 roadmap. (photos: 123)
Meetup in Taipei, Taiwan. @morphymore made a short intro of Decred and noted: "After the talk, many have approached to tell me that they literally don’t hear of Decred until today, and are interested in finding out more about the merit of a hybrid consensus system.". Longer report here, some photos and a video are here.
@eSizeDave introduced Decred to the SILC Undergraduate Program students at @YBFVentures. (photo)
OKEx Global Meetup Tour in Ho Chi Minh City, Vietnam. @joshuam gave a brief presentation covering the history of Decred, how the project functions, and the importance of governance. Afterwards he joined a panel discussion and spoke about Decred's incentives for long term viability. (video, video, photo)
Blockchain Futurist Conference in Toronto, Canada. @zubairzia0 noted: "Devs and the community were held in high regard for the people who knew about decred ... one positive thing I remember was someone defending us saying 'Decred does not need a booth', I believe that comment was reflective of the quality of projects being showcased at the conference.". (photo)
Meetup at @YBFVentures in Melbourne, Australia. @joshuam discussed Decred with Graham Stuart, U.K. Minister for International Trade. (news, photos)
Small meetup with Jackson Palmer in Melbourne, Australia. (photo)
Hawthorne Street Fair in Portland, USA. Raedah Group was out answering questions about crypto and Decred. (photos)
Blockchain APAC in Melbourne, Australia. @joshuam joined a panel discussion with reps from banking, university and ISO/TC 307. @eSizeDave reports: "This enterprise conference was indeed a whole lot better than I expected. The presentations were actually full of very worthwhile information from credible people, articulated aptly to a very government, academic, and corporate crowd, who genuinely took on board valuable insights. Good to know some of these key people are Decred holders and stakers as well. I got to use the entire day to speak directly with some of the most pivotal personalities in this particular populace. Ongoing relationships have been built and strengthened.". (photos: 123)
For those willing to help with the events:
BAB: Hey all, we are gearing up for conference season. I have a list of places we hope to attend but need to know who besides @joshuam and @Haon are willing to do public speaking, willing to work booths, or help out at them? You will need to be well versed on not just what is Decred, but the history of Decred etc... DM me if you are interested. (#event_planning) The Decred project is looking for ambassadors. If you are looking for a fun cryptocurrency to get involved in send me a DM or come talk to me on Decred slack. (@marco_peereboom, longer version here)
One private work channel was successfully migrated to Matrix.
Stylish room avatars were set.
@Haon has prepared a short guide to help new Matrix users get started and join the Decred rooms.
A thread was started to discuss changes to Decred jargon with the intent to make it more consistent and accessible to newcomers. The question whether changing "official" terminology requires stakeholder approval was touched in this thread and in #documentation.
Project fund transparency and constitution were extensively discussed on Reddit and in #general.
Pre-proposal to use Politeia to approve Politeia as a legitimate decision-making tool for Decred.
Reddit: substantive discussion about Decred cons; ecosystem fund; a thread about voter engagement, Politeia UX and trolling; idea of a social media system for Decred by @michae2xl; how profitable is the Obelisk DCR1. Chats: cross-chain trading via LN; plans for contractor management system, lower-level decision making and contractor privacy vs transparency for stakeholders; measuring dev activity; what if the network stalls, multiple implementations of Decred for more resilience, long term vision behind those extensive tests and accurate comments in the codebase; ideas for process for policy documents, hosting them in Pi and approving with ticket voting; about SPV wallet disk size, how compact filters work; odds of a wallet fetching a wrong block in SPV; new module system in Go; security of allowing Android app backups; why PoW algo change proposal must be specified in great detail; thoughts about NIPoPoWs and SPV; prerequisites for shipping SPV by default (continued); Decred vs Dash treasury and marketing expenses, spending other people's money; why Decred should not invade a country, DAO and nation states, entangling with nation state is poor resource allocation; how winning tickets are determined and attack vectors; Politeia proposal moderation, contractor clearance, the scale of proposals and decision delegation, initial Politeia vote to approve Politeia itself; chat systems, Matrix/Slack/Discord/RocketChat/Keybase (continued); overview of Korean exchanges; no breaking changes in vgo; why project fund burn rate must keep low; asymptotic behavior of Decred and other ccs, tail emission; count of full nodes and incentives to run them; Politeia proposal translations and multilingual environment. An unusual event was the chat about double negatives and other oddities in languages in #trading.
DCR started the month at USD 56 / BTC 0.0073 and had a two week decline. On Aug 14 the whole market took a huge drop and briefly went below USD 200 billion. Bitcoin went below USD 6,000 and top 100 cryptos lost 5-30%. The lowest point coincided with Bitcoin dominance peak at 54.5%. On that day Decred dived -17% and reached the bottom of USD 32 / BTC 0.00537. Since then it went sideways in the USD 35-45 / BTC 0.0054-0.0064 range. Around Aug 24, Huobi showed DCR trading volume above USD 5M and this coincided with a minor recovery. @ImacallyouJawdy posted some creative analysis based on ticket data.
StopAndDecrypt published an extensive article "ASIC Resistance is Nothing but a Blockchain Buzzword" that is much in line with Decred's stance on ASICs. The ongoing debates about the possible Sia fork yet again demonstrate the importance of a robust dispute resolution mechanism. Also, we are lucky to have the treasury. Mark B Lundeberg, who found a vulnerability in atomicswap earlier, published a concept of more private peer-to-peer atomic swaps. (missed in July issue) Medium took a cautious stance on cryptocurrencies and triggered at least one project to migrate to Ghost (that same project previously migrated away from Slack). Regulation: Vietnam bans mining equipment imports, China halts crypto events and tightens control of crypto chat groups. Reddit was hacked by intercepting 2FA codes sent via SMS. The announcement explains the impact. Yet another data breach suggests to think twice before sharing any data with any company and shift to more secure authentication systems. Intel and x86 dumpsterfire keeps burning brighter. Seek more secure hardware and operating systems for your coins. Finally, unrelated to Decred but good for a laugh: yetanotherico.com.
About This Issue
This is the 5th issue of Decred Journal. It is mirrored on GitHub, Medium and Reddit. Past issues are available here. Most information from third parties is relayed directly from source after a minimal sanity check. The authors of Decred Journal have no ability to verify all claims. Please beware of scams and do your own research. Feedback is appreciated: please comment on Reddit, GitHub or #writers_room on Matrix or Slack. Contributions are welcome too. Some areas are collecting content, pre-release review or translations to other languages. Check out @Richard-Red's guide how to contribute to Decred using GitHub without writing code. Credits (Slack names, alphabetical order): bee, Haon, jazzah, Richard-Red and thedecreddigest.
8/23 Come-from-BeyondToday at 5:17 AM In IoT broadcasting is enough to prove that work has been done and that requires few microseconds That technique goes under "NBPoW" codename now Come-from-BeyondToday at 5:23 AM [Wouldn't a system like this be vulnerable to interference of non-IoT devices?] jamming is possible Come-from-BeyondToday at 5:25 AM [where is this magical IoT land] In prototyping phase - https://www.youtube.com/watch?v=jV3RpeJNvbU Come-from-BeyondToday at 5:26 AM [That's a LiFi demo, no?] yes [simply a means of sending data already in use today?] yes, but noone offered a complete IoT solution yet Come-from-BeyondToday at 5:36 AM [So, NBPoW with LiFi, is that like PoW based on keeping the sending party light emitter occupied with sending the data as a form of proof of work?] No [jamming is possible. is that not a big problem?] Yes, and it's not solved yet. Luckily for LiFi it's much easier to see the location of the jammer. Eric Hop [IF]Today at 3:29 AM Abra is an intermediate language that is as close to assembler as you can get while still enabling translation to wildly different architectures like x86 and fpga I am in the process of writing a document that explains the Qubic Processing Model and describes Abra as part of that. May take a little while because I want it to be coherent and understandable. The concepts involved are alien enough as it is. Eric Hop [IF]Today at 6:28 AM I'm currently sitting with Paul discussing things and clarifying things and the conclusions we are drawing about the possibilities of Qubic are staggering. @stanley Abra is not exactly a VM. A virtual machine is usually a piece of software that can be compiled to different hardware platforms and then interprets the virtual machine code. Abra uses JIT-compilation to actually generate target machine code, including hardware like CPU, GPU, and FPGA. There is a Supervisor component, but all that one does is instantiating, loading, JIT-compiling (if necessary), and triggering the code. The Supervisor also handles the sending of events between qubics. Eric Hop [IF]Today at 6:48 AM Mind = blown. Paul just implemented Curl hash function in Abra as a real-world example of Abra code. Took him less than an hour, and most of it was fiddling with the editor to generate the correct tables. We're trying to get a feel for the language at the moment. Can't wait for the compiler to be ready. Eric Hop [IF]Today at 7:20 AM Abra is badass. Seriously. Paul and I are deep-diving in what it can do. While discussing it all kinds of light bulbs were going off on both sides. You know how when you have a deep discussion and try to explain what you are thinking to someone else you yourself get a deeper understanding? We've had several of these breakthrough moments within the last 24 hours. Eric Hop [IF]Today at 7:58 AM We're cleaning up some syntax rules in Abra at the moment. Actually using it in real life highlights where we want things to be simpler to do, or more readable. Once we have that we will probably incorporate those changes and post the Abra Curl function here. Just to throw you guys a bone until we have more extensive documentation. Eric Hop [IF]Today at 8:55 AM @Werner We have no syntax highlighting modules yet if that's what you are hoping for Eric Hop [IF]Today at 9:09 AM Right now it looks unlike pretty much anything I have ever seen and yet it seems familiar. We're trying to use familiar constructs as much as possible, yet some things are very different, even if they look like something you already know. The code looks familiar in that you see lots of lines of assignments, array-like tables, and function definitions. It looks unfamiliar in that the usual control statements are completely missing. No if-then-else, no loops. And yet it expresses the intent in a very simple and elegant way if you understand how it works. 8/24 Eric Hop [IF]Yesterday at 11:28 PM [Will Abra have an IDE?] @Zass Initially no IDE. Use your favorite code editor or dev environment. [@Eric Hop [IF] is it possible to use AOT compilation if you were to write something in Abra and distribute it in native code?] @Rajiv Shah Distributing in native code would limit the use of the qubic to the architecture it was compiled for. Eric Hop [IF]Today at 5:53 AM These things is literally where our community can shine. Creating syntax-highlighting for Abra in multiple dev environments. I would love an IntelliJ syntax highlighter for Abra for example. Ralf Rottmann [IF]Yesterday at 4:05 AM There is a modified (experimental) IRI node connected to the coordinator, and this node rejected valid transactions due to some minor issues. Once we understood the root cause, we fixed the code in this version of IRI and everything is back to normal. Eric Hop [IF]Last Friday at 10:52 AM @Ganreizu Since it is a JIT compiler compilation only needs to be done once when a qubic is instantiated and could be cached for future usage. Abra source code will be translated into intermediate trit code representation called Handy, so any translation phase will only need to load that representation of the code tree (no parsing, syntax checking, etcetera is necessary) and then can directly map that code tree to LLVM or Verilog. So it's the qubic packaging process that does the translation from Abra source code into Handy and that happens only once on the side of the qubic creator. This will allow for all kinds of handy (pun intended) tools in the future. We imagine a decompiler that can turn Handy back into Abra source code for example, or an obfuscator that can obfuscate Handy similar to how Java byte code is obfuscated. We also have ideas (very future ideas) for IDE's that can directly emit Handy, or even Evolutionary Algorithms (EA) that can generate optimal Handy trit code directly for certain applications. @empler All this will be open source code. No patents. @thebruce44 It's a functional programming language. With a few twists. Definitely a paradigm shift. But on the other hand it turns out the code is simple and elegant. It's less problematic to directly code into it than we originally anticipated. 8/26 Eric Hop [IF]Today at 2:21 AM [@Eric Hop [IF] hi Eric :nerd: do you know what's happening with exchanges?] Nope. Haven't used exchanges in a while and am too busy with Qubic. Eric Hop [IF]Today at 3:32 AM After last week I have revised my thoughts about this. Paul and I tried to implement 2 practical applications using Abra. We implemented the old Curl function just for laughs and it was possible and surprisingly easy without excessive bootstrap steps. We then proceeded to implement a key-value store and again it was entirely possible with hardly any bootstrapping, Practical applications will definitely be possible and we will demonstrate that with a cool idea we have for our PoC. Given these encouraging results I revised our chances of having a PoC by end of year from my original personal estimate of 50/50 to 95%. This does not mean Abra has been vetted. The compiler is still under development (80%). And after the compiler is done we will still need to build the Supervisor to be able to run the code as intended. We simply wrote source code that looked as if it should do what we want it to do, just like you can do in any language as a thought experiment without compiling. 8/27 Come-from-BeyondYesterday at 4:20 PM [Is there a POS staking reward opportunity in this Economic Clustering? If so, will it have a liquidity function or security function?] no. n/a. but there is opportunity to earn money with Ict Come-from-BeyondYesterday at 4:23 PM [@Come-from-Beyond iota coin?] iotas Come-from-BeyondYesterday at 4:31 PM [Any estimate when the next round of testing will start? I have to RPis I could prepare.] I'll know that after meeting with some people 8/28 domToday at 1:48 AM [Dom, Is the entire IF on the webpage yet?] no 15 - 18 people are missing domToday at 1:49 AM [still on holiday?] aye, until the 29th but I'm working ofc domToday at 1:53 AM [@dom when can we expect an update on the 15 companies that was on sumsum?] @TomTom not sure, it's a bigger project that takes serious effort to setup (several months) [Cfb says "IOTA can be created out of thin air" Is IOTA inflationary?] @drmvb no domToday at 1:54 AM [Dom. Noticeable improvement in comms recently from the whole team. Much appreech] @Northern🐳😍 agree, there is more room for improvement still domToday at 1:57 AM [Hey @dom, may I ask about the marketplace update which was said to be given last week? Just curious.] was postponed as we had to hire a new designer for the website (we are adding more pages to explain how the marketplace works etc.) domToday at 2:04 AM [@dom will iota marketplace be linked to oracles for analysis or is it strictly purchase and keep model?] that will be later domToday at 2:08 AM [Dom, is IF working with banks at the moment? You mentioned once there are a lot of use cases with IOTA considering PSD2. Is there happing anything behind closed curtains?] @icho yeh of course. We have MOU's with SinoPac and DNB and are working with others domToday at 2:16 AM [@dom are you feeling the IF is growing to a organisation that is less depended on private individuals?] @TomTom yeh, absolutely microhashYesterday at 8:38 PM i bought iota a year ago back when most people just barely knew about bitcoin and iota had just been listed on the first major exchange. i held through all the fud while iota matured from a startup to an organized foundation. lots of new partnerships, more exchange listings and now we have ixi hub and a perfectly working wallet. and yet, it's still cheaper than a year ago. if you buy now, think about it like this: you are getting what people bought a year ago back when everything was unclear. and they are getting out at a loss after holding that high risk asset for an entire year. sounds like a fucking opportunity to me.
Revision 1.4 - (show annotations) () Sat Jan 10 17:19:55 2015 UTC (5 years, 3 months ago) by blueness Branch: MAIN CVS Tags: HEAD Changes since 1.3: +1 -1 lines FILE REMOVED Version bump for bug #536228 (Portage version: 2.2.14/cvs/Linux x86_64, signed Manifest commit with key 0xF52D4BBA) If you want to deposit some amount of BTCs in testnet, you can use the bitcoin testnet faucet on the Web, such as, here. (Search for other bitcoin testnet faucet sites on the Web.) Unlike Bitcoin mainnet, there’s no need to pay real money for getting BTCs (satoshis) in Bitcoin testnet. Bitcoin Knots began in 2011 December as Bitcoin Next-Test, a derivative of Bitcoin Core's "master" branch with upcoming and proposed features merged in manner as unbiased as possible toward the changes themselves. In 2014, due to time constraints and a desire to maintain a more stable and well-maintained derivative, I began instead to base the branch off the latest stable release, and include ... In the output produced by the above command, you can safely ignore any warnings and failures, but you must ensure the output lists "OK" after the name of the release file you downloaded. For example: bitcoin-0.20.1-x86_64-linux-gnu.tar.gz: OK. Obtain a copy of the release signing key by running the following command: A test network called the Testnet (where coins with no associated value are traded for testing purposes), and ; A regression testing network (where coins are created instantly and are never traded to others outside the user’s network). Coins mined in one network stay in that network, thus coins cannot be transferred between networks. It is because of this separation that we are able to use ...
Test This stream is created with #PRISMLiveStudio Withdraw #Fast #Miner #Android #Bitcoin #Miner 2020 #bitcoincloudmining #bitcoingenerator #freebitcoin #Bitcoingeneratornofee #Cloud Mining 2019 Bitcoin generator 2019Bitcoin generator 2019 #Apk # ... انشالله تفعيل خاصية أبتفي على راوتر Tp-link من هاتفك بطريقه سهله وبسيطه لكي تستمع بمشاهدة جميع قنوات العالمية ... Crypto Mining - Bitcoin Wallet และสาธิตการขุด - Part 02 - Duration: 44:50. Anachakmobile 14,134 views. 44:50 . The best way to become a millionaire in five years or ... Bitcoin Mining Play APP Fake OR Real With Live Proof bitcoinmininglite APP Review - Duration: 3:32. Hussain Teach 4,811 views. 3:32 . How To Mine Bitcoin On Android - Duration: 4:18 ...