Qt Wallet Out Of Sync anacondacon17.io

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]

Beginners guide to Syscoin (SYS) and why you should be investing in this cryptocurrency in 2018

What is Syscoin?

Some have described Syscoin (SYS) as the Shopify, Amazon and Ebay of the blockchain world. Syscoin is a revolutionary cryptocurrency that offers near zero cost financial transactions, incredible speed and provides businesses the infrastructure to trade goods, assets, digital certificates and data securely. Syscoin isn’t just about money and trading, it has the ability to attract various business types thanks to its native set of features geared towards business on the blockchain. From eBay traders and High Street shops to Medical applications, Insurance and Gaming, Syscoin’s decentralized network benefits everyone!
Syscoin is developed by Blockchain Foundry (BF). BF provides blockchain technology based services, projects and products for a wide variety of use cases with the stated aim of disrupting markets by leveraging the potential of blockchain technology. Syscoin is mainly known to be the first cryptocurrency to offer a fully decentralized marketplace based on blockchain. What is lesser known is that this is only a part of what Syscoin offers.
With the introduction of Masternodes in February or March 2018 SYS will be transformed from just a ’marketplace coin’ to a completely ‘utilitarian coin’. The Masternode infrastructure allows the addition of decentralized databases and file storage, increased transaction speed to surpass POS/Visa/Mastercard capabilities, true Turing complete smart contract capabilities for unlimited business logic, sidechains, application layers and an identity layer. This will all be accessible through an API, rather than a new language, enabling nearly any developer to create any blockchain application they can conceive. This will usher in the next generation of blockchain applications - made for new or existing businesses - by conveniently offering everything available from the blockchain space today.

SYS Origin

The blockchain as conceptualized by Satoshi Nakamoto back in 2008 envisioned a peer-to-peer electronic cash network that would prevent double-spending. A year later, the blockchain became an integral part of bitcoin, serving as the latter's public ledger of transactions. Although Nakamoto's reference client mentioned a decentralized marketplace service, the subsequent implementation did not incorporate this due to a lack of resources.
Syscoin was initially described in a 2014 draft whitepaper that envisioned Decentralized Marketplace Creation, Decentralized Smart Contracts and Documents, Decentralized Certificate Issuance and Transfer, and Decentralized Data Storage and Retrieval, as among the services that it would offer upon its release.
Syscoin aimed to bring Nakamoto's vision of a decentralized marketplace back into the blockchain, among the other commercial-grade services it aims to deliver to clients. Other services that Syscoin plans to provide include secure data storage and transfer, and unique user aliases that link their owners to the services controlled by the alias.
The early Syscoin wallet was superseded by the release of Blockmarket Desktop 1.0 on September 12, 2017, marking the culmination of Syscoin's vision of a fully decentralized marketplace with a desktop GUI based on the blockchain.
The planned release of Blockmarket Web, a fully web-based version, and Blockmarket Professional in 2018 takes that vision one step further, as more advanced seller stores become a reality.

The Team

The Team that NEVER quits! Before the launch of Syscoin (Q3 2014), there was a presale ICO by Moolah (as a partner), which turned out to be detrimental for Syscoin. The project raised around 1,000BTC for development but the Syscoin Team only managed to access 250BTC which were used for price support. Moolah (Ryan Kennedy) absconded with the bulk of the ICO funds and the Syscoin team were left with ~30million Syscoin at a price around 400 satoshi. Even after this tragic event, the devs didn’t quit and continued to work on the project without stopping. The case against Moolah is still on-going. See the article from CoinDesk here: http://www.coindesk.com/uk-court-syscoin-injunction-moolah-750-btc/.
What is this detail telling us about the dev team? While some crypto projects are just scams and bring little to no innovation, they’ve proven that they are in it for the long term - ably demonstrated by the fact that they continued to work despite their funds being stolen. And now that hard work is beginning to pay off with the entire team going full-time for the first time in January 2018 and new developers being hired following VC funding for BF.

Team Page: https://syscoin.org/team/

Blockchain Foundry Products

https://www.blockchainfoundry.co/products

What is Blockmarket Desktop?

Building on the World's First Decentralized Marketplace, Blockmarket is the newest generation of Syscoin's Desktop wallet with a complete, state-of-the-art marketplace built-in where you can securely and reliably buy and sell any items you wish. Entire stores can be created directly through the marketplace where you can sell your own products or re-sell others’ products for commission. Use of blockchain technology eliminates middlemen, credit card fees, maintenance fees, downtime and political interference. Persons are literally able to buy or sell anything to anyone, anytime, anywhere on Earth! Blockmarket Desktop was launched on September 12, 2017.

Key Blockmarket Features

• Price Pegging to currencies such as USD, EUR, GBP, CAD, CNY and BTC
• Bitcoin and Zcash as payment options
• Arbitrated Escrow
• Encrypted Messaging
• KYC/AML Compliance
• Images
• Unlimited Inventory Items

Name Aliases

Wallet addresses for cryptocurrencies generally consist of a unique string of between 27-34 alphanumeric characters. Such an address isn’t easy to memorize. Although the addresses can be added to an address book within the wallet, Syscoin has taken the user's convenience one step further, allowing you to create a unique Alias for your wallet address, such as a name, title, or characters specific to a username. These can be used to send SYS from home, to a mobile wallet, to work, to friends, to common suppliers or to repeat customers easily, without requiring any memorizing, writing it down, copy & pasting or emailing yourself the address.

Digital Certificates

Using the cryptography of the blockchain persons can issue, authorize, and exchange digital certificates of any kind. With Syscoin anyone can issue provably-unique certificates with text or ASCII content to one or multiple parties on the Syscoin blockchain. These certificates can be authenticated by anyone via Syscoin’s cryptographic proof of work. This allows for the creation and free exchange of any kind of digital asset such as ownership certificates, warranties, receipts, tickets, certifications, diplomas, software licenses and more.

Integrated Exchanges

Integrated Crypto exchanges - Flypme and Changelly will facilitate exchanging 30+ cryptos for SYS, directly within the Blockmarket wallet.

Security Audit Verified

Blockmarket was successfully and independently security audited by Digital Boundary Group and was deemed low risk. Audit Results: [https://medium.com/@BlockchainFoundry/blockmarket-security-audit-results-and-next-steps-f69f94f149bf]

Blockmarket Web – (The Key to Mass Adoption)

BM web will bring SYS’s existing decentralized marketplace and all its features into a web-based version, enabling ease of use with a simple email and password login (grandma friendly) without any need for downloading a wallet or waiting for sync. Blockmarket web will be launched in February 2018.

Key Syscoin Developments

Masternodes

Ability for world-class transactions-per-second performance to scale-out with added nodes (theoretically 100k TPS per 1000 Masternodes, 300k TPS/3k masternodes, etc). In later releases, masternodes will also process smart contracts and facilitate sharded+encrypted offchain file-storage (with onchain anchors), among other touted functionality. They should also result in steadying the price movements - less volatility as holding will be incentivized

Smart Contracts

Scalable Ethereum Virtual Machine: Allows Turing complete smart contracts to be executed following the ethereum protocol at a much faster speed and at a fraction of the ethereum gas price.

Assets & Token Issuance

With its token issuance service, Syscoin allows anyone to create a custom asset token which can then be sent directly to anyone else on the network. This facilitates a variety of use cases including ICO token issuance, supply chain management, reward points, and loyalty programs.

Anonymous Transactions

Anonymous transactions: via mixing/shuffling at user-specified denomination. Afterwards, additional tech will be added in the near future which will further compound the degree of anonymity provided -Add ValueShuffle running on top of the masternode layer and you have the world's most advanced privacy tech in any coin. This brings true money fungibility to Syscoin and the missing link for true economic sovereignty. https://twitter.com/realSidhuJag/status/948588279540035584

Instant Send

Transactions can be sent and received instantly. This represents a similar sending capability as Dash, but is a step beyond- A type of backend node locking will allow an instantly received sum to be sent immediately, without delay, and without network risk of double-spend.

Why Invest in Syscoin?

https://medium.com/@StevenVoros88/the-most-undervalued-project-in-the-crypto-world-not-for-long-96814ac66b08 https://medium.com/@danieljasonwestby/syscoin-the-hidden-gem-of-2018-96f973b81b9 https://twitter.com/Asbsvc/status/939959284246380545 https://twitter.com/CryptoBulld0g/status/935915911776784384 https://medium.com/@BlockchainFoundry/syscoin-to-disrupt-ebay-and-real-estate-industries-96aa55ef709a https://medium.com/@thecryptojournal.com/top-crypto-investment-for-2017-b99656491c6f https://www.youtube.com/watch?v=VNDprLJhGys

Merchants

https://medium.com/@BlockchainFoundry/merchant-pilot-program-update-7479fe451639

Partnerships

(Microsoft Azure)[https://azure.microsoft.com/en-us/blog/syscoin-joins-azure/]

Decentralized Identity Foundation

https://medium.com/@BlockchainFoundry/consensus-decentralized-identity-foundation-blockmarket-beta-3-beyond-6f830419ea55

White Paper

http://syscoin.org/whitepaper.pdf
Note: It is anticipated that the whitepaper will be updated by the team in the near future due to recent developments

Roadmap

http://syscoin.org/images/roadmap_2018__1024.png

Blockchain Application Development Architecture

https://cdn-images-1.medium.com/max/1200/1*bUO6_nRI7q805edG59e0DQ.png

Feature List 2017 & 2018

https://pbs.twimg.com/media/DUJwbI_X4AI3QL_.jpg

Where to Buy

• Bittrex • Poloniex • Upbit • Tux Exchange • Livecoin • Yobit • AEX • Bittylicious • Changelly • Flyp.me

Wallets

• Block Market Wallet 1.2 – Windows and Mac. Download from https://syscoin.org/
• QT Wallet for Developers: Download from https://github.com/syscoin/syscoin2/releases/tag/2.1.6
• Coinomi – Syscoin MultiCoin Wallet (only supports send/receive)
• HolyTransaction – Syscoin Multicoin Web Wallet (desktop & android)

Other Sources

https://syscoin.org/ https://twitter.com/syscoin https://www.blockchainfoundry.co/ https://en.wikipedia.org/wiki/Syscoin
Disclaimer This post was created particularly to aid those who are new to Syscoin. Please note that the content provided within this post is for information purposes only and is not to be construed as investment advice.
submitted by one22manytimes to CryptoCurrency [link] [comments]

[PSA] Dogecoin Wallet version 1.4 released. You must update.

WARNING: DO NOT send your wallet.dat file or dogecoin folder to anyone. There have been reports of people offering to help others by asking them to send their files to them so they can help. DO NOT do this. Scam attempt picture
Always encrypt your wallet! I can't express this enough. You should use a strong password longer than 15 characters. This password should contain numbers, symbols, and some capitalization! There is no need to have your wallet open 24 hours a day. Open it only when you need it. See - 'Getting Started' on the side bar.
This entire post has been written to be as close to ELI5 (Explain it like I'm 5) as possible - By request! If anyone wants to add/fix/correct anything in this message, please send a message to the mods <<-- Click blue text.
All blue text in this post can be clicked on. The blue text is a link to a picture, site or download file.
A very important message/reminder below.
25 Jan 1.5 pre-releases have started.
http://www.reddit.com/dogecoin/comments/1uhpwf/dogecoin_for_mac_14_topic_thread/
OLD VERSIONS The 1.4 update for the dogecoin wallet has been released. This update addresses the block chain error that occurred. This update is mandatory meaning you have to do this update. Also further down the page you can read up about the block chain. You MUST make sure you're on the correct block chain and the old block chain has been removed.
For a Windows computer the version must be 1.4. - 1.4.1 just released! See below
For a Apple Mac Computer the version must be 1.4
Download links:
[Windows Download Link](https://github.com/dogecoin/dogecoin/releases/download/1.4/dogecoin-qt-v14-Win.zip) <<--Click to start download
Windows Download Link 1.4.1 UPDATED 19JAN
Mac Download Link <<--Click to start download
Mac users can join this thread if there are any problems
Android (phone): Please see This post
To update, simply download the new version from the download link above. Open the downloaded file and extract the contents of the downloaded file into any new folder or location on your computer. If you put the files into a folder you can name the folder anything you want but make sure you remember that this is the latest version of the software.
You don't have to remove your folder containing the old version of the wallet. You can place it in a folder called 'Old versions of dogecoin wallet' if you like.
Now you can click on the Dogecoin icon contained in the new folder to open your version 1.4 wallet.
What happens if I get an error when I open the new wallet?
An error was reported called "11DbException"
If this happens Download this file and place it in the same folder as your updated wallet. Open the file you just downloaded called "Dogecoin OPEN' and wait. This might take 2 or 3 minutes.
Also jtlarousse has found a solution that worked on Windows. Please follow carefully and make backups before starting.
Reebzy might have found a solution for Apple Mac
Blockchain fork 101: The block chain is a ledger or document created containing every transaction that has ever happened. This file can be quite large. Bitcoins ledger is over 15GB. At some point this document/ledger split into two separate documents known as a fork.
How do I know if I am on the right block chain?
Go to your newly updated dogecoin wallet and open it. Click on Help>>Debug next Observe the current block number
*Note the example numbers in the pictures might be out of date by the time you read them
Now go over to http://dogechain.info/chain/Dogecoin . This website is the official Dogecoin blockchain website. Check the block number they're reporting
The number you found in your wallet and the number reported on the website should close. There might be a difference of 100 blocks depending on when you last refreshed your wallet or how long it took for you to get from one step to the next step in this guide and if the dogechain website is lagging.
I'M NOT ON THE CORRECT BLOCK CHAIN
My numbers are very different. How do I get back onto the right block chain?
IMPORTANT
For windows:
1)Close down the Dogecoin wallet client.
2)Go to your data folder: C:\Users[your windows log-in name]\AppData\Roaming\DogeCoin
3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file!
4)Download this update file and place it into the Dogecoin folder where the other file was deleted.
For Apple Mac:
1)Close down the Dogecoin wallet client.
2)Go to your data folder: ~/Libarary/Application Support/Dogecoin
3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file!
4)Download this update file and place it into the Dogecoin folder where the other file was deleted.
Next visit this post by Netcodepool for instructions on how to manually download the correct block chain and install it.
Much Thanks. 
Edit: Some posts were removed from this thread. To limit confusion.
Check this post for details about mining pools that were/are using the wrong fork.
Did you send coins only to find out you're on the wrong chain? See this post to get them back
An Apple Mac support thread has been made by voidref (The mac developer). If you're having troubles please see this thread
Some shibes have reported their wallets wont sync. Please check to make sure your firewall, antivirus, malware scanner or similar programs are not blocking it the wallet. You can add rules to these programs to allow the wallet to make contact with the internet. It's not advised but possible to also disable the software for a short amount of time. Don't forget to enable the software again afterwards.
Is your wallet crashing? Try this helpful tip from gandhikahn or if you're using windows try the 1.4.1 update above.
submitted by 42points to dogecoin [link] [comments]

Useful Beginner's Guide to Syscoin

What is Syscoin?

Some have described Syscoin (SYS) as the Shopify, Amazon and Ebay of the blockchain world. Syscoin is a revolutionary cryptocurrency that offers near zero cost financial transactions, incredible speed and provides businesses the infrastructure to trade goods, assets, digital certificates and data securely. Syscoin isn’t just about money and trading, it has the ability to attract various business types thanks to its native set of features geared towards business on the blockchain. From eBay traders and High Street shops to Medical applications, Insurance and Gaming, Syscoin’s decentralized network benefits everyone!   Syscoin is developed by Blockchain Foundry (BF). BF provides blockchain technology based services, projects and products for a wide variety of use cases with the stated aim of disrupting markets by leveraging the potential of blockchain technology. Syscoin is mainly known to be the first cryptocurrency to offer a fully decentralized marketplace based on blockchain. What is lesser known is that this is only a part of what Syscoin offers.   With the introduction of Masternodes in February or March 2018 SYS will be transformed from just a ’marketplace coin’ to a completely ‘utilitarian coin’. The Masternode infrastructure allows the addition of decentralized databases and file storage, increased transaction speed to surpass POS/Visa/Mastercard capabilities, true Turing complete smart contract capabilities for unlimited business logic, sidechains, application layers and an identity layer. This will all be accessible through an API, rather than a new language, enabling nearly any developer to create any blockchain application they can conceive. This will usher in the next generation of blockchain applications - made for new or existing businesses - by conveniently offering everything available from the blockchain space today. In simple terms think Dash + Ethereum/Lisk + Monero + Nano + Storj + Particl capabilities all in one coin!    

SYS Origin

The blockchain as conceptualized by Satoshi Nakamoto back in 2008 envisioned a peer-to-peer electronic cash network that would prevent double-spending. A year later, the blockchain became an integral part of bitcoin, serving as the latter's public ledger of transactions. Although Nakamoto's reference client mentioned a decentralized marketplace service, the subsequent implementation did not incorporate this due to a lack of resources.   Syscoin was initially described in a 2014 draft whitepaper that envisioned Decentralized Marketplace Creation, Decentralized Smart Contracts and Documents, Decentralized Certificate Issuance and Transfer, and Decentralized Data Storage and Retrieval, as among the services that it would offer upon its release.   Syscoin aimed to bring Nakamoto's vision of a decentralized marketplace back into the blockchain, among the other commercial-grade services it aims to deliver to clients. Other services that Syscoin plans to provide include secure data storage and transfer, and unique user aliases that link their owners to the services controlled by the alias.   The early Syscoin wallet was superseded by the release of Blockmarket Desktop 1.0 on September 12, 2017, marking the culmination of Syscoin's vision of a fully decentralized marketplace with a desktop GUI based on the blockchain.   The planned release of Blockmarket Web, a fully web-based version, and Blockmarket Professional in 2018 takes that vision one step further, as more advanced seller stores become a reality.    

The Team

The Team that NEVER quits! Before the launch of Syscoin (Q3 2014), there was a presale ICO by Moolah (as a partner), which turned out to be detrimental for Syscoin. The project raised around 1,000BTC for development but the Syscoin Team only managed to access 250BTC which were used for price support. Moolah (Ryan Kennedy) absconded with the bulk of the ICO funds and the Syscoin team were left with ~30million Syscoin at a price around 400 satoshi. Even after this tragic event, the devs didn’t quit and continued to work on the project without stopping. The case against Moolah is still on-going. See the article from CoinDesk here: http://www.coindesk.com/uk-court-syscoin-injunction-moolah-750-btc/.   What is this detail telling us about the dev team? While some crypto projects are just scams and bring little to no innovation, they’ve proven that they are in it for the long term - ably demonstrated by the fact that they continued to work despite their funds being stolen. And now that hard work is beginning to pay off with the entire team going full-time for the first time in January 2018 and new developers being hired following VC funding for BF.
View Team Page.    

Blockchain Foundry Products

BF Products    

What is Blockmarket Desktop?

Building on the World's First Decentralized Marketplace, Blockmarket is the newest generation of Syscoin's Desktop wallet with a complete, state-of-the-art marketplace built-in where you can securely and reliably buy and sell any items you wish. Entire stores can be created directly through the marketplace where you can sell your own products or re-sell others’ products for commission. Use of blockchain technology eliminates middlemen, credit card fees, maintenance fees, downtime and political interference. Persons are literally able to buy or sell anything to anyone, anytime, anywhere on Earth! Blockmarket Desktop was launched on September 12, 2017. Download Blockmarket Desktop 1.2    

Key Blockmarket Features

- Decentralized Marketplace

The marketplace platform provides a decentralized and high redundant channel for selling goods and services. Features include: • Price Pegging to currencies such as USD, EUR, GBP, CAD, CNY and BTC • Bitcoin and Zcash as payment options • Arbitrated Escrow • Encrypted Messaging • KYC/AML Compliance • Images • Unlimited Inventory Items  

- Name Aliases

Wallet addresses for cryptocurrencies generally consist of a unique string of between 27-34 alphanumeric characters. Such an address isn’t easy to memorize. Although the addresses can be added to an address book within the wallet, Syscoin has taken the user's convenience one step further, allowing you to create a unique Alias for your wallet address, such as a name, title, or characters specific to a username. These can be used to send SYS from home, to a mobile wallet, to work, to friends, to common suppliers or to repeat customers easily, without requiring any memorizing, writing it down, copy & pasting or emailing yourself the address.  

- Digital Certificates

Using the cryptography of the blockchain persons can issue, authorize, and exchange digital certificates of any kind. With Syscoin anyone can issue provably-unique certificates with text or ASCII content to one or multiple parties on the Syscoin blockchain. These certificates can be authenticated by anyone via Syscoin’s cryptographic proof of work. This allows for the creation and free exchange of any kind of digital asset such as ownership certificates, warranties, receipts, tickets, certifications, diplomas, software licenses and more.  

- Integrated Exchanges

Integrated Crypto exchanges - Flypme and Changelly will facilitate exchanging 30+ cryptos for SYS, directly within the Blockmarket wallet.  

- Security Audit Verified

Blockmarket was successfully and independently security audited by Digital Boundary Group and was deemed low risk. View Audit Results.    

Blockmarket Desktop – Quickstart Tutorials (16 short vids)

BM Desktop – Quickstart Tutorials    

Blockmarket Web – (The Key to Mass Adoption)

BM web will bring SYS’s existing decentralized marketplace and all its features into a web-based version, enabling ease of use with a simple email and password login (grandma friendly) without any need for downloading a wallet or waiting for sync. Blockmarket web will be launched in Q1 2018.   This launch will be accompanied by a marketing campaign roll-out that seeks to build brand recognition with audiences within the existing crypto ecosystem and more significantly with the broader, global, non-crypto audience. For this reason Ballistic Arts, a full-service marketing agency was retained by BF. BF Engages Marketing Agency    

Primary Target Market + Value Potential

The primary target market for BF’s Syscoin/Blockmarket web flagship is the retail e-commerce industry. This sets up their decentralized marketplace to rival such commercial giants as Amazon ($648B market cap), Alibaba ($453B market cap) and eBay ($43B market cap). According to eMarketer’s Worldwide Retail and Ecommerce Sales report, global retail e-commerce sales for 2017 were $2.3 Trillion. This is expected to reach an estimated $4 Trillion by 2020 reflecting the rapid growth within this sector.   To perform a very simple assessment of the Syscoin/Blockmarket web’s potential let’s assume that a 1% portion of the forecasted $4 trillion market is captured, which represents $40 billion in revenue. Assuming a sales to market cap ratio of 1:1 for simplicity, the circulating supply of 531 million SYS, with a $40 billion market cap yields a price of roughly $75 per coin. However, with masternodes that limit the circulating supply and token utility that extends beyond retail e-commerce, the SYS price could likely reach much higher. Please note that these are just very simple assumptions and projections for this exercise, however the real world driven potential that this project has is clearly evident.    

Key Syscoin Developments

- Z-DAG: Zero Confirmation Transactions with Double Spend Protection (WORLD’S FIRST)

View Developer’s Twitter post View Syscoin’s Twitter post  

- Masternodes

Ability for world-class transactions-per-second performance to scale-out with added nodes (theoretically 100k TPS per 1000 Masternodes, 300k TPS/3k masternodes, etc). In later releases, masternodes will also process smart contracts and facilitate sharded+encrypted offchain file-storage (with onchain anchors), among other touted functionality. They should also result in steadying the price movements - less volatility as holding will be incentivized.  

- Masternode Rewards + Min. Hardware Specs

Masternode Rewards + Min. Hardware Specs Masternode ROI Calculator  

- Smart Contracts

Scalable Ethereum Virtual Machine: Allows Turin complete smart contracts to be executed following the ethereum protocol at a much faster speed and at a fraction of the ethereum gas price.  

- Assets & Token Issuance

With its token issuance service, Syscoin allows anyone to create a custom asset token which can then be sent directly to anyone else on the network. This facilitates a variety of use cases including ICO token issuance, supply chain management, reward points, and loyalty programs.  

- Anonymous Transactions

Anonymous transactions: via mixing/shuffling at user-specified denomination. Afterwards, additional tech will be added in the near future which will further compound the degree of anonymity provided -Add ValueShuffle running on top of the masternode layer and you have the world's most advanced privacy tech in any coin. This brings true money fungibility to Syscoin and the missing link for true economic sovereignty. View Developer’s Twitter post.  

- Instant Send

Transactions can be sent and received instantly. This represents a similar sending capability as Dash, but is a step beyond- A type of backend node locking will allow an instantly received sum to be sent immediately, without delay, and without network risk of double-spend.    

Why Invest in Syscoin?

 

Merchants

Merchant Pilot Program    

Partnerships

Development Updates

White Paper

White Paper.pdf Note: It is anticipated that the whitepaper will be updated by the team in the near future due to recent developments    

Roadmap

Roadmap 2017-2018.png    

Blockchain Application Development Architecture

Blockchain Application Development Architecture.png    

Feature List 2017 & 2018

Feature List 2017 & 2018.jpg    

Where to Buy

BittrexPoloniexUpbitTux ExchangeLivecoinYobitAEXBittyliciousChangellyFlyp.me    

Wallets

• Block Market Wallet 1.2 – Windows and Mac. Download from https://syscoin.org/ • QT Wallet for Developers: Download from https://github.com/syscoin/syscoin2/releases/tag/2.1.6Coinomi – Syscoin MultiCoin Wallet (only supports send/receive)HolyTransaction – Syscoin Multicoin Web Wallet (desktop & android)    

Need Help or Want to Contribute?

If you need help for an important wallet issue or if you want to know how you can contribute in promoting Syscoin Join the Slack channel where the SYS team and community members are active, helpful and responsive.    

Credit To

Other Sources

https://syscoin.org/ https://twitter.com/syscoin https://www.blockchainfoundry.co/ https://en.wikipedia.org/wiki/Syscoin    

Last Updated

This post was last updated on Feb 10 2018.    

Disclaimer

This post was created particularly to aid those who are new to Syscoin. Please note that the content provided within this post is for information purposes only and is not to be construed as investment advice.
submitted by idbrews to SysCoin [link] [comments]

Bitcoin Core 0.10.1 Released

Bitcoin Core version 0.10.1 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.10.1/
This is a new minor version release, bringing bug fixes and translation updates. If you are using 0.10.0, it is recommended to upgrade to this version.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

Upgrading and downgrading

How to Upgrade

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 (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).

Downgrade warning

Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with pre-0.10 versions of Bitcoin Core or other software:
If you want to be able to downgrade smoothly, make a backup of your entire data directory. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised 0.10 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.

Notable changes

This is a minor release and hence there are no notable changes. For the notable changes in 0.10, refer to the release notes for the 0.10.0 release at https://github.com/bitcoin/bitcoin/blob/v0.10.0/doc/release-notes.md

0.10.1 Change log

Detailed release notes follow. This overview includes changes that affect external behavior, not code moves, refactors or string updates.
RPC:
Block (database) and transaction handling:
P2P protocol and network code:
Validation:
Build system:
Wallet:
GUI:
Tests:
Miscellaneous:

Credits

Thanks to everyone who contributed to this release:
As well as everyone that helped translating on Transifex.
submitted by harda to Bitcoin [link] [comments]

[Social X] Architecture of A Decentralised System for Social Payment and Services

Dear fellow Reddheads:
It's been a month since the successful launch of PoSV, which marked the end of stage one of Reddcoin project. There were three main goals for stage one:
  1. fair distribution of Reddcoin to common users (tipping), miners (mining) and investors (IPCO).
  2. an innovative algorithm to secure the network and encourage ownership, participation and decentralisation (PoSV).
  3. to build out a team of super talented and trustworthy developers.
The three goals have all been achieved so it's time for us to enter stage two: the buildout of services to make Reddcoin actually useful. This is what Social X is meant for. I'm still polishing the whitepaper to make it live up to my own self-imposed high standard, but I think the time is right for me to unveil it in broad strokes. There are three main problems Social X aims to solve.

Social X: why are wallets so difficult to use?

To achieve wide adoption of Reddcoin (or any cryptocurrency) by the non-tech-savvy general public, wallets must solve the following issues:
Ever increasing blockchain size discourages users from running full-blown wallets. It takes too much time and efforts to install or repair. A common user tends to find the process frustrating or even impenetrable and is forced to either give up adoption or rely on 3rd-party service providers (e.g. exchanges, wallets using ReddAPI) to take full control of her fund. Blockchain size grows everyday and grows faster with wider adoption.
Current wallets generate private keys randomly. As a user engages in staking or normal transactions, she has to back up wallet.dat file periodically to make sure all newly generated private keys are backed up. If wallet.dat file is corrupted or lost, there is no way to recover lost fund.
Again, due to the fact that private keys are randomly generated, it's impossible for a user to share the same wallet.dat file across multiple devices (e.g. desktop, iOS, Android) and multiple platforms (e.g. Windows, Linux, Mac). Different copies of wallet.dat will get out-of-sync. A user has to manage each wallet independently, which leads to significant operational burden and risk.
It would be extremely valuable for a service provider, such as an exchange or e-commerce site, to be able to generate unique public keys to receive fund while putting the corresponding private keys in cold storage. The impact on security is significant.

Social X: why is it so hard for me to tip someone?

One essential feature of Bitcoin is pseudo-anonymity. To pay someone, you need to get hold of her impenetrable public hash key, somehow. And the hash key, i.e. the wallet address, may not be valid a moment later because the owner might have lost the corresponding private key. Ironically, this awkwardness, even backwardness, is not perceived as a disadvantage by almost all the cryptocurrencies. In fact, on the contrary, the single biggest, hottest, most wanted feature is full decentralised anonymity, which has seen the rise and fall of many cryptocurrencies and their copycats. While all the other cryptocurrencies compete with each other on this front, Reddcoin, aiming to the social currency of the digital age, moves in the opposite direction. Social lives are not possible without social identities.

Social X: why can't I use a service without giving up control?

The vast majority of 3rd-party service providers which hold fund on a user's behalf has exclusive full control of her private keys. If a service is indeed worthy, a user has no choice but to trust the 3rd party with security and integrity. It's ironic, to say the least, that cryptocurrencies which are created to remove exactly this need for blind trust in middlemen end up in a much worse position than fiat currencies due to the fact that many cryptocurrency companies are unregulated and incompetent. Then the question is: is there a way to create an ecosystem where anyone can write and provide valuable social applications in a fully decentralised fashion?

Social X: Architecture for a Decentralised System for Social Payment and Services

Social X has many components which are already being actively developed. Below I give a brief description of some of them.
  1. In the future, there will be two types of official Reddcoin wallets. QT wallet and reddcoind are full wallets required to run a full node. A second type of wallets, called thin wallets or SPV wallets will use the technology of Electrum modified and enhanced to support PoSV and staking. These wallets include mobile wallets on iOS, Android, next-generation Social Wallet on desktop and wallets inside browsers (Chrome/Firefox/Safari). I've already finished writing and started testing the reference implementation of Reddcoin Electrum server and client. Each client only needs to download 25M of data vs the current full blockchain at 660M. This is how we solve the blockchain size problem.
  2. All our official wallets, whether full or thin, will be deterministic. All private keys are generated deterministically from a long passphrase. This passphrase is all you need to remember and backup and with it you can fully recover your wallet and funds anytime anywhere. You will also be able to support multiple wallets on multiple platforms and devices and they will all be in sync. This is how we solve the portability problem.
  3. All our official wallets, whether full or thin, will be hierarchical. They will allow users to generate public keys on demand while keeping private keys in cold storage. This is how we solve the cold storage problem.
  4. I'm writing code (~30% finished) for sth we call Reddcoin Social ID (Redd-ID):
    • It's a new service provided at the blockchain level.
    • It allow users to associate a username with one private key.
    • The user can choose to bundle extra information such as email, address and avatar.
    • The information is public and embedded in the blockchain. As a result, any user can send Reddcoin to another by simply specifying the recipient's Redd-ID.
    • Redd-ID registration costs Reddcoins. The costs vary depending on many factors such as the length of the username. For example, we expect popular names like tom to cost at least 7 figure.
    • Redd-ID registration is verified in PoSV blocks. Therefore all active Reddcoin stakers will be the provider of Redd-ID service.
    • Redd-ID registration fee goes to the Reddhead who successfully mints the PoSV block that verifies and confirms the registration. In a sense, it will feel like a lottery. And this is why this service doesn't make sense for any PoW coin where each block is pool-mined.
    • Redd-IDs can be transferred to new addresses and by default auto-expire annually and can be renewed.
    • Small Reddcoin holders, as long as they keep staking, may double, triple or 10x their existing holdings just by receiving registration fees.
    • Businesses and organisations can register usernames for purposes like receiving donation.
  5. There will be several services available to provide more ways for Redd-ID to be used on Internet. I don't want to disclose all our cards here. Please wait for my whitepaper and see what we have for you as surprises. Meanwhile, do share with us how you imagine Redd-ID can be used.
  6. Different components of Social X will allow decentralised tipping across all social networks. In our next-generation social tipping platform, there will be no tipbots! When you tip someone on Reddit, Twitter, Twitch, Youtube or Facebook, the tipping goes straight from local wallet, whether on your mobile or desktop to the recipient.
  7. There will be APIs to allow 3rd parties to write and offer decentralised social applications.

Social X: where are we now?

  1. I'm finishing the whitepaper in coming weeks (while writing a lot of code). The whitepaper will contains much more information than this post.
  2. Reddcoin Electrum wallets for iOS and Android are being actively developed.
  3. Reddcoin full wallets (QT/reddcoind) are already hierarchical deterministic in the development branch and are being internally tested.
  4. The Social Tipping Platform is being actively developed.
  5. I need volunteers to host and test Reddcoin Electrum server and clients. I'll make a separate post next week.

Epilogue

Below I'll only answer questions selectively. Much more details will be available in the whitepaper and there is no reason to jump the gun and repeat it here. Stage one took us 6 months. We expect stage two to take 6 months also. It may be the most exciting period in the history of Reddcoin project.
Regards
laudney
submitted by laudney to reddCoin [link] [comments]

IRC Log from Ravencoin Open Developer Meeting - Aug 10, 2018

[16:01] <@Wolfsokta> Todays topics: DGW implementation, segfault, Q&A, feedback on IRC
[16:01] <@Wolfsokta> Just to set the stage here, this is a developer meeting where developers that have contributed source code to the Ravencoin project can meet and chat about items they are working on. Please be respectful to one another. For the sake of staying on target, please limit interactions to questions and comments on code or projects that you are working on. Any time left over at the end can be opened up for general Q&A.
[16:02] <@Wolfsokta> FYI - I'm RavencoinDev, and lets get started.
[16:03] <@Wolfsokta> @Tron, can you talk about where we are at with DGW on testnet and mainnet?
[16:03] <@Tron> Sure.
[16:03] can someone volunteer to take notes and post also?
[16:03] <@Tron> We are building binaries that will activate DGW-180 at block 338778
[16:04] <@Tron> It looks back 180 blocks to calculate the diff.
[16:04] I will copy the text from the meeting into a file that can be archived later. I can also make summary notes after like BTC core does.
[16:04] I'll save a log of the whole meeting and can post it on the subreddit thread.
[16:04] <@Wolfsokta> We have setup testnet4 in order to test the new binaries.
[16:04] great
[16:05] <@Wolfsokta> We plan to release the binaries later today.
[16:05] @Tron have you looked into the timestamp attack concerns of DGW?
[16:05] https://github.com/zawy12/difficulty-algorithms/issues/30
[16:06] <@Tron> Yes. And for that reason, we've tightened up the timestamps that will be accepted for valid blocks.
[16:06] <@Tron> Moved from 2h to 12 minutes.
[16:06] nice
[16:06] Oh wow okay
[16:06] <@Tron> Its also the reason we went from 60 blocks (lookback) to 180 blocks.
[16:07] why would 2h ever be acceptable? lol
[16:07] 2h was originally used for daylight savings shenanigans I believe
[16:07] <@Tron> It was from bitcoin, and it factors in clock skew, and variance in finding blocks on 10 minute intervals, and block propagation time.
[16:07] makes sense
[16:08] what about the segmentation fault when reindexing?
[16:08] any fix yet?
[16:08] @Tron 12 minutes seems to be pretty small window for clock skew
[16:08] I assume it was chosen due to 1/10th scaling from BTC?
[16:09] <@Wolfsokta> Not yet ruski, we'll cover that in a bit.
[16:09] <@Tron> We did divide existing by 10.
[16:10] <@Wolfsokta> Any further questions about DGW on testnet or on mainnet?
[16:10] What block is it activating on mainnet?
[16:10] <@Wolfsokta> 338778
[16:11] And will there be the need to update binaries twice (for DGW fork and asset layer fork)?
[16:11] <@Tron> We are activating DGW by block height because headers sync first, and the BIP9 activation flag sets a flag, and we need to look at either block height or version to know which diff algo.
[16:11] <@Wolfsokta> Calculated to be near the end of the month so we have some time with DGW on testnet.
[16:11] Someone on discord asked this a while back, but why Was DGW chosen over something like digishield or anyother algo
[16:11] <@Tron> And block version can be changed (tampering) and still make it on the chain.
[16:12] Binaries will need to be updated as more asset layer stuff get completed and tested. Not by the end of the month though.
[16:12] <@Tron> We looked at DGW and LWMA. LWMA has a lot of constants that must be tuned right.
[16:13] <@Tron> We were impressed with the amount of work on LWMA to analyze how it responds, but it wasn't straightforward to understand the nuances of how/why it works.
[16:13] zawy was in the #development channel on Discord. He's an expert on DAAs. I'm sure he would help with tuning LWMA if you asked.
[16:14] <@Tron> Either will be much better that what we have. Even at the extremes, it will adjust smoothly.
[16:14] Are there any issues or comments on the DGW code that should be addressed?
[16:14] @devs in general
[16:15] <@Wolfsokta> Thanks @brianmct, we did look extensively at the DGW code to ensure we weren't going to see the same issues that happened to Verge.
[16:16] so i guess you would have to make way more blocks with false timestamps to be able to exploit our version of dgw right?
[16:16] because of the 12 minute timestamp thing?
[16:16] <@Wolfsokta> With X16R, and with the changes Tron talked about we feel confident that this will address the swings without being able to be exploited.
[16:17] nice
[16:17] @russki Yeah, pretty much.
[16:17] verge is a different type of situation - but overall asics and mining are a risk always
[16:18] <@Wolfsokta> Okay, anything else on the difficulty targeting change?
[16:19] <@Wolfsokta> Cool, blondfrogs wanted to talk about subassets that were added.
[16:19] ooh yeah i saw those github commits
[16:19] looking good
[16:19] We also want to let everyone know that you can now create sub assets with the new binaries that will be posted soon. You can create these subassets using the issue rpc call. Qt will be built shortly. This will allow users to make an asset PARENT
[16:20] <@Wolfsokta> Basic overview. If you own an asset you can create sub-assets by including a '/
[16:20] nice
[16:20] And then make any of the following PARENT/A PARENT/B .... PARENT/Z
[16:20] <@Tron> We'll post a FAQ on assets later today.
[16:21] <@Wolfsokta> And it only is 100 Raven for a subasset
[16:21] on testnetv4 it still says asset activation status: waiting
[16:21] why?
[16:21] <@Tron> Yep, it needs to be voted in.
[16:21] <@Wolfsokta> We wanted to test the BIP9 activation process again as well. The more testing the better.
[16:21] We wanted to make sure that we follow the same process the Mainnet is going to go through.
[16:21] ok nice
[16:22] <@Wolfsokta> Any questions about subassets?
[16:23] are they unique?
[16:23] <@Tron> No
[16:23] <@Wolfsokta> Yes, they behave the same way as a normal asset, just live under an owned asset.
[16:23] <@Tron> Maybe I misunderstood the question. Unique with parent.
[16:23] Each subasset can have their own number issued? So PARENT/A can have 1,000 and PARENT/B can be 50?
[16:23] yes
[16:23] oooh ok that makes more sense
[16:23] <@Wolfsokta> Exactly thanks traysi
[16:24] <@Tron> And, not the same thing as "Unique Assets"
[16:24] <@Wolfsokta> The individual unique asset support is included in an upcoming phase.
[16:25] Moving onto the Segfault issue ----------------------->>>>>>>>>>> SEGFAULT
[16:25] Are we able to changes the properties of subassets after they have been created? Or is something like that specified when creating them?
[16:25] <@Tron> Yes
[16:25] can sub-assets be reassigned to other addresses while retaining control of the parent asset elsewhere?
[16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace?
[16:25] satoshi corbie @russkidooski
[16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace?
[16:26] <@Tron> Sub-assets are identical to assets after creation.
[16:26] <@Tron> Just cheaper to create, and in your "owned" namespace.
[16:26] Okay cool
[16:26] will subassets eventually have a unqiue tag? eg ASSET/SUB:1
[16:26] We have found an issue with our testnet binaries and are still looking to the issue. The issue presents itself when a user performs a reindexing of the chain. We think we have pinpointed the where the problem is and are currently working a fix. This fix will be out shortly.
[16:26] plan is to make default reissue=true and units=0 and allow increase in units on reissue
[16:26] How much is it going to be for a sub-asset?
[16:27] 100
[16:27] <@Wolfsokta> Okay, let's now focus on the SegFault issue that was discovered by Under.
[16:28] do you know what the issue was?
[16:28] <@Wolfsokta> It seems to be a build problem with the boost library.
[16:28] Still looking into though. :)
[16:29] <@Wolfsokta> We have been able to reproduce it on linux internally with 2.0.3
[16:29] yea i get the same issue on windows 10
[16:30] I saw a Bitcoin thread a while back about the seg fault error. I had it because I had conflicting versions of BDB
[16:30] static compiled on ubuntu 18.04
[16:30] <@Wolfsokta> We really appreciate you guys pulling down master and helping test.
[16:30] @Trap we will look into that also
[16:30] no problem, im just curious lol
[16:32] <@Wolfsokta> We haven't been able to build a windows version that doesn't have the segfault issue.
[16:32] <@Tron> We're dropping Windows support ;)
[16:32] lol
[16:33] Just finished setting up a new Windows test environment so we can test and validate the solution as we are working on it.
[16:33] The bdb issue is a known issue that has been around for some time. We are pretty certain it is a boost library issue, and are working quickly to get a windows build that fixes the issue.
[16:34] what did you guys do to fix the linux version?
[16:34] Once we have binaries for all supported platforms ready, hopefully tonight. No promises. We will make an announcement
[16:34] The issue has been fixed on Linux and Mac though?
[16:34] (oops sorry already answered)
[16:34] <@Wolfsokta> If anybody else gets there first with Windows please let us know what you found.
[16:34] Built the binairies on a Ubuntu 16.04 box.
[16:34] that was it?
[16:35] Yeah, we think so. 16.04 has boost 1.58 which seems to fix the issue. The build on 18.04 use boost 1.67 which seems to cause the issue.
[16:35] is there a boost 1.58 repo on 18.04?
[16:35] 18.04 used 1.65***
[16:36] I've built with boost 1.68 on arch Linux
[16:36] It worked
[16:37] wallet 2.0.x?
[16:37] @Trap, the issue is when -reindex is used.
[16:37] Oh sorry my bad
[16:37] Wallet 2.0.3
[16:38] <@Wolfsokta> For those that joined late we're discussing https://github.com/RavenProject/Ravencoin/issues/208
[16:38] 1 sec im going to boot into ubuntu and try compiling with 1.58 on 18.04
[16:39] Any other questions pertaining to the segfault?
[16:40] <@Wolfsokta> Alright, thanks everybody. Before we start the Q&A I would like to get some quick feedback on using IRC for this meeting.
[16:41] If we're going to use IRC we should take some measures to at least hide people's IPs when they join
[16:42] Yea. It is very hard to read this back.
[16:42] Also no message history
[16:42] If you disconnect and reconnect
[16:42] <@Tron> I'll throw in a vote for Discord.
[16:43] <@Wolfsokta> If you use a decent IRC client instead of the website it's not bad.
[16:43] Some of us used a VPN before we connected to IRC
[16:43] If needed we can restrict channel to Developer roles, etc for the developer meeting and open it up for general Q&A
[16:43] https://www.strawpoll.me/16247952
[16:43] poll
[16:43] Make a discord when only mods can submit links
[16:43] Where*
[16:45] Discord won the poll 5 to 2
[16:45] <@Wolfsokta> There are also a lot of IRC tools that can be used to track the meetings.
[16:45] we know
[16:46] <@Wolfsokta> We also want any developer to be able to speak.
[16:48] <@Wolfsokta> We're open to try Discord next week.
[16:48] <[kai]> perhaps you could even get a feed from this irc to discord?
[16:49] <[kai]> a feed would enable discordians to view the chat, but only contribute if they take the extra steps to come here.
[16:49] <@Wolfsokta> That's a good idea kai... Has anybody seen that working?
[16:50] <[kai]> https://github.com/reactiflux/discord-irc
[16:50] <[kai]> im sure you could make this a one way deal.
[16:51] <@Wolfsokta> I like that idea, let's try that for next week. So we'll meet here in IRC again, but it should be broadcast to Discord.
[16:53] <@Wolfsokta> Okay, we'll go with IRC next week with the broadcast to discord and re-visit for next week.
[16:54] <@Wolfsokta> Okay, let's do open Q&A for the next few mins.
[16:54] <[kai]> just a quickey, more for my curioisty, did you look at digishield?
[16:54] <[kai]> DGW solution seems solid.
[16:55] <[kai]> was just curious if it was one of the four solutions you looked at.
[16:55] <@Wolfsokta> Tron is answering... Any others Q?
[16:55] <@Tron> We briefly looked at Digishield, but our analysis was between DGW and LWMA.
[16:55] <[kai]> right on.
[16:56] <[kai]> cheers guys, see you next time.
[16:56] OPen the gates for the last 4 minutes for any other questions?
[16:58] <@Wolfsokta> Alright, thank you all for being here today and please join the development effort with us. If you have an idea, or a fix for an issue write it up and submit a pull request.
[16:59] <@Wolfsokta> Thanks again for all those that have contributed their time and effort to make Ravencoin successful. We have the BEST community.
[16:59] ^
6:59] You devs are pretty cool
[16:59] did the burn get discussed?
[16:59] <@Wolfsokta> Special thanks to Bruce, really glad you could make it with the short notice.
[17:00] <@Tron> Thanks everyone!
submitted by __pathfinder__ to Ravencoin [link] [comments]

September 21st Terracoin Update - Mandatory!!

MANDATORY UPGRADE OF THE TERRACOIN WALLET!
There is a mandatory upgrade of the Terracoin wallet in preparation for the hard fork on block 1087500 which will enable masternodes and decentralized governance.
Everyone must upgrade their wallet by block 1087500, which with current block timing is falling between the 29th and the 30th of this month!
We really need to get the word out to as many people as possible. So please post and talk to everyone you know.
This is a mandatory update which means if you continue to use the old wallet you will be on the wrong block chain and you won't be able to send or receive TRC from that wallet.
We also need to make sure that all of the mining pools (or whoever is throwing that crazy hash at TRC) have updated their wallets, otherwise the coins they mine will be worthless.
Always back up your wallet.dat file! Always back up your wallet.dat file!
Download the new wallets here: https://github.com/terracoin/terracoin
We will be using this repository going forward, but the old one has been updated as well.
The first time you run the binaries (or exes) it will create a new terracoincore folder. You can manually make it use your old terracoin app folder, but I recommend using the new folder. Stop (or close) the binaries and copy all of your files, except the peers.dat file over from the old folder into the new folder. That way you have an exact duplicate of your old data. (Except the peers.dat file, you will find .12.1.5 nodes faster without it, and you won't fully sync till you connect to a .12.1.5 masternode.)
Restart new binaries/exes.
It will say that it needs to reindex, so let it. Once it is done reindexing just sit back and wait for it to find .12.1.5 peers and masternodes. If it gives you an error saying network sync has failed, don't worry you just haven't gotten a .12.1.5 masternode yet. It will try again later.
If you are not sure how to do this please ask on one of the many forums. It is better to be safe then sorry!
I will be posting close to daily updates on which exchanges have updated their wallets and which haven't. If you see an exchange put the Terracoin wallet in maintenance that probably means they are upgrading it!
Hopefully we will have a Mac wallet out middle of next week.
In other news, the whale is now almost done with only ≈231,000 TRC left. He won't be around much longer. If you can get your TRC cheaper somewhere else then please do, but he has been consistantly selling to buy orders at .00003001 on Cryptopia. Once he is gone the price will most likely rise, so get it while you can!
Oh yeah, if you want you can set up your masternodes now, though you won't get rewards until the hard fork.
Numbers
30 days ago we were at 0.00001935 BTC (.0771 USD) and today we are at 0.00003010 BTC (.1098 USD).
A year ago we were at 0.00000442 BTC (.0026 USD).
We are ranked 321 on coinmarketcap with a market cap of $2,341,404 USD. Last week our market cap was $2,157,630 USD.
Source: http://coinmarketcap.com/currencies/terracoin/#charts
Donation Addresses
Terracoin: 12bTKJL3UiypnVQMyFXg7eCJudAyAtgh6p
Bitcoin: 14LW52k8vhHvHaGfmgx48d3su4RcKPyKcc
Terracoin Donations for the World Address
1BQH6gBzkxxyMQG3VSJCHnmVGfWu64nbPL
Public Discord Invite
https://discord.gg/r3QVQRN
Public Slack Invite
https://join.slack.com/t/terracoin/shared_invite/enQtMjQxNzU5NTY5NTIwLWJkNzIzOThhYzkyNGEyMDBmNjY2OWM2NmNhYzM0YjNmNzdlZWJkYjA3ZDgwYzkwMmMyYmM3OWNkMDQ2ZTIxYzk
Public Telegram Invite
https://t.me/terracoin
Newsletter Subscription
http://eepurl.com/cYRTwn
Youtube
https://www.youtube.com/channel/UCVt88faiKRWbMqaH_i6gXPA
submitted by clockuniverse to Terracoin [link] [comments]

Lore v2 QT on Raspberry Pi

Hello,
 
To follow up to mindphuk's excellent piece on building the headless client on Raspberry Pi (https://www.reddit.com/blackcoin/comments/6gkjrw/wip_blackpi_a_stake_device_based_on_raspberry/), I thought if anyone was interested I'd show you how to get the full QT version running on the Pi on the Jessie with Pixel desktop. This works and has been soak tested for several days now on a standard Raspberry Pi 3. I have since added some coins and it stakes a handful of times a day.
 
Running staking Lore clients paves the way for some of the future use cases of BLK utilising the Bitcoin 0.12 (and newer) core tech, including colored coins. So I'm going to leave this one going indefinitely to kickstart the number of Lore clients staking. It's certainly not mandatory but it will be good in the longer term to have a nice distribution of Lore staking clients.
 
The cross-compile which lets you create binaries for multiple platforms didn't work for the QT version on the Pi, so there is more to do than just running the binary unfortunately, as below. There are folks working on some much cleaner solutions than this for the Pi, with a custom front end, and where you won't have to do any mucking about. That is coming soon. In the meantime, if you enjoy a fiddle with such things, here's how to get this QT client working on your Pi.
 
These instructions assume you are starting from scratch with a completely blank OS.
 
Download Jessie with Pixel from: http://downloads.raspberrypi.org/raspbian/images/raspbian-2017-07-05/2017-07-05-raspbian-jessie.zip
 
Note they have since (August 2017) released a version called 'Stretch' which does not work with this guide. I'll see if I can come up with something new for that at some point and link to it here when I have. In the meantime the guide should work with the Jessie image above.
 
Unzip the file and extract the .img file to burn it onto Fresh SD card to boot from (to be safe, use 16GB or larger), using a tool like win32diskimager or Etcher.
 
Assuming you have keyboard/mouse and monitor plugged into your pi, boot it up and the Jessie Desktop will show.
 
Before we do anything else, you should increase the default swap size on the pi, as compiling certain libraries can exhaust the RAM and get stuck otherwise. To do this, launch a Terminal window and type:
 
sudo nano /etc/dphys-swapfile 
 
and Change the CONF_SWAPSIZE from 100 to:
 
CONF_SWAPSIZE=1024 
 
Exit nano with control + x to write out the file.
 
Then, run the following to restart the swapfile manager:
 
sudo /etc/init.d/dphys-swapfile stop sudo /etc/init.d/dphys-swapfile start 
 
Now, launch the browser and download the Lore 2.12 binaries for ARM here: https://mega.nz/#!k2InxZhb!iaLhUPreA7LZqZ-Az-0StRBUshSJ82XjldPsvhGBBH4 (Version with fee fix from 6 September 2017)
 
(If you prefer to compile it yourself instead, it is possible by following the instructions in the original article by Mindphuk just taking into account this is the newer version of the Lore client than when that was written (https://github.com/janko33bd/bitcoin/releases) and the versions of Boost and the Berkeley DB need to be the same as below.)
 
Double click the zip and extract the Lore binary files. Yes, at the moment they are all called 'bitcoin', not 'blackcoin' or 'Lore' - this is because the code derives from a recent bitcoin core implementation so this has not yet been updated. You can place these wherever you like.
 
In the Terminal window, change directory to where you put the binaries, e.g.:
 
cd Downloads/lore-raspberrypi-armv7-jessie-pixel chmod +x * 
 
That marks the binaries as executable.
 
Now, we need the Boost libraries installed for any of the Lore binaries to work. The project was done with Boost 1.62.0. Unfortunately the Jessie repository only goes up to 1.55, so we need to download and build 1.62 manually on the device.
wget https://sourceforge.net/projects/boost/files/boost/1.62.0/boost_1_62_0.tar.gz/download tar -xvzf download cd boost_1_62_0 sudo ./bootstrap.sh sudo ./b2 install 
 
(This will take almost 2 hours. Have a nice cup of tea and a sit down.)
 
When I came to run the binaries, I found they couldn't find Boost. Running this command fixes that:
sudo ldconfig 
 
Now we are going to install the packages which aren't already included in the default OS installation which the binaries need in order to run:
sudo apt-get install qrencode libprotobuf-dev libevent-pthreads-2.0-5 
 
Now we need to install the Berkeley Database version 6.2.23. This is the version Lore v2 uses. Bitcoin still uses 4.8 which is 10 years old! This doesn't take too long.
wget http://download.oracle.com/berkeley-db/db-6.2.23.tar.gz tar -xvzf db-6.2.23.tar.gz cd db-6.2.23/build_unix ../dist/configure --prefix=/usr --enable-compat185 --enable-dbm --disable-static --enable-cxx 
 
I find this next section of the Berkeley instructions worked better just switching to root, which can be fudged by running sudo su before the rest:
sudo su make make docdir=/usshare/doc/db-6.2.23 install chown -v -R root:root /usbin/db_* /usinclude/db{,_185,_cxx}.h /uslib/libdb*.{so,la} /usshare/doc/db-6.2.23 
 
Now we're going to go up a couple of directories to where the binaries were:
cd ../.. 
 
Then run the client!
./bitcoin-qt 
 
And there you have it. Should hopefully end up looking a bit like this: http://imgur.com/a/eEHGa
 
Using the Bootstrap can save a while syncing. Download it at: https://www.reddit.com/blackcoin/comments/6b3imq/blackcoin_bootstrapdat_up_to_block_1631800
 
Place the bootstrap.dat file into the ~/.lore directory.
 
Run ./bitcoin-qt again, it will say 'Importing Blocks' rather than 'Synchronising with Network'. My pi sync'ed fully in about 5-6 hours.
 
If you want peace of mind that Lore will always start on bootup into the Jessie w/Pixel desktop (i.e. after a power cycle), then you need to create a .desktop file in the following place.
sudo nano ~/.config/autostart/Lore.desktop 
 
And in it, enter the following (tailoring the Exec line below to the whereabouts of your bitcoin-qt file):
[Desktop Entry] Name=Blackcoin Lore Comment=Mining without the waste Exec=/home/pi/Downloads/lore-raspberrypi-armv7-jessie-pixel/bitcoin-qt Type=Application Encoding=UTF-8 Terminal=false Categories=None; 
 
Power usage and payback time
 
After a good while leaving it going by itself, the CPU load averages got down to almost zero, all of the time. Idling, the Pi uses a bit less than 3 watts. This means it would take two weeks to use one 1Kw/h of electricity.
 
If you pay e.g. 12.5 cents a unit, that's what you'd expect this to cost to run in a fortnight. That's around $0.25 a month or $3 a year. Green and cheap and helping to secure the BLK network. I paid for the year's worth of electricity in 2 days staking with 25k BLK. Makes mining look silly, huh? ;)
 
Securing your Pi
 
With staking, your wallet needs to be unlocked and as such, the keys to your wallet are on the device. In a clean and newly installed environment as described above, and if you don't allow others to use your device and there is no other software or nasties running on it, there is no real cause for concern. However, there are some basic security precautions you can take.
 
Firstly, if you have enabled SSH and are playing with your pi across your LAN (or worse, the Internet), you should immediately change the password for the default 'pi' user (which is preconfigured to be 'raspberry'). Simply log in as normal, then type:
 
passwd 
 
You'll be prompted to enter the old and the new passwords.
 
Security by default
 
Your Pi is likely, by default, to not be exposed to incoming connections from the outside world because your router is likely generating a private address range for your LAN (192.168.x.x or 10.0.x.x or 172.x.x.x) which means all incoming connections are effectively blocked at the router anyway unless you set up a 'port forward' record to allow packets arriving on certain ports to be forwarded to a specific internal IP address.
 
As for accessing your Pi across the internet, if you have set up a port forward, this likely has security ramifications. Even basic old fashioned protocols have proven in recent times to have uncaught flaws, so it's always advisable to lock down your device as much as possible, and even if you only plan to access the Pi over your LAN, install a firewall to configure this. I used one called ufw, because it's literally an uncomplicated firewall.
 
sudo apt-get install ufw sudo ufw allow from 192.168.0.0/16 to any port 22 sudo ufw --force enable 
 
This allows just port 22 (SSH) to be open on the Pi to any device on my LAN's subnet (192.168.0.x). You can change the above to a single IP address if paranoid, or add several lines, if you want to lock it down to your LAN and a specific external static IP address (e.g. a VPN service you use). To find out what subnet your router uses, just type:
 
ifconfig 
 
and you'll see on the interface you are using (either hard wired or wifi) the 192.168 or 10. or 172. prefix. Change the above rule so it matches the first two octets correctly (e.g. 10.0.0.0/16 if you're on a 10.0. address).
 
You may already use VNC to access your Pi's desktop across your LAN, this uses port 5900. Add a line like above to lock it down to an internal address. It's not a good idea to expose this port to the wider world because those connections are not encrypted and potentially could be subjected to a MITM attack.
 
You can query the status of the firewall like this:
ufw status 
 
And of course, try connecting remotely once you change the rules to see what works. You should consult the official documentation for further options: https://help.ubuntu.com/community/UFW
 
Back up & Recovery
 
There are again many ways to tackle this so I'll just speak about my basic precautions in this regard. Don't take it as a be-all-and-end-all!
 
The wallet.dat file is the key file (literally) containing all the private/public keys and transactions. This can be found in:
 
~/.lore 
 
You can navigate there using Jessie w/Pixel's own file manager or in a terminal window (cd ~/.lore). You can copy this file or, if you'd rather keep a plain text file of all your public and private keys, use the 'dumpwallet' command in the console. In Lore, go to Help > Debug Window > Console and type 'dumpwallet myfilename' where myfilename is the file you want it to spit out with all your keys in it. This file will end up in the same place you launch bitcoin-qt from.
 
The instructions earlier on, when running Lore for the first time intentionally left out encrypting your wallet.dat file because in order for the wallet to stake upon startup, it needs to have a decrypted key already. This isn't perfect, but after a power cycle, it would never stake unless you left it decrypted. So the best practice here is as soon as the wallet.dat file has left your device, i.e. you copy it to a USB stick for example, put it in an encrypted folder or drive (or both).
 
In Windows, one way is to use Bitlocker drive encryption for the entire drive. You should follow the instructions here to encrypt your flash drive before your wallet.dat is on there, and don't forget the password!!
http://infosec.nmsu.edu/instructions-guides/how-to-enable-bitlocker-to-go-for-external-hard-drives-and-usb-flash-drives/
 
On the Mac, I use a software package called Concealer to encrypt files I store on the Mac itself: http://www.belightsoft.com/products/conceale   There are almost certainly free packages with similar functionality, I have just used that one for years.
 
Either way, if you want to just make sure your USB drive is encrypted, you can do so in one-click in Finder before you put the sensitive files on it: http://lifehacker.com/encrypt-a-usb-stick-in-finder-with-a-click-1594798016
 
Note that these disk encryption methods may mean having to access the USB stick on a PC or Mac in order to retrieve the files in the event of a disaster. Be aware this may mean exposing them to more security issues if your computer is in any way compromised or someone nefarious has access to your computer. There are more 'manual' ways of backing up and recovering, such as literally writing down private/public key pairs which this guide doesn't go into, but may suit you better if paranoid about your setup.
 
Recovery
 
The wallet.dat file has everything in it you need to recover your wallet, or if you used 'dumpwallet', the file you saved out has all the keys.
 
Wallet.dat method: Install Lore as normal then replace any auto-generated wallet.dat in ~/.lore directory with your backup. If a lot of time has elapsed and many transactions have occurred since your backup, launch lore with:
./bitcoin-qt -rescan 
 
And if that doesn't do the job, do a full reindex of the blockchain:
 
./bitcoin-qt -reindex 
 
If you used the dumpwallet command, install Lore then place the file containing all the keys that you saved out in the same directory as bitcoin-qt. In Lore, go to Help > Debug Window > Console and type 'importwallet myfilename' where myfilename is that file containing all the keys. The wallet should automatically rescan for transactions at that point and you should be good to go.
 
There are a million ways to do effective security and disaster recovery, but I hope this shows you a couple of basic precautionary ways. There are discussions about better ways to stake without compromising too much security which are happening all the time and developments in this regard will happen in time.
 
In the meantime, feel free to comment with your best practices.
 
submitted by patcrypt to blackcoin [link] [comments]

The Monero Missives (weekly report) - September 16th, 2014

Original post is here
Monero Missives
September 15th, 2014
Hello, and welcome to our twelfth Monero Missive! This is our first Missive after a bit of a break whilst we thwarted two related blockchain attacks. Nonetheless, we have not sat by idly, we have been finalising and completing a brand new aspect of Monero designed to protect your privacy now and in the future: the Monero Research Lab
Major Updates
  1. The Monero Research Lab is an open collective and a multi-faceted academic group focused on the ongoing improvement of Monero. Membership is not fixed, and comes and goes as researchers become interested in Monero. This isn't a group focused on the addition of "features" to Monero, but rather the analysis and improvement of the underlying core of Monero to make sure that the theories and cryptography behind Monero continue to remain robust and sound. With that in mind, we are proud to announce the release of the first two publications out of the Monero Research Lab: MRL-0001 - A Note on Chain Reactions in Traceability in CryptoNote 2.0 - this is a research bulletin that investigates how a chain reaction could weaken the blockchain resistance properties of CryptoNote's ring signatures if low mixin values are consistently chosen MRL-0002 - Counterfeiting via Merkle Tree Exploits within Virtual Currencies Employing the CryptoNote Protocol - in this research bulletin we investigate how the block 202612 attack occurred and what it exploited, and also covers the permanent fix we have put in place
  2. This week Friday we're going to have our second #Monero-Dev Fireside Chat this week Friday, September 19th, 2014, at 10:00 EST which is 14:00 UTC and 16:00 UTC +2. For a full table of the time zones you can refer to this image, or you can use this online tool to add your city and make sure you have the correct starting time. Please note that this is a developer event, and so most of the focus will be from that perspective.
  3. To pick up where we left off with our last Missive, we are also happy to announce the availability of Monero merchandise on the Monero Gear store, powered by Zazzle. The advantage of us using Zazzle is that it is on-demand and we never have to worry about print runs or stock or anything. In return we get 15% of each sale as a "royalty" that will go towards enabling further Monero development, although Zazzle do not (yet!) accept Bitcoin or Monero. We hope to add new designs to the store on a regular basis. You can check the store out here: http://www.zazzle.com/monerogear* or take a peek at some of the new designs right here
  4. We are also pleased to announce the release of URS, a Monero project written in Go that allows you to sign messages using ring signatures as part of a group. The signature can be verified, but it cannot be determined which one of the signatories in the group did the actual signing (just like Monero uses for transactional unlinkability!). You can take a look at the project here: https://github.com/monero-project/urs, and the Bitcointalk thread dedicated to the project is here: https://bitcointalk.org/index.php?topic=768499.0
  5. We have a new tagged release, 0.8.8.4, available for download (binaries: Windows, Mac, Linux, FreeBSD). This adds the following features: Testnet: we now have an operating testnet. When using bitmonerod or simplewallet you can now use the --testnet flag to use testnet instead of mainnet. Feel free to run a mining node or just a testnet node, we will be setting up email alerts for testnet nodes when an update is pending (although having a few older testnet nodes on the network won't hurt testing). FreeBSD Compatability: Monero now works on FreeBSD out the box. We will add it to the ports tree soon. At the moment compilation is no different from regular Linux and Unix compilation, and the same dependencies apply. GPG commits: we have begun GPG-signing commits and merges. This is an important step in maintaining the integrity of the codebase, and will ensure that any compromise of our computers or even the github account won't allow a malicious attacker to push code to the repository without the unsigned commits being spotted. Verification can be done by running 'git log --show-signature', which will show and verify signatures. An example of what you should see can be found here Versioning: versioning is a lot easier, now, as tagged releases from 0.8.8.4 onwards will show version-final (eg. 0.8.8.4-final) as their version, and those built between tagged releases will show version-commithash (eg. 0.8.8.4-9088ea1). We expect this will greatly aid in debugging problems, as we can immediately pinpoint the actual version / commit a user is on. Logging: default log levels have been adjusted so that non-critical warnings are now relegated to log-level 1 and above. Apart from the normal reorganisation notifications, the only messages in red that should show up in the daemon are actual errors.
  6. We have slowed down development on the GUI to give us a bit more time to focus on the Monero internals. This is especially important given the recent attack. However, work has not come to a complete halt, and so we wanted to show off a couple of pages from the first start wizard. Bear in mind that these aren't mockups, this is the actual running Qt interface: http://i.imgur.com/jzUvSEP.jpg, http://i.imgur.com/Bj1PTcU.jpg, http://i.imgur.com/oirzi9n.jpg, http://i.imgur.com/ACDmOFJ.jpg
  7. Monero has been added to another exchange, Coin Swap. You can find the market here: https://coin-swap.net/market/XMBTC
Dev Diary
Core: because of all of the rapid changes that we had to merge into master to deal with the aftermath of the block 202612 attack, we have to bring the development branch in sync. At this stage the development branch should not be considered usable until the rebase is complete.
Build: the big change is FreeBSD compatibility, as mentioned above. A more subtle change is that the build will now first look for miniupnpc on the local system, and use that if found. If it fails to find miniupnpc it will fall back to the local copy.
Build: there is a new Makefile target, release-static, that builds statically linked binaries for redistribution. At this stage it forces 64-bit builds, once we have the embedded database working cleanly we can remove this.
Wallet: per-kb fees are nearly complete, and will be deployed to testnet within the next week or so. Once some thorough testing has been done on testnet we can merge this into master, and transaction fees can return to "normal".
Blockchain: this took a bit of a backseat with the blockchain attacks. Now that things are back to some semblance of normality, the first implementation can be written. We have chosen LMDB for the initial implementation, as this will allow us to rapidly write a Berkeley DB interface based off of it (they use similar APIs) and thus have a baseline for performance comparisons.
Core: all non-critical "errors" and warnings have been moved to log-level 1. As a developer, you may find it useful to run log-level 1 or 2 as your default.
Until next week!
submitted by fluffyponyza to Monero [link] [comments]

Moving Forward

Hey everyone,
I believe that the one of the most important we need to help boost our coin is creating nodes. For people that don't know nodes help new computers/ wallets sync up to the network (get the blockchain). Bitcoin currently has 1575+ public nodes.
At this very moment my wallet is finding 6 nodes, and during some hours of the day there is 8.
I believe that getting to 15 full time nodes would be a huge acomplishment for our coin.
Also on a side note I believe that it would also be benifical to have one place you could go to to grab and virtacoin-qt you need. (Windows, mac, and linux). The windows version is easy to find, and the mac version can be found with some digging. However personally I can't the linux version anywhere, also I am a linux file building noob. So having one of those readi ly availible would be a huge help.
So to do a quick summary, I believe we need 15+ nodes to become a better coin. You can learn how to create a node by going to https://bitcoin.org/en/full-node .
We also need a place to host virtacoin-qt for different operating systems. If someone would send me the linux one I would be happy to create a place on my site.
So thats what I am thinking right now. I will be working on more projects in the future. For now the bitcoin faucet will be inactive till I believe we have a coin that people might look twice at. We are almost there but we still have work to do. I'll do my part, will you do yours?
ps. the actual vta faucet will be up and running again before the end of the month. Leave any suggestions you have to make the coins appearance better. Nodes do cost money to keep running, I would be happy to run a couple using my own money but for others we will have to do some fundraising.
Future projects include:
Sorry for the long post
edit: formating
submitted by muchbeli to VirtaCoin [link] [comments]

Step-by-Step Guide to Making A Secure Bitcoin Wallet

I posted this in another thread, and figured it deserved its own post, since I don't think I've ever seen a simple guide like this published before. Enjoy!
1) Download the official bitcoin-qt client. It is the most reliable since it has by far the most developers. If possible, don't run it on Windows, period. Use Mac Or Linux.
2) Encrypt your wallet with a password you can remember, preferably one you don't use on any web site so that if you're hacked and your wallet is stolen, a hacker won't be able to figure out your password. You can encrypt your wallet within the bitcoin-qt program. Also, keep in mind that bitcoin-qt will not ask you for the password when the program starts up. It will only ask for the password when you try to send Bitcoins.
3) Backup your wallet.dat everywhere. Look up on Google to find where this file is. It is different depending on your operating system. Back up to external hard drives, jumpdrives, Gmail, Dropbox, etc. More is better, assuming you're using a good password.
4) Once bitcoin-qt is fully synced with the network, you will see a green check mark in the bottom-right of the program. Now you can send funds to your Bitcoin receive address! As soon as you send them, you will see a notification box pop up from bitcoin-qt telling you that you received funds. Technically, you can transfer the bitcoin even before the blockchain syncs and you get the green checkmark, but you will have to wait much longer to see that your Bitcoin arrived safely. I like to see it immediately, so that's why I wait for the check.
5) You can take your wallet.dat file, and import it into another computer running bitcoin-qt. If it synchronizes with the blockchain and picks up your transactions and correct balance, then you know you did it right! You can even leave your wallet running on two (or more) computers if you want! I keep it on two computers, myself. Remember to make a new backup of your wallet.dat file every couple of months or so just to be safe. If you forget, it's fine. An old backup will work, it's just that only 100 addresses are stored in the wallet file, and if you go over that amount the wallet may add new private keys that you will want in your backups. So back up at least once every 100 transactions, in case these transactions all used unique "change" addresses. If you don't understand how this works, type Bitcoin change address on Google. Just know to back it up every once in awhile and you will be fine.
Good luck! But you won't need it...if you follow this guide your bitcoin will be ridiculously safe. :)
submitted by joseph11h to Bitcoin [link] [comments]

Step-by-Step Guide to Keeping your Dogecoin Secure

Dogecoin subreddit has exploded over the past few days, and I realized that for many people around here, it's your first time hearing about a cryptocurrency and even probably never owned a bitcoin before.
One of the biggest problems with Bitcoin/Dogecoin is that it is online, and thus can be hacked/stolen by millions of hackers all over the world. Hence, it is of utmost importance that you keep your Dogecoins safe! Hope this helps you!
1) Download the official dogecoin-qt client. It is the most reliable since it has by far the most developers. If possible, don't run it on Windows, period. Use Mac Or Linux. Also try to avoid online wallets.
2) Encrypt your wallet with a password you can remember, preferably one you don't use on any web site so that if you're hacked and your wallet is stolen, a hacker won't be able to figure out your password. You can encrypt your wallet within the dogecoin-qt program. Also, keep in mind that dogecoin-qt will not ask you for the password when the program starts up. It will only ask for the password when you try to send Bitcoins.
3) Backup your wallet.dat everywhere. Look up on Google to find where this file is. It is different depending on your operating system. Back up to external hard drives, jumpdrives, Gmail, Dropbox, etc. More is better, assuming you're using a good password. Here's a way to keep your .dat files safe on Dropbox @ http://lifehacker.com/5794486/how-to-add-a-second-layer-of-encryption-to-dropbox
4) Once dogecoin-qt is fully synced with the network, you will see a green check mark in the bottom-right of the program. Now you can send funds to your Dogecoin receive address! As soon as you send them, you will see a notification box pop up from dogecoin-qt telling you that you received funds. Technically, you can transfer the dogecoin even before the blockchain syncs and you get the green checkmark, but you will have to wait much longer to see that your Dogecoin arrived safely.
5) You can take your wallet.dat file, and import it into another computer running dogecoin-qt. If it synchronizes with the blockchain and picks up your transactions and correct balance, then you know you did it right! You can even leave your wallet running on two (or more) computers if you want! Remember to make a new backup of your wallet.dat file every couple of months or so just to be safe. If you forget, it's fine. An old backup will work, it's just that only 100 addresses are stored in the wallet file, and if you go over that amount the wallet may add new private keys that you will want in your backups. So back up at least once every 100 transactions, in case these transactions all used unique "change" addresses. If you don't understand how this works, type "Bitcoin change address" on Google (Bitcoin works the same as Dogecoin). Just know to back it up every once in awhile and you will be fine.
Good luck! But you won't need it...if you follow this guide your dogecoins will be ridiculously safe. :)
If this helped you, feel free to tip @ DRUkJdqgJuWwStJGV2L2yt4vKcgWUg4U2M
submitted by bakedric3 to dogecoin [link] [comments]

Bitcoin-Qt on Mac questions

I am very new to Bitcoin. I downloaded the recommended software for BTC for my Mac, Bitcoin Core (Bitcoin-Qt on the icon) and I am beginning to use it. It has said "Synchronizing with network," at the bottom of the window for the past four hours and is on some arbitrary number like 138637 out of 279000 of unblocking... whatever that means...
Anyways, I made a transfer from coinbase.com to the wallet on Bitcoin-Qt and it has a receipt saying it went through, but because my Bitcoin-Qt wallet is "out of sync," nothing is showing up.
I guess my question(s) is (are), has anyone used this software before and is experiencing what I am experiencing? Is this normal? How long does it take for it to completely synchronize? Will my BTC transfer completely to my wallet after this has occurred?
Thanks
submitted by Carson325 to Bitcoin [link] [comments]

Wallets, wallets, wallets.. Instead of copying, an idea for innovation?

Good morning/afternoon/evening DevShibes,
I have an idea. I understand that wallets can't sync the same doge addresses on multiple devices due to change addresses and other issues. I've seen that the Dogecoin-qt, and Android wallets are forks of the bitcoin wallets. The issue with using multiple devices is that there's no way for the wallets to talk to eachother. So, I was thinking- can't an encrypted database be setup, using a users Google credentials for example.. it would still be passphrase encrypted (then doubly protected with the users google credentials..) So more or less would be stored in Drive.. each client could authenticate via Google's drive API right? I don't really know about this enough to know what's possible, I just see all these services doing similar things.
So, anyways, a universal, encrypted .db that is generated/synced between the Dogecoin-qt on the Windows/Linux(mac?) desktops, Android, and then iOS. It could be required that users use/generate a strong passphrase (min. 1 characters, autogenerate could produce a string of 4-5 letter dictionary words maybe?) Then maybe using a combination of authentication, 2-factor, and/or passphrase confirmation the clients via p2p/drive can securely transmit/sync private keys? Or maybe the Android/iOS (light?) wallets can sync/confirm keys and/or balances with the qt wallets that are full blockchain synced?
Does any of this make sense? I know we're like the 37th coin to be developed (citation needed.. or correction since I just made that up) but can't we innovate this wallet tech? Right now I'm not going to place any amount of Doge on a smartphone that isn't backing up automatically and/or syncing regularly. What if I drop it in a toilet or it gets run over.
Hopefully this isn't seen as FUD or me telling the devs what to do.. just thinking out loud. :)
Cheers guys, -pd
submitted by packetdoge to dogecoindev [link] [comments]

May 15th report

Qt-Wallets:
Emc2 coin got new wallets for both Mac and Windows. New version 0.9.1.0 syncs immediately after install and 0.9.2.0 implement test net. The significance of this build is that it is the first build made in 3 years, and also the first build released by the new development team. emc2-qt-wallet code has not changed since May 2014, but operating systems have, so what seemed to be an easy and straight forward task of a few days turned into 4 weeks or more of hard working job. The team had to go through the effort of not just adapting and building development and test environments but also diving deep into the code. Going forward next releases will be far easier. In addition to wallets we also manage to create a new test net. With wallets out, test net and 35 nodes, we can say we have accomplished the second step in our road map which is taking care of the infrastructure. Of course this is ongoing process, the core team will continue with improvements. We plan to make: Qt wallets v0.9.2.1 – new looking filed ~ in 3 weeks Qt wallets v0.13.3.0 – alignment with ltc core libraries ~ in 5-6 weeks
Releases after that will include more features as well as security improvements.
Web wallet, API, mobile wallets:
The next stop on our roadmap is: web wallet, api, and mobile wallets Mobile wallets are ready, but they rely on web wallet and API which is one big package. Since web development had to help infrastructure a little bit, we need to update our target release date and set expectations for the end of June.
Emc2 Store: 4you.emc2.foundation
Backend of emc2 Magento store is ready. SyncItGroup assigned two designers to take care of the front end. They are waiting on emc2 web wallet and API to implement emc2 coin as a payment method. We are thinking of releasing dev url this week to Slak users for testing, and to have production release in the first week of June. This release would only have fiat payments. SyncItGroup will finish Magento plug-in before emc2 API for sure, so as soon as our web wallet is ready a store will get emc2 payment option. But even without coin integration it is good for the store to be online for review and testing.
Crowdfunding: emc2me.io
Last time we posted report we were still in negotiation process. Now developers are chosen, the budget is ready. PM is finalizing specification. We will have kick of meeting with devs on Friday. In next two weeks I will loop with our marketing experts and all other members willing to take part and to push this important platform to the surface.
Business development:
Voxtel
– We held the meeting with Voxtel on April 28th. The fact that it was 4 hour long tells enough. First meetings are always risky bit this one was with great synergy. They are willing to move into blockchain. Now what would be next is for us to review all their products and to help them implement the coin for products that are good match. For others that are not we are thinking of releasing new coin for Voxtel as side chain to emc2. Emc2 coin will benefit from fees. Important: this is not quick approach, but since Voxtel is established and well connected business it is important that we keep moving along. You will feel the results.
Other: Every day we get interesting leads via our website and LinkedIn. We are talking to two more business to form a common project that would consume emc2 coin, and maybe even launch ICO if needed. Very interesting stuff. Let me have a clear picture and the view, and I will share it with you.
Media:
Einsteinium Foundation has secured relations with several very important media. They are waiting on our content.
Blog: Check some interesting articles:
https://www.emc2.foundation/emc2-blog/2017/5/11/who-missed-bitcoin-and-wants-to-start-over-again-1 Who missed bitcoin and wants to start over again?
https://www.emc2.foundation/emc2-blog/2017/5/11/of-bubbles-and-metaphors Of bubbles and metaphor
https://www.emc2.foundation/emc2-blog/2017/5/11/btc-ad-astra Btc ad astra
What do you think?
We will inform wider crypto audience with what is going on with Einsteinium via newsletters during the week.
submitted by djnocide to einsteinium [link] [comments]

Can someone explain this huge outbound transaction I'm seeing in my Blockchain.info wallet?

SOLVED, see edit below, hurr durrr
OK, remaining calm and telling myself there's a chance that this could just be one of bitcoin's idiosyncrasies, but at the moment it seems to me that I've transferred effectively all of my BTC worth to an unknown address. Basically, I sent .2 BTC to bitcoinbuilder from my unsynchronized copy of bitcoin-qt (Hadn't opened it in a month or two) and the transaction went through. About a half hour later I dumped the private keys of the two deposits in my wallet and uploaded them to a new wallet on blockchain.info. Blockchain recognized the .2BTC I sent to bitcoinbuilder immediately and deducted it, but look! Instead of it being a .2BTC withdrawl, it's the entire value of my big deposit from November: http://i.imgur.com/6wAIm7x.png
If you check out those two addresses that were sent to, the first is 2.014829 to an unknown address and the second is .2 to my bitcoinbuilder address. I did not send to the unknown address. Order of events, for clarity:
  1. Wanted to get in on some bitcoinbuilder action. Fired up bitcoin-qt and sent .2BTC to my bitcoinbuilder address.
  2. Saw coins appear in bitcoinbuilder, but bitcoin-qt looked like it was going to take a week to sync so I decided to spin up a blockchain wallet.
  3. Uploaded private keys for a .001 bitfaucet deposit from 2011 and a 2.214839 deposit from 2013. Did notice that when I pasted the private key for the big deposit into the blockchain uploader window, the value for it still said "0".
  4. Blockchain took my private keys no problem, but then showed me that it registered the .2 I sent to bitcoinbuilder as .2 + 2.014829.
  5. Began staring at the cover of my Hitchhiker's Guide. Decided to post here.
I'm aware that Bitcoin doesn't send "X amount" to someone but instead forwards a previous transaction or part of it as the next transaction in line, or something like that. But I don't fully understand how that works, I'm just hoping this is a temporary artifact of that. In the meantime I'm scanning my Mac with ClamAV for Pony or Cointhief, just in case. But I would really REALLY appreciate possible explanations for this and what might be happening. Thanks :(
edit- A big THANK YOU to responders in this thread, especially CorgiDad and AlmostSawTheEnd for their clarity and patience. Who says that dogecoin has the best community? You guy piled onto my question in a very helpful manner within a half hour. Gracias!
submitted by freeradicalx to Bitcoin [link] [comments]

Bitcoin Core 0.11.0 released | Wladimir J. van der Laan | Jul 12 2015

Wladimir J. van der Laan on Jul 12 2015:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Bitcoin Core version 0.11.0 is now available from:
<https://bitcoin.org/bin/bitcoin-core-0.11.0/>
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
<https://github.com/bitcoin/bitcoin/issues>
The entire distribution is also available as torrent:
magnet:?xt=urn:btih:82f0d2fa100d6db8a8c1338768dcb9e4e524da13&dn;=bitcoin-core-0.11.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F 
Upgrading and downgrading

How to Upgrade
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 (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrade warning
Because release 0.10.0 and later makes use of headers-first synchronization and
parallel block download (see further), the block files and databases are not
backwards-compatible with pre-0.10 versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility. There are no
known problems when downgrading from 0.11.x to 0.10.x.
Important information

Transaction flooding
At the time of this release, the P2P network is being flooded with low-fee
transactions. This causes a ballooning of the mempool size.
If this growth of the mempool causes problematic memory use on your node, it is
possible to change a few configuration options to work around this. The growth
of the mempool can be monitored with the RPC command getmempoolinfo.
One is to increase the minimum transaction relay fee minrelaytxfee, which
defaults to 0.00001. This will cause transactions with fewer BTC/kB fee to be
rejected, and thus fewer transactions entering the mempool.
The other is to restrict the relaying of free transactions with
limitfreerelay. This option sets the number of kB/minute at which
free transactions (with enough priority) will be accepted. It defaults to 15.
Reducing this number reduces the speed at which the mempool can grow due
to free transactions.
For example, add the following to bitcoin.conf:
minrelaytxfee=0.00005 limitfreerelay=5 
More robust solutions are being worked on for a follow-up release.
Notable changes

Block file pruning
This release supports running a fully validating node without maintaining a copy
of the raw block and undo data on disk. To recap, there are four types of data
related to the blockchain in the bitcoin system: the raw blocks as received over
the network (blk???.dat), the undo data (rev???.dat), the block index and the
UTXO set (both LevelDB databases). The databases are built from the raw data.
Block pruning allows Bitcoin Core to delete the raw block and undo data once
it's been validated and used to build the databases. At that point, the raw data
is used only to relay blocks to other nodes, to handle reorganizations, to look
up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or
for rescanning the wallet. The block index continues to hold the metadata about
all blocks in the blockchain.
The user specifies how much space to allot for block & undo files. The minimum
allowed is 550MB. Note that this is in addition to whatever is required for the
block index and UTXO databases. The minimum was chosen so that Bitcoin Core will
be able to maintain at least 288 blocks on disk (two days worth of blocks at 10
minutes per block). In rare instances it is possible that the amount of space
used will exceed the pruning target in order to keep the required last 288
blocks on disk.
Block pruning works during initial sync in the same way as during steady state,
by deleting block files "as you go" whenever disk space is allocated. Thus, if
the user specifies 550MB, once that level is reached the program will begin
deleting the oldest block and undo files, while continuing to download the
blockchain.
For now, block pruning disables block relay. In the future, nodes with block
pruning will at a minimum relay "new" blocks, meaning blocks that extend their
active chain.
Block pruning is currently incompatible with running a wallet due to the fact
that block data is used for rescanning the wallet and importing keys or
addresses (which require a rescan.) However, running the wallet with block
pruning will be supported in the near future, subject to those limitations.
Block pruning is also incompatible with -txindex and will automatically disable
it.
Once you have pruned blocks, going back to unpruned state requires
re-downloading the entire blockchain. To do this, re-start the node with
  • -reindex. Note also that any problem that would cause a user to reindex (e.g.,
disk corruption) will cause a pruned node to redownload the entire blockchain.
Finally, note that when a pruned node reindexes, it will delete any blk???.dat
and rev???.dat files in the data directory prior to restarting the download.
To enable block pruning on the command line:
  • - -prune=N: where N is the number of MB to allot for raw block & undo data.
Modified RPC calls:
    • getblockchaininfo now includes whether we are in pruned mode or not.
    • getblock will check if the block's data has been pruned and if so, return an
error.
  • - getrawtransaction will no longer be able to locate a transaction that has a
UTXO but where its block file has been pruned.
Pruning is disabled by default.
Big endian support
Experimental support for big-endian CPU architectures was added in this
release. All little-endian specific code was replaced with endian-neutral
constructs. This has been tested on at least MIPS and PPC hosts. The build
system will automatically detect the endianness of the target.
Memory usage optimization
There have been many changes in this release to reduce the default memory usage
of a node, among which:
    • Accurate UTXO cache size accounting (#6102); this makes the option -dbcache
    precise where this grossly underestimated memory usage before
    • Reduce size of per-peer data structure (#6064 and others); this increases the
    number of connections that can be supported with the same amount of memory
    • Reduce the number of threads (#5964, #5679); lowers the amount of (esp.
    virtual) memory needed
Fee estimation changes
This release improves the algorithm used for fee estimation. Previously, -1
was returned when there was insufficient data to give an estimate. Now, -1
will also be returned when there is no fee or priority high enough for the
desired confirmation target. In those cases, it can help to ask for an estimate
for a higher target number of blocks. It is not uncommon for there to be no
fee or priority high enough to be reliably (85%) included in the next block and
for this reason, the default for -txconfirmtarget=n has changed from 1 to 2.
Privacy: Disable wallet transaction broadcast
This release adds an option -walletbroadcast=0 to prevent automatic
transaction broadcast and rebroadcast (#5951). This option allows separating
transaction submission from the node functionality.
Making use of this, third-party scripts can be written to take care of
transaction (re)broadcast:
    • Send the transaction as normal, either through RPC or the GUI
    • Retrieve the transaction data through RPC using gettransaction (NOT
    getrawtransaction). The hex field of the result will contain the raw
    hexadecimal representation of the transaction
    • The transaction can then be broadcasted through arbitrary mechanisms
    supported by the script
One such application is selective Tor usage, where the node runs on the normal
internet but transactions are broadcasted over Tor.
For an example script see [bitcoin-submittx](https://github.com/laanwj/bitcoin-submittx).
Privacy: Stream isolation for Tor
This release adds functionality to create a new circuit for every peer
connection, when the software is used with Tor. The new option,
-proxyrandomize, is on by default.
...[message truncated here by reddit bot]...
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009400.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

syncing Bitconnect qt wallet on a mac for staking How to Setup and Sync Bitconnect-Qt Wallet on macOS How to make your Bitconnect QT wallet sync on Mac How to Sync Your Bitcoin or Dodgecoin Wallet prevent bitcoin-qt client from crashing on the mac

The wallet will always say out of sync the first time you open it, as it has to download the blockchain. This process can take up to 4 hours or so depending on your internet speed and number of connections to our network, so please be patient. This free Mac app was originally produced by July IGHOR. Centrabit AG. Qtbitcointrader_beta.dmg is the frequent file name to indicate this application's installer. The most popular version among Qt Bitcoin Trader for Mac users is 1.0. Our built-in antivirus scanned this Mac download and rated it as 100% safe. This free Mac app is an intellectual property of Qt sync. The following versions: 0.4 and 0.3 are the most frequently downloaded ones by the program users. QT Sync for Mac belongs to Audio & Video Tools. The bundle identifier for QT Sync for Mac is com.qtsync.qtsync. This free program was developed to work on Mac OS X 10.4.0 or later. Big Sur, the latest Mac operating system, is officially macOS 11. Meaning that after almost 20 years, OS X is dead and gone. 02/09/2018 · Wallet not syncing – Troubleshooting an out of sync QT wallet Internet connection and Firewall issues. My situation.... Bitcoin QT is taking for EVER to sync with the network. I need to sell a few of my Bitcoins today. But I am afraid to do so while QT is 'out of sync.' Is it generally safe or unsafe to do this? Thanks in advance, you awesome people, you. P.S. if this is the wrong section on r/Bitcoin, please kindly redirect my idiocy.

[index] [16184] [41633] [4200] [2701] [2597] [22741] [21618] [2426] [47373] [49617]

syncing Bitconnect qt wallet on a mac for staking

Find out why Close. Bitcoin Core Wallet sync 100% result Sabah RcDrone. Loading... Unsubscribe from Sabah RcDrone? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 250. Loading ... You are using the Mac OSX OS and your bitcoin-qt client is crashing when opening? Then watch this tutorial on how to solve this issue. The bitcoin talk topic... Quick Fix Bitconnect QT Wallet Out of Sync 🖥️ Mac OSX - Duration: 5:30. Nad Daniels 2,327 views. 5:30 . Fixing The PRO Wallet Out Of Sync Message - Duration: 24:09. Cryptocurrency Group ... Find out why Close. Increase slow download and sync of bitcoin blockchain on Mac Daniel's Tutorials ... How to install Ethereum and Mist with Fast Sync + Add EtherDelta and ENS - Duration: 23:09 ... Find out why Close. How to Sync Your Bitcoin or Dodgecoin Wallet Radioactive Chipmunks. Loading... Unsubscribe from Radioactive Chipmunks? Cancel Unsubscribe. Working... Subscribe Subscribed ...

#