bitcoin-qt.exe Windows process - What is it?

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

Syscoin Platform’s Great Reddit Scaling Bake-off Proposal

Syscoin Platform’s Great Reddit Scaling Bake-off Proposal

https://preview.redd.it/rqt2dldyg8e51.jpg?width=1044&format=pjpg&auto=webp&s=777ae9d4fbbb54c3540682b72700fc4ba3de0a44
We are excited to participate and present Syscoin Platform's ideal characteristics and capabilities towards a well-rounded Reddit Community Points solution!
Our scaling solution for Reddit Community Points involves 2-way peg interoperability with Ethereum. This will provide a scalable token layer built specifically for speed and high volumes of simple value transfers at a very low cost, while providing sovereign ownership and onchain finality.
Token transfers scale by taking advantage of a globally sorting mempool that provides for probabilistically secure assumptions of “as good as settled”. The opportunity here for token receivers is to have an app-layer interactivity on the speed/security tradeoff (99.9999% assurance within 10 seconds). We call this Z-DAG, and it achieves high-throughput across a mesh network topology presently composed of about 2,000 geographically dispersed full-nodes. Similar to Bitcoin, however, these nodes are incentivized to run full-nodes for the benefit of network security, through a bonded validator scheme. These nodes do not participate in the consensus of transactions or block validation any differently than other nodes and therefore do not degrade the security model of Bitcoin’s validate first then trust, across every node. Each token transfer settles on-chain. The protocol follows Bitcoin core policies so it has adequate code coverage and protocol hardening to be qualified as production quality software. It shares a significant portion of Bitcoin’s own hashpower through merged-mining.
This platform as a whole can serve token microtransactions, larger settlements, and store-of-value in an ideal fashion, providing probabilistic scalability whilst remaining decentralized according to Bitcoin design. It is accessible to ERC-20 via a permissionless and trust-minimized bridge that works in both directions. The bridge and token platform are currently available on the Syscoin mainnet. This has been gaining recent attention for use by loyalty point programs and stablecoins such as Binance USD.

Solutions

Syscoin Foundation identified a few paths for Reddit to leverage this infrastructure, each with trade-offs. The first provides the most cost-savings and scaling benefits at some sacrifice of token autonomy. The second offers more preservation of autonomy with a more narrow scope of cost savings than the first option, but savings even so. The third introduces more complexity than the previous two yet provides the most overall benefits. We consider the third as most viable as it enables Reddit to benefit even while retaining existing smart contract functionality. We will focus on the third option, and include the first two for good measure.
  1. Distribution, burns and user-to-user transfers of Reddit Points are entirely carried out on the Syscoin network. This full-on approach to utilizing the Syscoin network provides the most scalability and transaction cost benefits of these scenarios. The tradeoff here is distribution and subscription handling likely migrating away from smart contracts into the application layer.
  2. The Reddit Community Points ecosystem can continue to use existing smart contracts as they are used today on the Ethereum mainchain. Users migrate a portion of their tokens to Syscoin, the scaling network, to gain much lower fees, scalability, and a proven base layer, without sacrificing sovereign ownership. They would use Syscoin for user-to-user transfers. Tips redeemable in ten seconds or less, a high-throughput relay network, and onchain settlement at a block target of 60 seconds.
  3. Integration between Matic Network and Syscoin Platform - similar to Syscoin’s current integration with Ethereum - will provide Reddit Community Points with EVM scalability (including the Memberships ERC777 operator) on the Matic side, and performant simple value transfers, robust decentralized security, and sovereign store-of-value on the Syscoin side. It’s “the best of both worlds”. The trade-off is more complex interoperability.

Syscoin + Matic Integration

Matic and Blockchain Foundry Inc, the public company formed by the founders of Syscoin, recently entered a partnership for joint research and business development initiatives. This is ideal for all parties as Matic Network and Syscoin Platform provide complementary utility. Syscoin offers characteristics for sovereign ownership and security based on Bitcoin’s time-tested model, and shares a significant portion of Bitcoin’s own hashpower. Syscoin’s focus is on secure and scalable simple value transfers, trust-minimized interoperability, and opt-in regulatory compliance for tokenized assets rather than scalability for smart contract execution. On the other hand, Matic Network can provide scalable EVM for smart contract execution. Reddit Community Points can benefit from both.
Syscoin + Matic integration is actively being explored by both teams, as it is helpful to Reddit, Ethereum, and the industry as a whole.

Proving Performance & Cost Savings

Our POC focuses on 100,000 on-chain settlements of token transfers on the Syscoin Core blockchain. Transfers and burns perform equally with Syscoin. For POCs related to smart contracts (subscriptions, etc), refer to the Matic Network proposal.
On-chain settlement of 100k transactions was accomplished within roughly twelve minutes, well-exceeding Reddit’s expectation of five days. This was performed using six full-nodes operating on compute-optimized AWS c4.2xlarge instances which were geographically distributed (Virginia, London, Sao Paulo Brazil, Oregon, Singapore, Germany). A higher quantity of settlements could be reached within the same time-frame with more broadcasting nodes involved, or using hosts with more resources for faster execution of the process.
Addresses used: 100,014
The demonstration was executed using this tool. The results can be seen in the following blocks:
612722: https://sys1.bcfn.ca/block/6d47796d043bb4c508d29123e6ae81b051f5e0aaef849f253c8f3a6942a022ce
612723: https://sys1.bcfn.ca/block/8e2077f743461b90f80b4bef502f564933a8e04de97972901f3d65cfadcf1faf
612724: https://sys1.bcfn.ca/block/205436d25b1b499fce44c29567c5c807beaca915b83cc9f3c35b0d76dbb11f6e
612725: https://sys1.bcfn.ca/block/776d1b1a0f90f655a6bbdf559ff5072459cbdc5682d7615ff4b78c00babdc237
612726: https://sys1.bcfn.ca/block/de4df0994253742a1ac8ac9eec8d2a8c8b0a6d72c53d6f3caa29bb6c171b0a6b
612727: https://sys1.bcfn.ca/block/e5e167c52a9decb313fbaadf49a5e34cb490f8084f642a850385476d4ef10d70
612728: https://sys1.bcfn.ca/block/ab64d989edc71890e7b5b8491c20e9a27520dc45a5f7c776d3dae79057f59fe7
612729: https://sys1.bcfn.ca/block/5e8b7ecd0e36f99d07e4ea6e135fc952bf7ec30164ab6f4d1e98b0f2d405df6d
612730: https://sys1.bcfn.ca/block/d395df3d31dde60bbb0bece6bd5b358297da878f0beb96be389e5f0e043580a3
It is important to note that this POC is not focused on Z-DAG. The performance of Z-DAG has been benchmarked within realistic network conditions: Whiteblock’s audit is publicly available. Network latency tests showed an average TPS around 15k with burst capacity up to 61k. Zero-latency control group exhibited ~150k TPS. Mainnet testing of the Z-DAG network is achievable and will require further coordination and additional resources.
Even further optimizations are expected in the upcoming Syscoin Core release which will implement a UTXO model for our token layer bringing further efficiency as well as open the door to additional scaling technology currently under research by our team and academic partners. At present our token layer is account-based, similar to Ethereum. Opt-in compliance structures will also be introduced soon which will offer some positive performance characteristics as well. It makes the most sense to implement these optimizations before performing another benchmark for Z-DAG, especially on the mainnet considering the resources required to stress-test this network.

Cost Savings

Total cost for these 100k transactions: $0.63 USD
See the live fee comparison for savings estimation between transactions on Ethereum and Syscoin. Below is a snapshot at time of writing:
ETH price: $318.55 ETH gas price: 55.00 Gwei ($0.37)
Syscoin price: $0.11
Snapshot of live fee comparison chart
Z-DAG provides a more efficient fee-market. A typical Z-DAG transaction costs 0.0000582 SYS. Tokens can be safely redeemed/re-spent within seconds or allowed to settle on-chain beforehand. The costs should remain about this low for microtransactions.
Syscoin will achieve further reduction of fees and even greater scalability with offchain payment channels for assets, with Z-DAG as a resilience fallback. New payment channel technology is one of the topics under research by the Syscoin development team with our academic partners at TU Delft. In line with the calculation in the Lightning Networks white paper, payment channels using assets with Syscoin Core will bring theoretical capacity for each person on Earth (7.8 billion) to have five on-chain transactions per year, per person, without requiring anyone to enter a fee market (aka “wait for a block”). This exceeds the minimum LN expectation of two transactions per person, per year; one to exist on-chain and one to settle aggregated value.

Tools, Infrastructure & Documentation

Syscoin Bridge

Mainnet Demonstration of Syscoin Bridge with the Basic Attention Token ERC-20
A two-way blockchain interoperability system that uses Simple Payment Verification to enable:
  • Any Standard ERC-20 token to be moved from Ethereum to the Syscoin blockchain as a Syscoin Platform Token (SPT), and back to Ethereum
  • Any SPT to be moved from Syscoin to the Ethereum blockchain as an ERC-20 token, and back to Syscoin

Benefits

  • Permissionless
  • No counterparties involved
  • No trading mechanisms involved
  • No third-party liquidity providers required
  • Cross-chain Fractional Supply - 2-way peg - Token supply maintained globally
  • ERC-20s gain vastly improved transactionality with the Syscoin Token Platform, along with the security of bitcoin-core-compliant PoW.
  • SPTs gain access to all the tooling, applications and capabilities of Ethereum for ERC-20, including smart contracts.
https://preview.redd.it/l8t2m8ldh8e51.png?width=1180&format=png&auto=webp&s=b0a955a0181746dc79aff718bd0bf607d3c3aa23
https://preview.redd.it/26htnxzfh8e51.png?width=1180&format=png&auto=webp&s=d0383d3c2ee836c9f60b57eca35542e9545f741d

Source code

https://github.com/syscoin/?q=sysethereum
Main Subprojects

API

Tools to simplify using Syscoin Bridge as a service with dapps and wallets will be released some time after implementation of Syscoin Core 4.2. These will be based upon the same processes which are automated in the current live Sysethereum Dapp that is functioning with the Syscoin mainnet.

Documentation

Syscoin Bridge & How it Works (description and process flow)
Superblock Validation Battles
HOWTO: Provision the Bridge for your ERC-20
HOWTO: Setup an Agent
Developer & User Diligence

Trade-off

The Syscoin Ethereum Bridge is secured by Agent nodes participating in a decentralized and incentivized model that involves roles of Superblock challengers and submitters. This model is open to participation. The benefits here are trust-minimization, permissionless-ness, and potentially less legal/regulatory red-tape than interop mechanisms that involve liquidity providers and/or trading mechanisms.
The trade-off is that due to the decentralized nature there are cross-chain settlement times of one hour to cross from Ethereum to Syscoin, and three hours to cross from Syscoin to Ethereum. We are exploring ways to reduce this time while maintaining decentralization via zkp. Even so, an “instant bridge” experience could be provided by means of a third-party liquidity mechanism. That option exists but is not required for bridge functionality today. Typically bridges are used with batch value, not with high frequencies of smaller values, and generally it is advantageous to keep some value on both chains for maximum availability of utility. Even so, the cross-chain settlement time is good to mention here.

Cost

Ethereum -> Syscoin: Matic or Ethereum transaction fee for bridge contract interaction, negligible Syscoin transaction fee for minting tokens
Syscoin -> Ethereum: Negligible Syscoin transaction fee for burning tokens, 0.01% transaction fee paid to Bridge Agent in the form of the ERC-20, Matic or Ethereum transaction fee for contract interaction.

Z-DAG

Zero-Confirmation Directed Acyclic Graph is an instant settlement protocol that is used as a complementary system to proof-of-work (PoW) in the confirmation of Syscoin service transactions. In essence, a Z-DAG is simply a directed acyclic graph (DAG) where validating nodes verify the sequential ordering of transactions that are received in their memory pools. Z-DAG is used by the validating nodes across the network to ensure that there is absolute consensus on the ordering of transactions and no balances are overflowed (no double-spends).

Benefits

  • Unique fee-market that is more efficient for microtransaction redemption and settlement
  • Uses decentralized means to enable tokens with value transfer scalability that is comparable or exceeds that of credit card networks
  • Provides high throughput and secure fulfillment even if blocks are full
  • Probabilistic and interactive
  • 99.9999% security assurance within 10 seconds
  • Can serve payment channels as a resilience fallback that is faster and lower-cost than falling-back directly to a blockchain
  • Each Z-DAG transaction also settles onchain through Syscoin Core at 60-second block target using SHA-256 Proof of Work consensus
https://preview.redd.it/pgbx84jih8e51.png?width=1614&format=png&auto=webp&s=5f631d42a33dc698365eb8dd184b6d442def6640

Source code

https://github.com/syscoin/syscoin

API

Syscoin-js provides tooling for all Syscoin Core RPCs including interactivity with Z-DAG.

Documentation

Z-DAG White Paper
Useful read: An in-depth Z-DAG discussion between Syscoin Core developer Jag Sidhu and Brave Software Research Engineer Gonçalo Pestana

Trade-off

Z-DAG enables the ideal speed/security tradeoff to be determined per use-case in the application layer. It minimizes the sacrifice required to accept and redeem fast transfers/payments while providing more-than-ample security for microtransactions. This is supported on the premise that a Reddit user receiving points does need security yet generally doesn’t want nor need to wait for the same level of security as a nation-state settling an international trade debt. In any case, each Z-DAG transaction settles onchain at a block target of 60 seconds.

Syscoin Specs

Syscoin 3.0 White Paper
(4.0 white paper is pending. For improved scalability and less blockchain bloat, some features of v3 no longer exist in current v4: Specifically Marketplace Offers, Aliases, Escrow, Certificates, Pruning, Encrypted Messaging)
  • 16MB block bandwidth per minute assuming segwit witness carrying transactions, and transactions ~200 bytes on average
  • SHA256 merge mined with Bitcoin
  • UTXO asset layer, with base Syscoin layer sharing identical security policies as Bitcoin Core
  • Z-DAG on asset layer, bridge to Ethereum on asset layer
  • On-chain scaling with prospect of enabling enterprise grade reliable trustless payment processing with on/offchain hybrid solution
  • Focus only on Simple Value Transfers. MVP of blockchain consensus footprint is balances and ownership of them. Everything else can reduce data availability in exchange for scale (Ethereum 2.0 model). We leave that to other designs, we focus on transfers.
  • Future integrations of MAST/Taproot to get more complex value transfers without trading off trustlessness or decentralization.
  • Zero-knowledge Proofs are a cryptographic new frontier. We are dabbling here to generalize the concept of bridging and also verify the state of a chain efficiently. We also apply it in our Digital Identity projects at Blockchain Foundry (a publicly traded company which develops Syscoin softwares for clients). We are also looking to integrate privacy preserving payment channels for off-chain payments through zkSNARK hub & spoke design which does not suffer from the HTLC attack vectors evident on LN. Much of the issues plaguing Lightning Network can be resolved using a zkSNARK design whilst also providing the ability to do a multi-asset payment channel system. Currently we found a showstopper attack (American Call Option) on LN if we were to use multiple-assets. This would not exist in a system such as this.

Wallets

Web3 and mobile wallets are under active development by Blockchain Foundry Inc as WebAssembly applications and expected for release not long after mainnet deployment of Syscoin Core 4.2. Both of these will be multi-coin wallets that support Syscoin, SPTs, Ethereum, and ERC-20 tokens. The Web3 wallet will provide functionality similar to Metamask.
Syscoin Platform and tokens are already integrated with Blockbook. Custom hardware wallet support currently exists via ElectrumSys. First-class HW wallet integration through apps such as Ledger Live will exist after 4.2.
Current supported wallets
Syscoin Spark Desktop
Syscoin-Qt

Explorers

Mainnet: https://sys1.bcfn.ca (Blockbook)
Testnet: https://explorer-testnet.blockchainfoundry.co

Thank you for close consideration of our proposal. We look forward to feedback, and to working with the Reddit community to implement an ideal solution using Syscoin Platform!

submitted by sidhujag to ethereum [link] [comments]

Reddcoin (RDD) 02/20 Progress Report - Core Wallet v3.1 Evolution & PoSV v2 - Commits & More Commits to v3.1! (Bitcoin Core 0.10, MacOS Catalina, QT Enhanced Speed and Security and more!)

Reddcoin (RDD) Core Dev Team Informal Progress Report, Feb 2020 - As any blockchain or software expert will confirm, the hardest part of making successful progress in blockchain and crypto is invisible to most users. As developers, the Reddcoin Core team relies on internal experts like John Nash, contributors offering their own code improvements to our repos (which we would love to see more of!) and especially upstream commits from experts working on open source projects like Bitcoin itself. We'd like tothank each and everyone who's hard work has contributed to this progress.
As part of Reddcoin's evolution, and in order to include required security fixes, speed improvements that are long overdue, the team has up to this point incorporated the following code commits since our last v3.0.1 public release. In attempting to solve the relatively minor font display issue with MacOS Catalina, we uncovered a complicated interweaving of updates between Reddcoin Core, QT software, MacOS SDK, Bitcoin Core and related libraries and dependencies that mandated we take a holistic approach to both solve the Catalina display problem, but in doing so, prepare a more streamlined overall build and test system, allowing the team to roll out more frequent and more secure updates in the future. And also to include some badly needed fixes in the current version of Core, which we have tentatively labeled Reddcoin Core Wallet v3.1.
Note: As indicated below, v3.1 is NOT YET AVAILABLE FOR DOWNLOAD BY PUBLIC. We wil advise when it is.
The new v3.1 version should be ready for internal QA and build testing by the end of this week, with luck, and will be turned over to the public shortly thereafter once testing has proven no unexpected issues have been introduced. We know the delay has been a bit extended for our ReddHead MacOS Catalina stakers, and we hope to have them all aboard soon. We have moved with all possible speed while attempting to incorproate all the required work, testing, and ensuring security and safety for our ReddHeads.
Which leads us to: PoSV v2 activation and the supermajority on Mainnet at the time of this writing has reached 5625/9000 blocks or 62.5%. We have progressed quite well and without any reported user issues since release, but we need all of the community to participate! This activation, much like the funding mechanisms currently being debated by BCH and others, and employed by DASH, will mean not only a catalyst for Reddcoin but ensure it's future by providing funding for the dev team. As a personal plea from the team, please help us support the PoSV v2 activation by staking your RDD, no matter how large or small your amount of stake.
Every block and every RDD counts, and if you don't know how, we'll teach you! Live chat is fun as well as providing tech support you can trust from devs and community ReddHead members. Join us today in staking and online and collect some RDD "rain" from users and devs alike!
If you're holding Reddcoin and not staking, or you haven't upgraded your v2.x wallet to v3.0.1 (current release), we need you to help achieve consensus and activate PoSV v2! For details, see the pinned message here or our website or medium channel. Upgrade is simple and takes moments; if you're nervous or unsure, we're here to help live in Telegram or Discord, as well as other chat programs. See our website for links.
Look for more updates shortly as our long-anticipated Reddcoin Payment Gateway and Merchant Services API come online with point-of-sale support, as we announce the cross-crypto-project Aussie firefighter fundraiser program, as well as a comprehensive update to our development roadmap and more.
Work has restarted on ReddID and multiple initiatives are underway to begin educating and sharing information about ReddID, what it is, and how to use it, as we approach a releasable ReddID product. We enthusiastically encourage anyone interested in working to bring these efforts to life, whether writers, UX/UI experts, big data analysts, graphic artists, coders, front-end, back-end, AI, DevOps, the Reddcoin Core dev team is growing, and there's more opportunity and work than ever!
Bring your talents to a community and dev team that truly appreciates it, and share the Reddcoin Love!
And now, lots of commits. As v3.1 is not yet quite ready for public release, these commits have not been pushed publicly, but in the interests of sharing progress transparently, and including our ReddHead community in the process, see below for mind-numbing technical detail of work accomplished.
e5c143404 - - 2014-08-07 - Ross Nicoll - Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope. *99a7dba2e - - 2014-08-15 - Cory Fields - tests: fix test-runner for osx. Closes ##4708 *8c667f1be - - 2014-08-15 - Cory Fields - build: add funcs.mk to the list of meta-depends *bcc1b2b2f - - 2014-08-15 - Cory Fields - depends: fix shasum on osx < 10.9 *54dac77d1 - - 2014-08-18 - Cory Fields - build: add option for reducing exports (v2) *6fb9611c0 - - 2014-08-16 - randy-waterhouse - build : fix CPPFLAGS for libbitcoin_cli *9958cc923 - - 2014-08-16 - randy-waterhouse - build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix. *342aa98ea - - 2014-08-07 - Cory Fields - build: fix automake warnings about the use of INCLUDES *46db8ad51 - - 2020-02-18 - John Nash - build: add build.h to the correct target *a24de1e4c - - 2014-11-26 - Pavel Janík - Use complete path to include bitcoin-config.h. *fd8f506e5 - - 2014-08-04 - Wladimir J. van der Laan - qt: Demote ReportInvalidCertificate message to qDebug *f12aaf3b1 - - 2020-02-17 - John Nash - build: QT5 compiled with fPIC require fPIC to be enabled, fPIE is not enough *7a991b37e - - 2014-08-12 - Wladimir J. van der Laan - build: check for sys/prctl.h in the proper way *2cfa63a48 - - 2014-08-11 - Wladimir J. van der Laan - build: Add mention of --disable-wallet to bdb48 error messages *9aa580f04 - - 2014-07-23 - Cory Fields - depends: add shared dependency builder *8853d4645 - - 2014-08-08 - Philip Kaufmann - [Qt] move SubstituteFonts() above ToolTipToRichTextFilter *0c98e21db - - 2014-08-02 - Ross Nicoll - URLs containing a / after the address no longer cause parsing errors. *7baa77731 - - 2014-08-07 - ntrgn - Fixes ignored qt 4.8 codecs path on windows when configuring with --with-qt-libdir *2a3df4617 - - 2014-08-06 - Cory Fields - qt: fix unicode character display on osx when building with 10.7 sdk *71a36303d - - 2014-08-04 - Cory Fields - build: fix race in 'make deploy' for windows *077295498 - - 2014-08-04 - Cory Fields - build: Fix 'make deploy' when binaries haven't been built yet *ffdcc4d7d - - 2014-08-04 - Cory Fields - build: hook up qt translations for static osx packaging *25a7e9c90 - - 2014-08-04 - Cory Fields - build: add --with-qt-translationdir to configure for use with static qt *11cfcef37 - - 2014-08-04 - Cory Fields - build: teach macdeploy the -translations-dir argument, for use with static qt *4c4ae35b1 - - 2014-07-23 - Cory Fields - build: Find the proper xcb/pcre dependencies *942e77dd2 - - 2014-08-06 - Cory Fields - build: silence mingw fpic warning spew *e73e2b834 - - 2014-06-27 - Huang Le - Use async name resolving to improve net thread responsiveness *c88e76e8e - - 2014-07-23 - Cory Fields - build: don't let libtool insert rpath into binaries *18e14e11c - - 2014-08-05 - ntrgn - build: Fix windows configure when using --with-qt-libdir *bb92d65c4 - - 2014-07-31 - Cory Fields - test: don't let the port number exceed the legal range *62b95290a - - 2014-06-18 - Cory Fields - test: redirect comparison tool output to stdout *cefe447e9 - - 2014-07-22 - Cory Fields - gitian: remove unneeded option after last commit *9347402ca - - 2014-07-21 - Cory Fields - build: fix broken boost chrono check on some platforms *c9ed039cf - - 2014-06-03 - Cory Fields - build: fix whitespace in pkg-config variable *3bcc5ad37 - - 2014-06-03 - Cory Fields - build: allow linux and osx to build against static qt5 *01a44ba90 - - 2014-07-17 - Cory Fields - build: silence false errors during make clean *d1fbf7ba2 - - 2014-07-08 - Cory Fields - build: fix win32 static linking after libtool merge *005ae2fa4 - - 2014-07-08 - Cory Fields - build: re-add AM_LDFLAGS where it's overridden *37043076d - - 2014-07-02 - Wladimir J. van der Laan - Fix the Qt5 build after d95ba75 *f3b4bbf40 - - 2014-07-01 - Wladimir J. van der Laan - qt: Change serious messages from qDebug to qWarning *f4706f753 - - 2014-07-01 - Wladimir J. van der Laan - qt: Log messages with type>QtDebugMsg as non-debug *98e85fa1f - - 2014-06-06 - Pieter Wuille - libsecp256k1 integration *5f1f2e226 - - 2020-02-17 - John Nash - Merge branch 'switch_verification_code' into Build *1f30416c9 - - 2014-02-07 - Pieter Wuille - Also switch the (unused) verification code to low-s instead of even-s. *1c093d55e - - 2014-06-06 - Cory Fields - secp256k1: Add build-side changes for libsecp256k1 *7f3114484 - - 2014-06-06 - Cory Fields - secp256k1: add libtool as a dependency *2531f9299 - - 2020-02-17 - John Nash - Move network-time related functions to timedata.cpp/h *d003e4c57 - - 2020-02-16 - John Nash - build: fix build weirdness after 54372482. *7035f5034 - - 2020-02-16 - John Nash - Add ::OUTPUT_SIZE *2a864c4d8 - - 2014-06-09 - Cory Fields - crypto: create a separate lib for crypto functions *03a4e4c70 - - 2014-06-09 - Cory Fields - crypto: explicitly check for byte read/write functions *a78462a2a - - 2014-06-09 - Cory Fields - build: move bitcoin-config.h to its own directory *a885721c4 - - 2014-05-31 - Pieter Wuille - Extend and move all crypto tests to crypto_tests.cpp *5f308f528 - - 2014-05-03 - Pieter Wuille - Move {Read,Write}{LE,BE}{32,64} to common.h and use builtins if possible *0161cc426 - - 2014-05-01 - Pieter Wuille - Add built-in RIPEMD-160 implementation *deefc27c0 - - 2014-04-28 - Pieter Wuille - Move crypto implementations to src/crypto/ *d6a12182b - - 2014-04-28 - Pieter Wuille - Add built-in SHA-1 implementation. *c3c4f9f2e - - 2014-04-27 - Pieter Wuille - Switch miner.cpp to use sha2 instead of OpenSSL. *b6ed6def9 - - 2014-04-28 - Pieter Wuille - Remove getwork() RPC call *0a09c1c60 - - 2014-04-26 - Pieter Wuille - Switch script.cpp and hash.cpp to use sha2.cpp instead of OpenSSL. *8ed091692 - - 2014-04-20 - Pieter Wuille - Add a built-in SHA256/SHA512 implementation. *0c4c99b3f - - 2014-06-21 - Philip Kaufmann - small cleanup in src/compat .h and .cpp *ab1369745 - - 2014-06-13 - Cory Fields - sanity: hook up sanity checks *f598c67e0 - - 2014-06-13 - Cory Fields - sanity: add libc/stdlib sanity checks *b241b3e13 - - 2014-06-13 - Cory Fields - sanity: autoconf check for sys/select.h *cad980a4f - - 2019-07-03 - John Nash - build: Add a top-level forwarding target for src/ objects *f4533ee1c - - 2019-07-03 - John Nash - build: qt: split locale resources. Fixes non-deterministic distcheck *4a0e46e76 - - 2019-06-29 - John Nash - build: fix version dependency *2f61699d9 - - 2019-06-29 - John Nash - build: quit abusing AMCPPFLAGS *99b60ba49 - - 2019-06-29 - John Nash - build: avoid the use of top and abs_ dir paths *c8f673d5d - - 2019-06-29 - John Nash - build: Tidy up file generation output *5318bce57 - - 2019-06-29 - John Nash - build: nuke Makefile.include from orbit *672a25349 - - 2019-06-29 - John Nash - build: add stub makefiles for easier subdir builds *562b7c5a6 - - 2020-02-08 - John Nash - build: delete old Makefile.am's *066120079 - - 2020-02-08 - John Nash - build: Switch to non-recursive make
Whew! No wonder it's taken the dev team a while! :)
TL;DR: Trying to fix MacOS Catalina font display led to requiring all kinds of work to migrate and evolve the Reddcoin Core software with Apple, Bitcoin and QT components. Lots of work done, v3.1 public release soon. Also other exciting things and ReddID back under active dev effort.
submitted by TechAdept to reddCoin [link] [comments]

Groestlcoin 6th Anniversary Release

Introduction

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.

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

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here

Source

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.

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

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.

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

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.

Features

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

ALL NEW! – Vanity Search Vanity Address Generator

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).

Features

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

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).

Features

Download

Source

Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

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.

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.

Features

Download

Windows
Linux :
 pip3 install -r requirements.txt python3 bip39\_gui.py 

Source

ALL NEW! – Electrum Personal Server

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.

Features

Download

Windows
Linux / OSX (Instructions)

Source

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.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

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.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

BITCORE BTX [ANN v2.0]

BITCORE BTX [ANN v2.0]
https://preview.redd.it/uv18v1yaxhe11.jpg?width=1440&format=pjpg&auto=webp&s=a32ca263d2dbe5510e678f4c3c645d1f7e2f3b59
Coin Specification Segwit with Core 0.15.1.0 PoW Algo Wallets
- BitCore BTX- Core 0.15.0.2- 21 Million Coin- 2,5 min- DefaultPort = 8555 - RPC Port 40332- Segwit and Bloom- 20 MB Blocksize (10 MB + 10 MB Segwit)_- Algo Timetravel10- Diff Retarget: Bitcore 64_15 The Segwit opens up new possibilities like the Lightning Network,Tumblebit, Schnorr Signatures,_Confidential Transactions, Cross-chain atomic swaps, and so on.We are alreadyexploring all these new functions, and testing the water.We expect the first implementations as fast as possible. “TimeTravel10”, that actually bases on 40320 different combinations of hashing algorithms and that easily can be extended_to 362880, 3628800 or even more,lets miners travel through time throughthem or through them through time. Source: Github Release Download: Releases Mobile Wallet: Coinomi / Android / iOS Electrum Wallet Electrem Third party wallets Zeltrez / Jaxx Liberty < NEW
https://preview.redd.it/pw88xkmpyhe11.jpg?width=1440&format=pjpg&auto=webp&s=67d08cb8f738866e7d8a78964d096fcbd5dc22bc
Discover our roadmap here
https://i.redd.it/eghvz61yyhe11.gif
https://preview.redd.it/c4pwm9s0zhe11.jpg?width=1440&format=pjpg&auto=webp&s=57d8756540c1d8bd2c0c9ad801ce84b703780d4f
Bit-Z BTX/BTC Cryptopia BTX/ BTC USDT NZDT LTC DOGE HitBTC BTX/BTC VE Bitcoin BTX/BTC
https://preview.redd.it/45tdng85zhe11.jpg?width=1440&format=pjpg&auto=webp&s=cda69b8bb27aebf0ec1f88bd897a81bb8de11f74
Exrates BTX/ USD EUR BTC ETH Crypto-Bridge BTX/BTC QBTC BTX/CNTY CoinExchange BTX/BTC
https://preview.redd.it/kqab5a36zhe11.jpg?width=1440&format=pjpg&auto=webp&s=35a2f4535ad1eec0fd60b5b258dc646b2f34bec3
Ocatex BTX/BTC Bitexlive BTX/ USD EUR BTC Bitibu BTX/BTC Trade Satoshi BTX/BTC
https://preview.redd.it/1eb95r08zhe11.jpg?width=1440&format=pjpg&auto=webp&s=375e596f41744a8142bcc0d12b8f1d9fdfd1e1d9
PayCml BTX/LYRA Crex24 BTX/BTC Excoincial SOON > BTX/BTC ...
https://preview.redd.it/al254pcx0ie11.jpg?width=1440&format=pjpg&auto=webp&s=30412c82c128e6a96fe68a07b40142362dda33dc
Go to Livingroom of Satoshi Go to Kamoney Go to Cryptonaut Go to EasyRabBit Go to LucckyGames
https://preview.redd.it/ohap3qhb1ie11.jpg?width=1440&format=pjpg&auto=webp&s=eed1c63f80a83f892ed440f8b67dab24c9d73a3c
Go to CryptoID Go to InsightAPI Go to Livenet
https://preview.redd.it/jwy48q5k1ie11.jpg?width=1440&format=pjpg&auto=webp&s=7ade73d514597465d2d62055842ec7cdce9ef9c6
Go to CryptoCompare Go to WorldCoinIndex Go to CoinMarketCap
https://preview.redd.it/7rd3gfow1ie11.jpg?width=1440&format=pjpg&auto=webp&s=9d73ff816499d41b545dbaec74f26bf32e32fc1f
Bitcorepool Omegapool Suprnova Chainworks
https://preview.redd.it/uditpyyz1ie11.jpg?width=1440&format=pjpg&auto=webp&s=bee3aa36f3aff473a84e683709bd650123cfb175
Antminepool Coin-miners BSOD Umine
https://preview.redd.it/doqwb0212ie11.jpg?width=1440&format=pjpg&auto=webp&s=dfff42d64e4f1244aeca369ba5258f69d2442b45
Poolgpu Yiimp BTXpool Minersport
https://preview.redd.it/1j7vghsv2ie11.jpg?width=1440&format=pjpg&auto=webp&s=2735b983853a727b382b865cd2c6b93da29ba7d4
Cointelegraph Bitcore a lightning fast solution to the scaling debate Read
CCN Bitcore winning scaling race earth shattering speed Read
BTC Echo Muss es immer ein Hardfork sein? Nein! – Bitcore (BTX) legt seit April vor Read
Steemit Bitcore BTX Guide: the 2nd snapshot for BTC HODLers - free BTX | how it works Read
Steemit Making blockchain history: Bitcore (BTX) is currently writing blocks with over 3000 kB of data! Read
BTCmanager.com Why is the Cryptocurrency Community Ignoring Bitcore? Read
Bitcore Bitcoin Core Developer Jimmy Song about Bitcore “the most clever fork” Read
Cryptonaut Bitcore is one of the first known cryptocurrencies to use the hybrid fork method to distribute BTX Read
Soft2share Cryptocurrency was what made an entry into the financial sector to address the concerns raised by the centralized infrastructure. Read
https://preview.redd.it/9oc876384ie11.jpg?width=1440&format=pjpg&auto=webp&s=33f5957bef004cb7abb65e9e9df87dda5e402bd0
Bitcore BTX - Twitter Official Bitcore BTX - Telegram Official Telegram German Telegram Spanish Telegram Italian Telegram Italian Telegram Russian Telegram Ukraine Telegram Bahasa Telegram Philipine Telegram Romania
..
Bitcore on Youtube Bitcore on Discord Facebook Fanpage / Group

QQ Groupno. 680492670 Go to Chat on Crypto Go to Line @Bitcore.btx / @Bitcore_official
https://preview.redd.it/vusyttoe7ie11.jpg?width=1440&format=pjpg&auto=webp&s=fcd73ad87db51932d57f76bcae5bbda67898d353
How to sign a message? How to type your sign message from wallet in the registration form? Read BTX Mining Manual A manual for those who struggles setting up mining BTX. Read
https://preview.redd.it/faytk6716ie11.jpg?width=1095&format=pjpg&auto=webp&s=082127977aaad2ec02e686c87281fa4e63552f91
Bitcore Snapshot The premine address is 13hwgY4YUvrgnhjLP5ugFafL1cmbRRtr5ePRE ANN was 23.04.2017Download Snapshot...here (140 MB)Mediafiles and CI Download files here Press kit Basic | Press kit Full
https://preview.redd.it/r4txod466ie11.jpg?width=1440&format=pjpg&auto=webp&s=eb57e83e2291572c9f3731717b9f7f261430ee76
Chris Jon Steve David
System, Service Administrator & All-Round Talent Core Developer Brand Ambassador & Social Media Publications & Graphic Design
Chris is Bitcore’s main developer. He has worked on several other coins like BitSend, Bitcloud and more.Founder from Limxtec Jon is the API, Electrum and infrastructure developer for Bitcore. He supervises the contact to exchanges, listing sites and more. David is the artistic mind behind Bitcore. He is also working on media publications and supports the core team’s workflow.
Ivo Thomas Greg (GM) DgCarlosLeon
Web Development & Project Consultant Exchange Manager Mining Expert Support and Graphic Design
Ivo is working on the website as well as helping Bitcore grow both legally and technically. Thomas is our email and exchange manager responsible for most of our official communication with services and exchange platforms. Mining pool admin and mining support via telegram channel. Carlos is Bitcore Reddit communicator and graphic supporter.
Fahim Altinordu Brad Eric Hampus
Supporter Supporter Telegram and Facebook Support Supporter
Turkish and international exchange management. Brad is Bitcore’s Facebook manager. Hampuz is organizing signature campaigns and manages our threads on a lot of altcoin forums.
Klaas Ibrahim Acir Ugur Jose Martin
Supporter Developer Team (Turkey) Supporter Spanish Community Manager
Telegram and altcoin forum support. Ugur is managing Bitcore’s Turkish community and helps with telegram support work.
https://preview.redd.it/mb06uk2e7ie11.jpg?width=1440&format=pjpg&auto=webp&s=8135a85c34e26bb222ca8e871dc53e0129ef2800
DISCLAIMER | The Bitcore BTX (ANN REDDIT) cannot take responsibility for third party providers, such as the listed exchanges, wallets, sites and pools. All links hosted on our domain are by community members and third parties and by clicking on any of the listed links you are accepting the risks of using the third party domain and taking responsibility for any losses, damage or other issues using said domain. Crypto-currencies are inherently risky and investors and users must remain vigilant.
Web: Official | News | Coin Specs | Roadmap | White Paper | Ecosystem | Network Update | Community | FAQ | Blog | Team Wallets: Windows | Win Wallet & Blockchain | Linux | Mac | iOS | Android | Eletrum | Zeltrez | Jaxx Liberty Exchanges: Bit Z | Cryptopia | hitBTC | VE Bitcoin | Exrates | Crypto Bridge | QBTC | Coinexchange | Octaex | Bitexlive | Bitibu | Trade Satoshi | PayCML Services: Livingroom of Satoshi | Kamoney | Cryptonaut | EasyRabBit.net | LuckyGames.io Block Explorers: InsightAPI | Crypto ID | Liivenet Mining Pools: Bitcorepool | Yiimp | Suprnova | Chainworks | Umine | Ant Mine Pool | Coin Miners | BSOD | BTXpool | Minersport | Omegapool | PoolGPU Market Info: CoinMarketCap | World Coin Index | Cryptocompare Source: Github | Kryptowerk | DgCarlosLeon _____________________________________________________________________________
ANN Designed by DgCarlosLeon | Bitcore BTX - 2018
submitted by dgcarlosleon to bitcore_btx [link] [comments]

Gridcoin Research 3.7.12.0 Released

The Gridcoin Developers are pleased to unveil 3.7.12 to you today, which is a massive release featuring over 450 commits over the last couple months. While being a large update it is still leisure, and users do not have to update.
Download the update from GitHub here.
The Windows MSI can be downloaded here.
 
Rather than posting the full release notes (because that would be ridiculous given the number of changes), I will instead showcase some of the more prominent and exciting features in this release. If you would like the full unedited changelog please see the Github commit list here.
 
New changes in this release include:

Gridcoin Research is now a 64 bit installation

New UI

NewUI

RPC Overhaul

New AutoTools Build System

Neural Network Enhancements

 
These are far from all the changes, but these five are the ones we would like to specifically showcase for the average wallet user. We hope you will be happy with the new release and look forward to your feedback.
 
As always, thank you to all the developers who contributed to this release, including but not limited to: @ravonn, @ifoggz, @tomasbrod, @thecharlatan, and @jamescowens.
 
I would also like to thank all our dedicated testnet users who helped to find bugs and issues to ensure a smooth release. Special thanks to @noah-blaker, @jamescowens (again!), and @GlenArm for going the extra mile to assist debugging tricky last minute issues.
submitted by barton26 to gridcoin [link] [comments]

Gridcoin Leisure Update 3.7.14.0 Released

Today we have a new leisure update for you. This version includes a lot of "under the hood" changes, but there are some improvements for the average user as well.
 
Notably this release includes a better time to stake calculation method, thanks to @jamescowens. Also the Neural Network runs much smoother thanks to many optimizations by @ifoggz.
 
Download the update from GitHub here.
The Windows MSI can be downloaded here.
 
Full Release Notes:
Added
 
Changed
 
Fixed
 
Removed
 
Thank you to all the developers who contributed to this release. I will update this post when the Windows MSI has been uploaded to the website.
submitted by barton26 to gridcoin [link] [comments]

Dogecoin 1.5.1 Released - Upgrade Now!

We’re happy to announce the release of Dogecoin version 1.5.1!
This release incorporates a range of updates from community contributors, some much needed bug fixes, plus some cool treats brought down-stream from the recent Bitcoin 0.9 release candidate.
Thanks to everyone who helped make this release possible, the entire community appreciates it. We recommend all users update to the latest version and please report any issues you may encounter. As always, backup your wallet.dat file before updating (just to be safe).
Downloads: Windows Installer Windows Archive Mac OS X App
Release highlights: - Switched to Boost 1.55 to fix network connectivity issues on Windows - Removal of reliance on IRC for discovering nodes - Support for URL protocol, eg. dogecoin:addr?amount=xxx&(see Bitcoin’s implementation) - Ability to automatically look up transactions on Dogechain from your client - Working Windows setup script and installer - Opt-in debug logging via -debuglog (to save disk space and stop constant writing) - Fixed Mac Splashscreen’s greedy desktop behavior - Reimplemented testnet, fixing RPC crash due to no genesis block being present - Allow user to load any wallet from data directory specified using -wallet=mywallet.dat - Updated to LevelDB 1.15 to address blockchain database corruption issues - Allow user to send change only to specified address(es) using -change= (one -change parameter per address) - Fixed RPC difficulty look up
Troubleshooting
If anyone experiences issues, delete all 1.4 data (apart from your backed up wallet.dat file) and do a fresh 1.5.1 install.
Enjoy!
submitted by Laika1954 to dogecoin [link] [comments]

Transcript of Developer Meeting in Discord - March 29, 2019

Pho3nix Monk3y03/29/2019
Is this unlocked?
oh cool. yes it is
Guess we need an admin to unlock it. Some of our devs cant type in here yet.
@shiggidy @traysi ★★★★★ Can yall unlock this channel?
traysi ★★★★★03/29/2019
Should be open now
bhorn03/29/2019
open!
GhostDogsGhost03/29/2019
heya!
SamzOnline [w1ne]03/29/2019
Woot
theking03/29/2019
Glad to be here.
traysi ★★★★★03/29/2019
@Jeroz can you type now?
Jeroz03/29/2019
Works now
ty
Pho3nix Monk3y03/29/2019
Great. Didn't really have an agenda for this meeting I'm told. Can open it up? Anyone have anything to start?
Bianca_NL03/29/2019
YaY
GhostDogsGhost03/29/2019
testnet voting on messaging bip?
Pho3nix Monk3y03/29/2019
I like it.
@GhostDogsGhost You might be the main "answerer of questions" for this. Not sure where @[Dev-Happy] Blondfrogs is.
GhostDogsGhost03/29/2019
anyone know if it's passed? if and when it'd be great to get some usage
Vincent03/29/2019
all good @traysi ★★★★★
Jeroz03/29/2019
Messaging is active on testnet now. The vote passed.
traysi ★★★★★03/29/2019
I'll try to clean up the permissions for this channel to make it simpler for future meetings.
Jeroz03/29/2019
There is no GUI yet to test it.
GhostDogsGhost03/29/2019
sweet -- yeah just rpc for now
[Dev-Happy] Blondfrogs03/29/2019
here
Pho3nix Monk3y03/29/2019
yay
[Dev-Happy] Blondfrogs03/29/2019
So, for messaging. There is not GUI, we really want to test the protocol which you can use fully through the rpc console.
We understand that this limits the number of users that will want to do testing but we wanted to get it out there asap to find bugs
Jeroz03/29/2019
Is there list of commands / little guide on how to get started with them in the console?
[Dev-Happy] Blondfrogs03/29/2019
Also, we wanted to let everyone know that we are going to try and get messaging protocol and restricted assets on mainnet at the same time. This means that the release for messaging might be delayed by a couple weeks. The devs are working really hard to make this happen and hope that the community is willing to wait a little longer for mainnet messaging.
There are commands like sendmessage listmessages and subscribe rpc calls yes
Jeroz03/29/2019
That would mean 1 hardfork instead of 2 right?
[Dev-Happy] Blondfrogs03/29/2019
Exactly @Jeroz
[Master] Roshii03/29/2019
Hello!
[Dev-Happy] Blondfrogs03/29/2019
Also, the Qt for messaging wont be released until after the hardfork, but the Qt for messaging and restricted assets would be in the same release.
S1LVA | GetRavencoin.org03/29/2019
Hello! Thanks for holding this meeting.
Jeroz03/29/2019
Will dividends also be included to that? @WhaleStreet (BW) (not sure if you are here)
[Dev-Happy] Blondfrogs03/29/2019
Dividends can be released at anytime it is completed as it doesn't require a hardfork
Jeroz03/29/2019
I meant the GUI update
S1LVA | GetRavencoin.org03/29/2019
For restricted assets, will owners of !uniquename have a grace period to claim $uniquename ?
[Dev-Happy] Blondfrogs03/29/2019
I am not sure on the GUI for dividends.
We are still figuring out if we are going to allow for a grave period or not. I think we are leading to the answer of Yes there will be a grace period.
but we aren't sure yet
SamzOnline [w1ne]03/29/2019
I've been studying and out of the loop of the RVN scene for a long time - is there any chance of someone updating me on what y'all talking about?
Pho3nix Monk3y03/29/2019
We have also been going through and cleaning up issues in GitHub. Tried to clean up tags in there as well. We will probably start going though those on a weekly ->monthly basis to stay ahead of things.
Vincent03/29/2019
community seens to agree !ASSET has exclsuvie on $ASSET
GhostDogsGhost03/29/2019
Silva -- that's open for discussion -- I think the general sentiment is that there should be some preference given to current asset owners
[Dev-Happy] Blondfrogs03/29/2019
@SamzOnline [w1ne] We are talking about the roadmap and how the development of the new features are coming along.
SamzOnline [w1ne]03/29/2019
Lovely many thanks
Vincent03/29/2019
what is the justification on only a grace period?
S1LVA | GetRavencoin.org03/29/2019
Is it possible to reissue a !ownership as a $ownership?
Jeroz03/29/2019
@SamzOnline [w1ne]
https://medium.com/@tronblack/ravencoin-tags-and-restricted-assets-84fe3070a226
https://medium.com/@tronblack/ravencoin-kaaawww-2f72077aece
[Dev-Happy] Blondfrogs03/29/2019
@Vincent I don't think is has exclusive rights. More like a first right of refusal for a couple months
Synicide03/29/2019
agree there should be some kind of grace period, or users that originally registered those assets will feel shafted
Vincent03/29/2019
but what is that justification?
if you are building Applein ur garage, you may need a few yrs to go public
S1LVA | GetRavencoin.org03/29/2019
Issue being assets will cease to be unique with two different types about
[Dev-Happy] Blondfrogs03/29/2019
True.
We aren't sure on what approach will be taken yet
Synicide03/29/2019
should regular and restricted assets share the same 'uniqueness of naming'?
[Dev-Happy] Blondfrogs03/29/2019
Please the community let us know what you think is fair.
This topic will 100% need to be discussed a lot
Vincent03/29/2019
when it was announced, there was a lot of discussion; most seemed to agree
SamzOnline [w1ne]03/29/2019
@Jeroz Many thanks
[Dev-Happy] Blondfrogs03/29/2019
If the consensus is that we shouldn't allow for ASSET! and $ASSET to be issued by different people then we will need to make sure that is the right approach. The code hasn't been written yet.
GhostDogsGhost03/29/2019
Some of this will depend on what we end up pricing the $ASSETS at (burn for issuance)..
Vincent03/29/2019
prcing shouldnt matter imo
S1LVA | GetRavencoin.org03/29/2019
We need to determine how important unique asset names are, for varying types.
Vincent03/29/2019
should be the owner of the asset name
[Dev-Happy] Blondfrogs03/29/2019
@S1LVA | GetRavencoin.org Exactly
push | ravenland.org03/29/2019
hey all, sorry im late :thumbsup:
[Dev-Happy] Blondfrogs03/29/2019
Howdy
Synicide03/29/2019
If someone registers !company123, and starts building a platform for themselves, seems they should be given an option to convert to $company123, and shouldnt have to worry about another party creating $company123
[Dev-Happy] Blondfrogs03/29/2019
They will be given that option
Vincent03/29/2019
indefinately
[Dev-Happy] Blondfrogs03/29/2019
the question is, is that option going to exist for forever, or maybe only 4 months
Vincent03/29/2019
then the worry still exists
Rikki RATTOE Sr. SEC Impresantor03/29/2019
I definitely vote for ! And $ to only be issued by the same people
Synicide03/29/2019
lets say they choose not to, can someone else create $company123? Or is that unqiue name shared?
S1LVA | GetRavencoin.org03/29/2019
I believe, ideally, a reissuance option would be available at anytime from !ownership
[Dev-Happy] Blondfrogs03/29/2019
@Synicide That decision hasn't been made yet
theking03/29/2019
@[Dev-Happy] Blondfrogs I do agree that releasing both messaging and restricted assets at same time makes sense so there is only one hard fork. What is the current thinking on tentative timeline before they would both be on main net?
push | ravenland.org03/29/2019
im excited about this memo indication, its useful because it means a buyer of an asset sending rvn can indicate the 'return address' without the 'seller of the asset receiving ravencoin' having to transverse the full vin/vout chain to obtain the source address to dispatch asset to. Is there a timeline for this feature or any documentation on it @[Dev-Happy] Blondfrogs ?
Synicide03/29/2019
my 2 cents, they should be a shared pool of unique names. The door is opened for scammers galore if it isnt.
[Dev-Happy] Blondfrogs03/29/2019
@theking A couple months atleast.
To make sure it is tested on testnet for long enough
theking03/29/2019
That makes perfect sense!
[Dev-Happy] Blondfrogs03/29/2019
@push | ravenland.org It will be on mainnet as soon as it and restricted assets are tested. Is the goal
push | ravenland.org03/29/2019
excellent, i look forward to it
Chill03/29/2019
Thank you for taking the time to bring up the ! and $ ownership issue. It's of extreme importance imo
push | ravenland.org03/29/2019
its gods work your doing there
bitnaive03/29/2019
yeah it seems like any modifiers to the original !NAME should belong to !NAME
DirkDiggler (RVN ded)03/29/2019
I would like to voice concern over the idea of the "grace period".... The idea of a UNIQUE asset name is key to our success. Many of us jumped on names we wanted. This doesn't feel right to need to have yet another name floating around if it's not controlled by the !OWNERSHIP token
S1LVA | GetRavencoin.org03/29/2019
@Chill NP :p
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Yes please on only 1 hard fork
Chill03/29/2019
unique is unique. I have 510 of them!
Synicide03/29/2019
@DirkDiggler (RVN ded) grace peroid wont matter if the naming pool is shared for uniqueness
[Dev-Happy] Blondfrogs03/29/2019
So, If I own GOOGLE!, and I don't want $GOOGLE, no one should be allowed to own it?
DirkDiggler (RVN ded)03/29/2019
exactly
S1LVA | GetRavencoin.org03/29/2019
@[Dev-Happy] Blondfrogs Ideally, yes
bhorn03/29/2019
that feels right to me
Jeroz03/29/2019
yes
SamzOnline [w1ne]03/29/2019
Interesting
DirkDiggler (RVN ded)03/29/2019
yes
Rikki RATTOE Sr. SEC Impresantor03/29/2019
@[Dev-Happy] Blondfrogs I'm good w that
Synicide03/29/2019
that makes the most sense to me. As said, opens the door to scammers if not
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Would add extra value to the ownership token as well
S1LVA | GetRavencoin.org03/29/2019
If more power is given to !ownership(changing type), more value is added to said asset, by way of design and ability
Vincent03/29/2019
and if you want to covert your assets to restricted yrs from now you will have a logistic nightmare if you have a bunch of owners
[Dev-Happy] Blondfrogs03/29/2019
I feel like, if we give people the option to register the restricted asset $ and they don't want it, that it is only fair that it is up for grabs
bitnaive03/29/2019
maybe no one else should be allowed to issue it but it can be transferred
Vincent03/29/2019
why?
Chill03/29/2019
I really don't think that's fair, to be honest
S1LVA | GetRavencoin.org03/29/2019
@[Dev-Happy] Blondfrogs Unique names are lost, in that case.
And in that way, !ownership loses value by not having the ability to change, if need be
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Yeah I'd rather see the one name issued only forever
bitnaive03/29/2019
that way, if some one wants it. the can contact the owner for it.
[Dev-Happy] Blondfrogs03/29/2019
I think restricted assets have a different use case than regular assets, and they can be frozen.
Vincent03/29/2019
i can buy ravenland and revent push from moving forward with is project (after grace)
DirkDiggler (RVN ded)03/29/2019
seems like from a "code" perspective... the idea of 2 different (but similar names) would be a nightmare as well
Jeroz03/29/2019
Ideally give reissuable the extra option of making it restricted in my mind. I have mixed feelings about tokens traveling around that have the same asset name but are a different type.
Vincent03/29/2019
all his logos would have to change to his new name
S1LVA | GetRavencoin.org03/29/2019
They not have them remain one in the same? With the ability to change to restricted, should they have to. Though reissuance?
[Dev-Happy] Blondfrogs03/29/2019
@Vincent That is why push would have plenty of time to pick up the ravenland restricted asset if he wanted it
Rikki RATTOE Sr. SEC Impresantor03/29/2019
One of our selling points over ETH is that ETH can issue a bunch of the same named assets as long as the contract address is different
Vincent03/29/2019
bbut who says what is enough time
i may need yrs
bhorn03/29/2019
the extra cost could be onerous as well
Chill03/29/2019
when the asset layer was launched, it was billed as being unique names. Be careful in changing this, please.
[Dev-Happy] Blondfrogs03/29/2019
True, that amount of time isn't determined yet, if this is the route that is taken
bhorn03/29/2019
some have many many many assets
Rikki RATTOE Sr. SEC Impresantor03/29/2019
RVN, u issue that name once, it can never be duplicated
DirkDiggler (RVN ded)03/29/2019
where as having just another sub asset type ($RESTRICTED) falls under the same hierarchy already defined
bhorn03/29/2019
and the RVN is not as cheaply replaced
[Dev-Happy] Blondfrogs03/29/2019
@Chill Not changing that, just talking about the next asset usecase and how it could be coded is all
Rikki RATTOE Sr. SEC Impresantor03/29/2019
What kind of burn costs are we thinking w issuing restricted assets?
Synicide03/29/2019
@[Dev-Happy] Blondfrogs what if push decides not to, then someone else registers it for malicious intent with the same name? Surely the person who built their company on chain doesnt want another token of their company name out there
Vincent03/29/2019
@[Dev-Happy] Blondfrogs you seem to be the only one fighting for the garce period
[Dev-Happy] Blondfrogs03/29/2019
@Rikki RATTOE Sr. SEC Impresantor Not sure yet, going to be more than regular issuanace is the thought.
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Agreed
S1LVA | GetRavencoin.org03/29/2019
@Vincent Simply bringing it into conversation, no harm
[Dev-Happy] Blondfrogs03/29/2019
@Vincent Not fighting, just keeping an open mind. I just code it, I am not the one making the decision.
push | ravenland.org03/29/2019
hey this is a bit of a random question but i get a lot of subassets send to me, what about wildcard sending via the wallet? like if i wanted to send RAVENLAND/* to an address
Vincent03/29/2019
true but just showing what the concesous is
[Dev-Happy] Blondfrogs03/29/2019
@push | ravenland.org Create a request in the issues on github for extra functionality
push | ravenland.org03/29/2019
:thumbsup:
will do mate
Synicide03/29/2019
seems if ! and $ arent shared unique, then companies will have to register both just to protect themselves
Rikki RATTOE Sr. SEC Impresantor03/29/2019
How about a unique asset w re-issuable IPFS?
S1LVA | GetRavencoin.org03/29/2019
We should be giving more power to !ownership by allowing it the ability to change to $ - Not giving less power to !ownership by duplicating unique names.
Rikki RATTOE Sr. SEC Impresantor03/29/2019
GUNCERT provided a valid use case IMO for unique w re-issuable IPFS
[Dev-Happy] Blondfrogs03/29/2019
@Vincent Sure I get that.
Sevvy (not worried til 500sats)03/29/2019
Agrees
If this is a possibility, to give the restricted assets to those who own the normal ones, it ought to be done
[Dev-Happy] Blondfrogs03/29/2019
@Rikki RATTOE Sr. SEC Impresantor Looking in on how to do that. The request is on github just don't have the time to implement it yet.
restricted assets, will have to be issued. and the corresponding amount of rvn will be burned for them
push | ravenland.org03/29/2019
it'd be nice to see a ravencoin network swarm, us and mango farms are doing something with that so if anyone else wants to get involved, i think its a worthwhile thing to build the power of the ravencoin ipfs hash network to keep them hashes alive
Sevvy (not worried til 500sats)03/29/2019
Yikes
Ah well
push | ravenland.org03/29/2019
i wrote a programmatic script to scrape all the ipfs files, so i can probably runa simple enough shellscript to ipfs add pin everything from chain
Vincent03/29/2019
plus ravenland sent me a bunch of tokens...they will be worthless now!!! :sunglasses:
push | ravenland.org03/29/2019
:joy:
vincent
one day tho eh
Chill03/29/2019
my 250,000 RVN that were spent on RVN assets are feeling pretty weak at the moment
[Dev-Happy] Blondfrogs03/29/2019
@Vincent haha ravenland assets are still assets. They just don't have the ability to freeze then and stop you from trading them
DirkDiggler (RVN ded)03/29/2019
you got to have one ring to rule them all... the Unique Ownership Token does that
SamzOnline [w1ne]03/29/2019
@Chill That puts my 80 to shame!
[Dev-Happy] Blondfrogs03/29/2019
@Chill Like I said, no decision has been made yet.
Vincent03/29/2019
@[Dev-Happy] Blondfrogs just playing with that one
[Dev-Happy] Blondfrogs03/29/2019
@Vincent Yeah, I understand
S1LVA | GetRavencoin.org03/29/2019
Changing gears alittle, Has any further thought been put into privacy?
push | ravenland.org03/29/2019
a tor network with proxychains could be effectively used to privatize a node
Jeroz03/29/2019
Seems that we need to continue discussions about the asset naming and make a write up about the proposals.
I have a different question:
About metadata and transactions. Tron mentioned that it will be possible to attach metadata to every transaction. It was unclear to me whether he meant every messaging transaction or every regular RVN/Asset transaction.
push | ravenland.org03/29/2019
ive been looking into this a little bit
Synicide03/29/2019
@S1LVA | GetRavencoin.org been wondering that too, and if restricted assets for KYC/AML NEED to be trackable
[Dev-Happy] Blondfrogs03/29/2019
@S1LVA | GetRavencoin.org Privacy isn't the main thing ravencoin wants right now. We need to be able to send and trade assets with visibility of amounts and the asset names. Once the main core components are finished, we can start thinking about integration privacy.
push | ravenland.org03/29/2019
as i understand it tor could as a protocol be built into ravencoin itself and distroed as a private tor based connector or hardened in such a way not to leak dns or requests that are not 'tor' proxied .. but you could do this already with some modifications to most linux systems (without the need for a ravencoin release)
S1LVA | GetRavencoin.org03/29/2019
Understood
[Dev-Happy] Blondfrogs03/29/2019
@Jeroz With messaging, all asset transactions can contain a metadata field yes.
Jeroz03/29/2019
RVN too?
[Dev-Happy] Blondfrogs03/29/2019
Not RVN at this time, as that already exists with the OP_RETURN functionality of bitcoin
Jeroz03/29/2019
Yeah I was about to say
S1LVA | GetRavencoin.org03/29/2019
I dream of one day Ravencoin giving users the ability to protect themselves from state level actors looking to oversee transactions on chain.
[Master] Roshii03/29/2019
What's the subject?
[Dev-Happy] Blondfrogs03/29/2019
@S1LVA | GetRavencoin.org That would be amazing, however the dividends and voting require a public ledger in order to send
Synicide03/29/2019
@[Master] Roshii large one is if regular and restricted assets should share unique names, and/or if a grace peroid should be allowed for original owners to register restricted assets
[Dev-Happy] Blondfrogs03/29/2019
So we would need to figure out a way to have that info public and keep privacy
S1LVA | GetRavencoin.org03/29/2019
Agree'd
Synicide03/29/2019
that was my worry, that it HAS to be public for a lot of uses. Privacy would have to be optional
[Dev-Happy] Blondfrogs03/29/2019
ravencoin was built and is being built to support asset trading. Privacy is important but isn't currently the focus of the dev team.
Synicide03/29/2019
sounds good, focus on our roadmap and can research it more in the future
S1LVA | GetRavencoin.org03/29/2019
Privacy is one of the very lasts subjects brought up in the whitepaper, after all :wink:
Vincent03/29/2019
to bring up an old topic; assets that haven't been reissued, there was talk about lowering the decimal places to reissue; i know not important but if it needed to be in a hard fork; should it be looked at the add to th next?
[Dev-Happy] Blondfrogs03/29/2019
@Vincent I have found a way to do this, however it requires the reissuer to own all assets
Synicide03/29/2019
how would you determine the correct values if lowering decimals? rounding?
Rikki RATTOE Sr. SEC Impresantor03/29/2019
@[Dev-Happy] Blondfrogs Yes!
Vincent03/29/2019
correct
nice
Synicide03/29/2019
if they all own, I guess its a non-issue
[Dev-Happy] Blondfrogs03/29/2019
We aren't currently working on that, but I will try and get it into the hard fork release
Vincent03/29/2019
it would be a 1 time option, correct?
Rikki RATTOE Sr. SEC Impresantor03/29/2019
In that event too, ability to reduce total supply as well if u still own every asset created would also be an excellent Option to have
When 350? (350club)03/29/2019
Is Bruces worry about the security of Ravencoin a curent issue?
Chill03/29/2019
That seems to be the talk of the day
Zaab03/29/2019
Its just honesty
Sevvy (not worried til 500sats)03/29/2019
We know a 51% attack is cheap
[Dev-Happy] Blondfrogs03/29/2019
@Vincent Depends on if it meets requirements.
Sevvy (not worried til 500sats)03/29/2019
But reorg depth protection is good
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Yes Ravencoin currently doesn't have the network security that Bitcoin does, and water is wet
push | ravenland.org03/29/2019
more full nodes is the answer to a stronger consensus and therefore a more securer network
Sevvy (not worried til 500sats)03/29/2019
Hmmm checks out
push | ravenland.org03/29/2019
:ThinkBlack:
Vincent03/29/2019
right i guess my question is one time at most?
Synicide03/29/2019
It feels like more than just honesty. The last 4 post in a row from the Ravencoin twitter have some type of FUD based around it. Its all you see on the first page when looking at it. Some of that stuff needs to be kept to his personal account
Sevvy (not worried til 500sats)03/29/2019
Probably not a development Question, what Bruce says on his own time. :persevere:
Rikki RATTOE Sr. SEC Impresantor03/29/2019
@Synicide Bruce don't wanna spend a fortune on restricted assets :yum:
Sevvy (not worried til 500sats)03/29/2019
I don't like it myself either though @Synicide
boatsandhoes03/29/2019
yeah the ravencoin twitter has been a bit..... not good to put it easy
Vincent03/29/2019
this is bruces baby...and fud should be taken lightly imo
[Dev-Happy] Blondfrogs03/29/2019
Bruce can say what he wants :_)
Chill03/29/2019
well, it is the unofficial official Twitter page, so it kind of does matter
[Dev-Happy] Blondfrogs03/29/2019
We have taken measures to make sure ravencoin is safe and to stop 51% attacks
Synicide03/29/2019
I agree on his personal account. When people look up this project on twitter, they dont need a full page of fud
push | ravenland.org03/29/2019
its not a very development orientated debate tho in fairness
Vincent03/29/2019
no news will stop a well designed code
S1LVA | GetRavencoin.org03/29/2019
Many new users are asking about IPFS integration. Is this still being researched?
When 350? (350club)03/29/2019
I only asked as it appeared Bruce was saying there is a current security vulnerability..
push | ravenland.org03/29/2019
@[Dev-Happy] Blondfrogs what can people do to help secure the ravencoin network into 2019 and in the future?
Rikki RATTOE Sr. SEC Impresantor03/29/2019
@When 350? (350club) Bruce doesn't code, he wouldn't know
boatsandhoes03/29/2019
sorry, got a late start on this meeting. is kyc stuff on the table for discussion today, or is that at a later meeting?
[Dev-Happy] Blondfrogs03/29/2019
@push | ravenland.org Looks at the PR's, make sure the code being added is well written and secure.
push | ravenland.org03/29/2019
sure thing
and run fullnodes right?
[Dev-Happy] Blondfrogs03/29/2019
Run nodes, and mine ravencoin!
haha
hashpower
push | ravenland.org03/29/2019
:thumbsup:
boatsandhoes03/29/2019
that part
Pho3nix Monk3y03/29/2019
Looks like its time.
Jeroz03/29/2019
Alright, I have to pick up my son. Thanks everyone!
Pho3nix Monk3y03/29/2019
Thanks all
Rikki RATTOE Sr. SEC Impresantor03/29/2019
Thx!
Vincent03/29/2019
:sunglasses:
push | ravenland.org03/29/2019
cheers again :thumbsup: keep up the good work :rvn_hop:
Chill03/29/2019
thanks for everyone's hard work
Synicide03/29/2019
great talks today, thanks guys
Pho3nix Monk3y03/29/2019
Can have an admin shut it down and move this over to another channel until next time.
[Dev-Happy] Blondfrogs03/29/2019
Thanks for voicing your concerns.
S1LVA | GetRavencoin.org03/29/2019
Thanks everyone
Pho3nix Monk3y03/29/2019
@traysi ★★★★★ can you lock it back?
traysi ★★★★★03/29/2019
The channel is locked now.
submitted by mrderrik to Ravencoin [link] [comments]

9. bitcoind 6. bitcoin-qt Programming Bitcoin-qt using the RPC api (1 of 6) Communicate with Bitcoin-qt using C# - .NET (5 of 6) How to run Bitcoin-qt as a server with a configuration file (3 of 6)

Bitcoin Core 0.17.0. If the following options are not in a section, they will only apply to mainnet: addnode=, connect=, port=, bind=, rpcport=, rpcbind= and wallet=.The options to choose a network (regtest= and testnet=) must be specified outside of sections.‘label’ and ‘account’ APIs for wallet Prevent RPC move from deadlocking. This was caused by trying to lock the database twice. Fix use-after-free problems in initialization and shutdown, the latter of which caused Bitcoin-Qt to crash on Windows when exiting. Correct library linking so building on Windows natively works. The Bitcoin.com mining pool has the lowest share reject rate (0.15%) we've ever seen. Other pools have over 0.30% rejected shares. Furthermore, the Bitcoin.com pool has a super responsive and reliable support team. There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called bitcoind).They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. "C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -datadir=d:\BitcoinData Start Bitcoin, now you will see all the files are created in the new data directory. Linux. By default Bitcoin will put its data here: ~/.bitcoin/ You need to do a "ls -a" to see directories that start with a dot. If that's not it, you can do a search like this:

[index] [18346] [38370] [33540] [22784] [18607] [29513] [41553] [8254] [45415] [14005]

9. bitcoind

Programming Bitcoin-qt using the RPC api (1 of 6) - Duration: 3:17. Lars Holdgaard 4,643 views. 3:17. Language: English Location: United States Restricted Mode: Off History Help About ... An introduction to the Bitcoin JSON-RPC tutorial series. BTC: 1NPrfWgJfkANmd1jt88A141PjhiarT8d9U Communicate with Bitcoin-qt using C# - .NET. Category Howto & Style; Show more Show less. Loading... Autoplay When autoplay is enabled, a suggested video will automatically play next. Up next What ... Bitcoin JSON-RPC Tutorial 5 - Your First Calls - Duration: 10:06. m1xolyd1an 11,838 views. 10:06 . Building a Blockchain in Under 15 Minutes - Programmer explains - Duration: 14:28. Ivan on Tech ... Programming Bitcoin-qt using the RPC api (1 of 6) - Duration: 3:17. Lars Holdgaard 4,609 views. 3:17. Bitcoin-QT wallet review - Duration: 8:53. Secure Your Wallet Recommended for you. 8:53 . Web ...

#