Where do I find the *actual* blockchain size? - Bitcoin

In early 2013, it became a common belief that new Bitcoin users should not be recommended Bitcoin-QT, the full node client. Bitcoin.org was changed to no longer exclusively recommend it. Two years later, the block size conservatives are saying the drop in full node count was due to block size

I distinctly remember that the recommending of Bitcoin-QT to new Bitcoin users became a faux pas in early 2013. It was claimed that regular people should download and install an SPV client like Multibit.
Predictably, there was a large drop in the full node count, as the wallet market became dominated by a large number of new, light clients, and the most trafficked Bitcoin website, bitcoin.org, stopped exclusively recommending people to install Bitcoin-QT.
Now, we have important developers like Luke-Jr claiming that this 95% drop in full node count can be mainly attributed to the growing size of the block chain, despite the fact that the drop began right when light clients began being recommended..
EDIT to add some data:
This is the image that GMaxwell and Peter Todd, two individuals who are conservative about the block size (in particular Peter Todd, who's been warning about increasing the 1 MB size limit since 2013), have linked to to make their point about the full node count:
http://i.imgur.com/EL0zHRe.jpg
Up until at least March 18, 2013, the only client recommended to visitors of bitcoin.org was Bitcoin-QT, and an installation link for it was provided right on the landing page:
https://web.archive.org/web/20130318211940/http://bitcoin.org/
The WayBack Machine shows that by March 25th, 2013, this had changed, and a 'Choose Your Wallet' button appeared on Bitcoin.org/:
https://web.archive.org/web/20130513214959/http://bitcoin.org/en/
From March 25th 2013 onward, the number of non-full-node wallets recommended by bitcoin.org increased, in response to a general increase in the number of high quality and/or well marketed light and mobile wallets on the market.
Now a days, Bitcoin-QT is one of twelve clients displayed on bitcoin.org's Choose Your Wallet page:
https://bitcoin.org/en/choose-your-wallet
Other than Bitcoin-QT and Bitcoin Armory, all of them are non-full-node clients.
This shift, from a wallet market where only Bitcoin-QT was available and recommended to one that is increasingly diverse and dominated by light clients, coincides with the point (Spring 2013) where we start seeing a rapid decline in the full node count.
submitted by aminok to Bitcoin [link] [comments]

Going to increase block size 1MB per year (by hand) in Bitcoin QT on my full bitcoin node starting 01 jan 2016.

I'm already running bitcoin-qt with the new block size (=block size limit) without relaying (port closed) on a different computer, with:
minrelaytxfee=0.0001
limitfreerelay=0
Block size=block size limit=max block size: largest block that will be excepted by a full bitcoin node.
The current solution to the block size problem tries to solve the problem forever including looking into the far future and this is wrong for such a complicated issue. What we should strive for is a MINIMAL solution that nevertheless implements a forever increasing block size. The only drawback will be that we will need a final hard fork let's say 5 years from now. Because an exponential increase is too slow for a short term solution it should be a linear increasing block size, a final solution can be something exponential.
So again I'm proposing the 1MB per year block size increase as the temporary compromise minimal solution and we should implement it as soon as possible:
1 jan 2016: 2 MB
1 jan 2017: 3 MB
1 jan 2018: 4 MB
1 jan 2019: 5 MB
1 jan 2020: 6 MB
Etc.
Compiled bitcoin core (changing the max block size by hand every year) like this on Ubuntu Linux:
Change /home/user EVERYWHERE into where you want to install Bitcoin Core.
The hardest part: you need to install Berkeley db 4.8
cd /home/user
wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef db-4.8.30.NC.tar.gz' | sha256sum -c
tar -xvf db-4.8.30.NC.tar.gz
cd db-4.8.30.NC/build_unix
mkdir -p build
../dist/configure --disable-shared --enable-cxx --with-pic --prefix=/home/usedb-4.8.30.NC/build_unix/build
make install
cd /home/user
wget https://bitcoin.org/bin/bitcoin-core-0.11.0/bitcoin-0.11.0.tar.gz
tar -xvf bitcoin-0.11.0.tar.gz
cd /home/usebitcoin-0.11.0/src/consensus
Use your favorite editor to change block size or execute the line below:
mv consensus.h consensus.h_back ; sed s/"MAX_BLOCK_SIZE = 1000000"/"MAX_BLOCK_SIZE = 2000000"/ consensus.h_back > consensus.h
cd /home/usebitcoin-0.11.0
./configure CPPFLAGS="-I/home/usedb-4.8.30.NC/build_unix/build/include/ -O2" LDFLAGS="-L/home/usedb-4.8.30.NC/build_unix/build/lib/" --with-gui
make
bitcoind in bitcoin-0.11.0/src, bitcoin-qt in bitcoin-0.11.0/src/qt (or execute sudo make install)
submitted by sumBTC to Bitcoin [link] [comments]

How I synced on a 2013 ultrabook in a few days

Note: I don't know exactly how long it took because I didn't do it in one go. I guess it was like 4,5 days doing it only at night. At some points(2015Q3, 2018Q2) it slows down and ETA goes up to 16 weeks or something.
The main bottleneck is IO. My 2013 mobile i3 has enough processing power to sync, I only used 3 threads and most of the time only one was close to 100%. The two directories that need to be written and read from intensively are chainstate and blocks/index. I pruned to 2GB and chainstate didn't go much over 3GB during the entire process. blocks/index is like 100MB.
The best solution is to move chainstate and blocks/index to a ramdisk. If you don't have enough ram the linux kernel has a thing called zram. Zram creates a compressed swap(cache) file in ram, this effectively increases your ram size at the cost of a bit of processing power and access speed(of the compressed part). On my machine I can net a bit more than 1GB of extra ram. That's right, with linux you can download more ram! The second best solution is to leave chainstate and block/index on a sdd. From what I've tested it should take up between 5 whole days and 2 weeks.
With regards to config, I didn't see much benefit in increasing the db cache over the default 450MB in bitcoin-qt. If I recall correctly, smaller prune sizes make chainstate larger.
After the initial sync keeping up to date is very easy on resources. You can catch up a week in a few minutes. At the moment bitcoind is using 400MB but I'm still working on bringing that number down.
Remember: If you want safety or if you want to help the network you need o run a full node. A full node is a node that verifies all transactions. A pruned node is a full node.
Edit: bitocoind really likes to hover around 400MB, sometimes it gets higher than that, some times it get's lower. A lot of that is data, not code, so if you start running out of ram your OS should drop those pages and get down to 250~300MiB. If you really want the memory to be this low all the time, on linux, you can either: Use cgroups to set the swappiness of the process to 99 so all data gets swapped but not code does; Use systemd and set MemoryLimit=300MiB(for example) so almost all data gets swapped but no code. I don't think any of those options are worth the small setup hassle.
submitted by nothing_works4me to Bitcoin [link] [comments]

Creamcoin 0.18.0.0 – following Bitcoin’s tale

Creamcoin 0.18.0.0 – following Bitcoin’s tale

06/08/2019 3 min read📷216SHARES216VIEWSShare on Twitter
When new Creamcoin was designed, we had in mind not only a coin that would hold parity with any cryptocurrency, but something that would demonstrate the extra-special capabilities of a decentralized ledger, capable to introduce, help and bring it further to the regular people. Blockchain developing is unstoppable complex process with endless possibilities. Integration of applications on such a technology could achieve better, secure pass of value.
0.18.0.0

On August 5th, 2019 Creamcoin code was successfully updated to the latest Bitcoin version 0.18.0
https://github.com/creamcoin/cream/
With this latest release, we proved that Creamcoin itself it’s not a sort of a tenant to the Bitcoin. Much easier to apply and to pursue the main purpose of existence and to create further innovations in our Cream Line. The new release brings tremendous performance improvements, as well as integration will be much easier for any platform, exchange or integrator. Wallets are available to Releases tab on github
WALLETS

Multi-wallet support

Cream Core now supports loading multiple, separate wallets. The wallets are completely separated, with individual balances, keys and received transactions. Multi-wallet is enabled by using more than one -wallet argument when starting Creamcoin, either on the command line or in the Cream config file. In Creamcoin-Qt, only the first wallet will be displayed and accessible for creating and signing transactions. GUI selectable multiple wallets will be supported in a future version. This feature will continue to be refined with later updates, as there are still some known issues in using the GUI to access the “multiwallet” command. The most notable is that you can’t use coin control features with multiple wallets loaded, or else you will likely retain the wrong wallet when attempting to switch wallets.
When running Cream Core with multi-wallet, wallet-level RPC methods must specify the wallet for which they’re intended in every request. HTTP RPC requests should be send to the :/wallet// endpoint, for example 127.0.0.1:8332/wallet/wallet1.dat/. bitcoin-cli commands should be run with a -rpcwallet option, for example [bitcoin-cli -rpcwallet=wallet1.dat getbalance] A new node-level [listwallets] RPC method is added to display which wallets are currently loaded. Starting command for both wallets should look like this: [creamd -daemon -wallet=wallet1.dat -wallet=wallet2.dat]

Hardware Wallet native compatibility

With a new release of Cream Core the possibility is added in the form of use hardware wallets (Ledger, Trezor, Digital BitBox, KeepKey, Coldcard), but this process is manual and involves the use of Hardware Wallet Interaction (HWI) tool and it needs HW support and addition of Cream in the future, which is not excluded from roadmap. This is a great news for everyone who use Cream Core, and want extra security. Only applies to those who can use command line/CLI (for now), and when some of Hardware wallets actually supports Cream.

SegWit 4MB limit

SegWit replacing the block size limit with a block “weight” limit, allowing up to 4 megabytes of transaction data, and giving a substantial boost in the transaction capacity of the Cream network.

www.creamcoin.com

In the same with the new code update, Creamcoin Team is doing major shifting power, migrating the marketing and promotion activities, from our news site cream.technology to our main page www.creamcoin.com. We will come up with additional statement in this matter, so our supporters and followers have better perspective of Cream Line and the products of it.
In the meantime we are looking into new ways that developers can enhance the capabilities of the Creamcoin protocol, integration of decentralized exchange functionality, lightning network and number of other options that would allow for different types of conditional sends of Creamcoin assets. We are inviting any individual, platform, exchange or integrator who would like to submit recommendations or feature requests, feel free to contribute to the Creamcoin Github.
By Cream Team
submitted by creamcointeam to u/creamcointeam [link] [comments]

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

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

Groestlcoin 6th Anniversary Release

Introduction

Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

Windows
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer.
OSX
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

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

Download

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

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.

Features

Live Version (Not Recommended)

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

Download

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

Source

ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).

Features

Usage

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

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).

Features

Download

Source

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

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

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

Features

Download

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

Source

ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.

Features

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

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

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

I support allowing very large blocks, as long as they grow under conditions of rising fee pressure (provided by an elastic block size cap), but this image linked to by GMaxwell deserves serious consideration

I support allowing very large blocks, as long as they grow under conditions of rising fee pressure (provided by an elastic block size cap), but this image linked to by GMaxwell deserves serious consideration submitted by aminok to Bitcoin [link] [comments]

Gridcoin 4.0.5.0-Leisure "Elizabeth" Release

The core developers are pleased to present the 4.0.5.0 Elizabeth milestone leisure release. This is a leisure release primarily aimed at non-mandatory items and bug fixes leading up to the Fern mandatory milestone release.
This release also enables us to whitelist teams other than Gridcoin as a stepping stone for the implementation of no team requirement in Fern.
Enjoy!
https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/4.0.5.0
Changelog...

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

Updated (Dec 2017). A collection of evidence regarding Bitcoin's takeover.

REPOSTED AS TITLE WAS INCORRECTLY PHRASED.
A month back on November 22 I posted this https://www.reddit.com/btc/comments/7eszwk/links_related_to_blockstreams_takeover_of_bitcoin/
I have added a lot more links now, please give feedback on what else I could add for next time I will add (few weeks/month).
  1. The history between btc and bitcoin Archive link
yours.org link
  1. A brief and incomplete history of censorship in /Bitcoin Archive link
  2. User posts on bitcoin about 6900 BTC that theymos stole, post gets removed. Archive link
  3. Go to /noncensored_bitcoin to see posts that have been censored in /bitcoin
  4. Theymos caught red-handed - why he censors all the forums he controls, including /bitcoin Archive link
  5. User gets banned from /bitcoin for saying "A $5 fee to send $100 is absolutely ridiculous" Archive link
  6. Greg Maxwell caught using sockpuppets Archive link
  7. Wikipedia Admins: "[Gregory Maxwell of Blockstream Core] is a very dangerous individual" "has for some time been behaving very oddly and aggressively" Archive link
  8. Remember how lightening network was promised to be ready by summer 2016? https://coinjournal.net/lightning-network-should-be-ready-this-summe Archive link
  9. rBitcoin moderator confesses and comes clean that Blockstream is only trying to make a profit by exploiting Bitcoin and pushing users off chain onto sidechains Archive link
  10. "Blockstream plans to sell side chains to enterprises, charging a fixed monthly fee, taking transaction fees and even selling hardware" source- Adam Back Blockstream CEO Archive link Twitter proof Twitter Archive link
  11. September 2017 stats post of bitcoin censorship Archive link
  12. Evidence that the mods of /Bitcoin may have been involved with the hacking and vote manipulation "attack" on /Bitcoin. Archive link
  13. bitcoin mods removed top post: "The rich don't need Bitcoin. The poor do" Archive link
  14. In January 2017, someone paid 0.23 cents for 1 transaction. As of December 2017, fees have peaked $40.
  15. Death threats by Bitcoin for cashing out
  16. Bitcoin is a captured system
  17. Bot attack against bitcoin was allegedly perpetrated by its own moderator and Blockstream’s Greg Maxwell
  18. Remember: Bitcoin Cash is solving a problem Core has failed to solve for 6 years. It is urgently needed as a technical solution, and has nothing to do with "Roger" or "Jihan".
  19. Bitcoin Cash has got nothing new.
  20. How the Bilderberg Group, the Federal Reserve central bank, and MasterCard took over Bitcoin BTC More evidence
  21. Even Core developers used to support 8-100MB blocks before they work for the Bankers Proof
  22. /Bitcoin loves to call Bitcoin Cash "ChinaCoin", but do they realize that over 70% of BTC hashrate comes from China?
  23. /bitcoin for years: No altcoin discussion, have a ban! /bitcoin now: use Litecoin if you actually need to transact!
  24. First, they said they want BCH on coinbase so they could dump it. Now they are crying about it because it's pumping.
  25. Luke-Jr thinks reducing the blocksize will reduce the fees..
  26. Core: Bitcoin isn't for the poor. Bitcoin Cash: we'll take them. Our fees are less than a cent. Core: BCash must die!
  27. How The Banks Bought Bitcoin. The Lightning Network
  28. Big Blocks Can Scale, But Will It Centralize Bitcoin?
  29. "Fees will drop when everyone uses Lightning Networks" is the new "Fees will drop when SegWit is activated"
  30. Adam Back let it slip he hires full-time teams of social media shills/trolls
  31. The bitcoin civil war is not about block size; it's about freedom vs. authoritarianism
  32. Why BCH is the real Bitcoin
  33. We don't need larger blocks, since lightning will come someday™, the same way we don't need cars or planes since teleporters will come someday™
  34. We don't need larger blocks, since lightning will come someday™, the same way we don't need cars or planes since teleporters will come someday™
  35. Facts about Adam Back (Bitcoin/Blockstream CEO) you heard it right, he himself thinks he is in charge of Bitcoin.
  36. A explaination why Core's vision is different from the real Bitcoin vision
  37. The dangerously shifted incentives of SegWit
  38. Lighting Network was supposed to be released in 2016
submitted by thepaip to btc [link] [comments]

[ANN] Bitcoin blockchain data torrent

[ANN] Bitcoin blockchain data torrent submitted by jgarzik to Bitcoin [link] [comments]

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B

Intro

This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
 
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
 
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
 
The updates
 
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
     

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

https://www.youtube.com/watch?v=Snr5e8bzftI
This video shows how long it takes to start Reddcoin Core.   TL;DR:
     

Extra

Backup
Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
 
 
   
Boot with only 1 USB drive plugged in:
Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly.   If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
   
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
   
Start Reddcoin Core easier
Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
   
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
   
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
 
   
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
   
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  
     

Credits:

   
Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

Bitcoin-QT issue on Mac [Failed to Write Block]

I have been syncing my Bitcoin-QT for countless hours for the last couple of days. As of lately it appears to get stuck on around 91% with a message saying "Failed to Write Block" I have updated Bitcoin-QT to the newest version and also imported a bootstrap.dat file to help speed things up since I was syncing 1% every 2-3 hours.
submitted by smirkypigeon to Bitcoin [link] [comments]

A collection of evidence regarding Bitcoin's problem and takeover (January 2018)

REPOSTED FOR MORE VISIBILITY, EDITED A FEW MISTAKES AND INCLUDED NO.1-39 also.*
On November 22th I posted this
On December 27th I posted [this](https://np.reddit.com/btc/comments/7mg4tm/updated_dec_2017_a_collection_of_evidence/
I have added a lot more links now, please give feedback on what else I could add for next time I will add (few weeks/month).
1 The history between btc and bitcoin
Archive link
yours.org link
2 A brief and incomplete history of censorship in /Bitcoin
Archive link
3 User posts on bitcoin about 6900 BTC that theymos stole, post gets removed.
Archive link
4 Go to /noncensored_bitcoin to see posts that have been censored in /bitcoin
5 Theymos caught red-handed - why he censors all the forums he controls, including /bitcoin
Archive link
6 User gets banned from /bitcoin for saying "A $5 fee to send $100 is absolutely ridiculous"
Archive link
7 Greg Maxwell caught using sockpuppets
Archive link
8 Wikipedia Admins: "[Gregory Maxwell of Blockstream Core] is a very dangerous individual" "has for some time been behaving very oddly and aggressively"
Archive link
9 Remember how lightening network was promised to be ready by summer 2016? https://coinjournal.net/lightning-network-should-be-ready-this-summe
Archive link
10 rBitcoin moderator confesses and comes clean that Blockstream is only trying to make a profit by exploiting Bitcoin and pushing users off chain onto sidechains
Archive link
11 "Blockstream plans to sell side chains to enterprises, charging a fixed monthly fee, taking transaction fees and even selling hardware" source- Adam Back Blockstream CEO
Archive link
Twitter proof
Twitter Archive link
12 September 2017 stats post of bitcoin censorship
Archive link
13 Evidence that the mods of /Bitcoin may have been involved with the hacking and vote manipulation "attack" on /Bitcoin.
Archive link
14 bitcoin mods removed top post: "The rich don't need Bitcoin. The poor do"
Archive link
15 In January 2017, someone paid 0.23 cents for 1 transaction. As of December 2017, fees have peaked $40.
16 Told to kill yourself by Bitcoin for cashing out
17 Bitcoin is a captured system
18 Bot attack against bitcoin was allegedly perpetrated by its own moderator and Blockstream’s Greg Maxwell
19 Remember: Bitcoin Cash is solving a problem Core has failed to solve for 6 years. It is urgently needed as a technical solution, and has nothing to do with "Roger" or "Jihan".
20 Bitcoin Cash has got nothing new.
21 How the Bilderberg Group, the Federal Reserve central bank, and MasterCard took over Bitcoin BTC
More evidence
22 Even Core developers used to support 8-100MB blocks before they work for the Bankers
Proof
23 /Bitcoin loves to call Bitcoin Cash "ChinaCoin", but do they realize that over 70% of BTC hashrate comes from China?
24 /bitcoin for years: No altcoin discussion, have a ban! /bitcoin now: use Litecoin if you actually need to transact!
25 First, they said they want BCH on coinbase so they could dump it. Now they are crying about it because it's pumping.
26 Luke-Jr thinks reducing the blocksize will reduce the fees..
27 Core: Bitcoin isn't for the poor. Bitcoin Cash: we'll take them. Our fees are less than a cent. Core: BCash must die!
28 How The Banks Bought Bitcoin. The Lightning Network
29 Big Blocks Can Scale, But Will It Centralize Bitcoin?
30 "Fees will drop when everyone uses Lightning Networks" is the new "Fees will drop when SegWit is activated"
31 Adam Back let it slip he hires full-time teams of social media shills/trolls
32 The bitcoin civil war is not about block size; it's about freedom vs. authoritarianism
33 Why BCH is the real Bitcoin
34 We don't need larger blocks, since lightning will come someday™, the same way we don't need cars or planes since teleporters will come someday™
35 We don't need larger blocks, since lightning will come someday™, the same way we don't need cars or planes since teleporters will come someday™
36 Facts about Adam Back (Bitcoin/Blockstream CEO) you heard it right, he himself thinks he is in charge of Bitcoin.
37 A explaination why Core's vision is different from the real Bitcoin vision
38 The dangerously shifted incentives of SegWit
39 Lighting Network was supposed to be released in 2016
40 You can now store a year's worth of continuously full 8MB blocks for the cost of a single BTC transaction
41 They say we are trying to Kill Bitcoin. No, we are not. We are trying to save it, and make it usable for everyone, and everything. Not tomorrow. Not 6 months from now, Not 18 Months from now. NOW. That's what's going on Here.
42 Miners that want to pull out daily have to switch to BCH due to the fees
43 At $25 #BTC tx fees, if miners want to withdraw their revenue daily, they require a minimum of $140,000 worth of mining hardware to reduce the tx fee to less than 1% of their outgoings. At a $100 tx fee it requires min $560,000. Which is the centralising coin again?
44 Core developer : Bitcoin fees too high? You have invested in early tech! Have faith. Give us time.
45 A redditor even predicted the /bitcoin front page
46 Elizabeth Stark of Lightning Labs admits that a hostile actor can steal funds in LN unless you broadcast a transaction on-chain with a cryptographic proof that recovers the funds. This means LN won't work without a block size limit increase. @8min17s
47 /bitcoin is in uproar about Coinbase not implementing Segwit -> mempool mooning is single handedly Coinbase' fault. So all it takes to bring bitcoin to its knees is a single corporate entity not implementing segwit? Me thinks its not Coinbase there's something wrong with.
48 /bitcoin for years: No altcoin discussion, have a ban! /bitcoin now: use Litecoin if you actually need to transact!
49 $BCH has been attacked in every way possible since it's creation. Exchanges listing it with deceiving names and abbreviations; being dumped by bitcoin holders for over 6 months; and it still managed to close every month positively, while adding numerous new wallet/exchange pairs
50 theymos claims that the whitepaper is a historical artifact not worthy of being on the sidebar of bitcoin
51 Even a Bitcoin conference can't use Bitcoin because of it's high fees
52 185% Growth in Active Addresses for BCH in 1 month, 125% for ETH, -5% for BTC
53 Shapeshift: "Sub-$100 fees unadvisable on BTC." Core supporters: "Implement Segwit already!" Shapeshift: "We did. We're the biggest user of Segwit."
54 How btc and Bitcoin see each other
55 Man who vandalized Bitmain's office hired by Blockstream
56 Bitcoin Cash vs Bitcoin Core compared. Just the facts
57 It was obvious from the very beginning that #Bitcoin transactions were meant to be as cheap as possible. Bitcoin Core has destroyed Bitcoin's usefulness as money by creating a system where $30 fees are celebrated. - @Bitcoin
58 User explains why Core's vision is not the real Bitcoin vision
59 Fake Tweet from the president bashes BCH on /bitcoin front page. Calling it exactly what it is will get you banned.
60 A public appeal to Michael Marquardt the original Theymos.
61 Now they are angry at the CEO of Coinbase for supporting BCH. It's like you are not allowed to have your own opinion without getting attacked.
62 bitcoin user says Bitcoin should not be used as a cryptocurrency
63 The five stages of grief, transaction fees
64 A brief history of the attempted takeover of Bitcoin by BlockstreamCore/The legacy banking systems/The Powers That Be
65 Warning! Theymos admitted he 'misled millions of people' yet he wanna 'leave the text as it is' to mislead more people!
66 "Wait. What? My private keys need to be on an internet-connected computer in order to use Lightning Network?"
67 a year ago Adam Back accused u/Jacktenz of exaggerated claims about fees. The truth is the claims were understated!
68 Roger Ver was not selling explosives, he was selling firecrackers.
69 Core devs pop champaigne, and openly celebrate high fees. Now core supporters blame coinbase for high fees?
70 Now that we've had a few 8MB blocks, let's dispel this centralisation myth once and for all.
71 Reddit admin sodypop on censorship in /Bitcoin: "We generally allow moderators to run their communities how they like as long as they are within our site-wide rules and moderator guidelines." Blatant censorship, hacking, vote manipulation, and brigading are "within [Reddit's] site-wide rules".
72 Another obvious sockpuppet account being used to push Blockstream's agenda.
73 Totally organic grassroots support for the #NO2X "movement." Definitely not a purchased sockpuppet account, you guys.
74 Charlie Lee [Litecoin creator]: "I have sold and donated all my LTC [...] Litecoin has been very good for me financially, so I am well off enough that I no longer need to tie my financial success to Litecoin’s success"
75 If it’s inaccessible to the poor it’s neither radical nor revolutionary.
76 BSCoretabs shills are vandalizing Wikipedia to smear Roger Ver with false quoting, missparaphrasing and accusations.
77 Introducing dipshit extraordinaire Warren Togami, the link between Theymos and BlockStream
78 Debunking: "Blockstream is 3 or 4 developers out of hundreds of developers at Core" - Tone Vays
79 This blockchain debate is purely political and is not about scaling but about control. X-Post from /bitcoin
80 A profile to look at for more evidence
81 What exactly is Blockstream Core's excuse for causing a year of stagnation in Bitcoin with no end in sight?
82 We have a way to build bank-like services.
83 "There is a reason why things are done in a certain way in the financial system, and Bitcoin will be doing something similar"
84 Some thoughts about the possible Bitcoin Segwit, Bilderberg/AXA/BockStream/Core, In-Q-Tel, CIA connection.
85 Theymos on Bitcoin XT
86 (If this is not allowed mods, please remove this text) I cannot verify this yet, but a source has given me information about theymos. theymos is known as Michael Marquardt, from Wisconsin and is a graduate from the University of Wisconsin as a computer-science student.
submitted by thepaip to btc [link] [comments]

Help appreciated: bitcoin-qt runs fine on mac, copy dir to linux, bitcoind doesn't like it.

TL;DR: It's ok to ignore this post, you're not my personal tech support. :)
I've been running a full bitcoin-qt core node on and off on my mac without issues for years (well, until I hosed my blockchain, had to reindex and came here to vent about how slow it was - fixed thanks to yogibreakdance).
I'm trying to move it to a Raspberry Pi so I can have it running full time inside a closet and have the blockchain always up to date, available to sync back to the mac to move my BTC when I need to.
After copying the whole bitcoin dir to the RPI, bitcoind immediately throws "Error initializing block database", removes most of the chainstate contents and stops.
I tried changing file permissions, deleting everything except the blocks and chainstate dirs, using a config file appropriate for the RPI... No change.
If I run bitcoind -reindex-chainstate, it seems to work. At least it starts reindexing, but I don't have the patience to wait till it finishes, it might take months.
Some possibly relevant info: On the mac side the blockchain is stored on a 4 TB Mac OS Extended external disk, on the RPI side it's stored on a 1TB Ext4 external disk, published through samba and mounted on the mac. I use "rsync -rt --size-only" to move the files. Both bitcoin clients are v0.17.0.1. Empty wallet on both sides. On the RPI side, dirs are 777 and files 600 (I tried 777 too).
A couple of weeks ago I had it running, the only difference was that the RPI drive was formatted as NTFS. I switched to Ext4 because NTFS was slow and didn't play nice with the mac.
My google-fu got me nowhere. Hoping someone here might point me in the right direction.
submitted by jungle to Bitcoin [link] [comments]

[BITCOIN REAL GUIDE FOR NEWBIES!] Everything you have to know about BITCOIN REAL in 3 minutes.

Introduction:
When the great revolution that is bitcoin began, the anonymous desired to test two parameters - a trustless, decentralized database (a distributed ledger or blockchain) protected by the everlasting security of cryptography and robust transaction systems capable of sending value across the world without intermediaries. Yet, the past 9 years have excruciatingly shown the lack of a third missing feature, which the brought the community to take action upon vacancy, ending up with the creation of endless Bitcoin Forks "real" Bitcoins", such as BitcoinCash, BitcoinGreen, BitcoinPrivate, BitcoinDiamond. All of these coins have been created because of this third and fundamental feature is missing. Bitcoin lacks innovation. Or rather it has innovation, it simply is extremely slow and cautious., and in the cryptocurrency, innovation is moving fast, the fastest possible. And this is the need that we seek to satisfy.

What is Bitcoin Real?
Bitcoin Real is a Bitcoin Fork which will happen on the TBD block. It will have all the features of the most popular Bitcoin Forks such as master nodes and staking, segregated witness, bigger blocks, proof of work + proof of stake, ASIC resistance) and it will be airdropped with following value across the world without intermediaries. Yet, the past 9 years excruciatingly shown ratios to each coin holder of each forked chain.
A secure blockchain network providing instant payment solutions across the globe with the revolution in block-chain technology-dilemma to choose any two from a trio of trust/security, mass adoption and decentralization has become real for projects. Bitcoin Real (BR) is one of the very few projects that will tap into all three parameters of blockchain together with providing robust transaction system.
In terms of verification of transactions, BR is using 8 MB block size in which several transactions can be verified instantly. The total size of Blockchain will be 140 GB through which BR will be able to cover many of the users’ transaction simultaneously. From the facts, it takes 60 seconds to break a block time in BR. So, around 400000 transactions per second can be done in BR.


Where can I buy Bitcoin Real?

You can purchase BitcoinReal from the exchanges listed below.

Where can I store my coins?

You can store your coins in the desktop wallet provided by the Community.

Contact Information?

Telegram: https://t.me/BitCoinRealPublic
Website: https://www.bitcoinreal.org/
Github: https://github.com/bitcoinreal
submitted by LiteSpeedDev to bitcoinrealcoin [link] [comments]

Summary of Feb 6 Engineering Call #18

Fork Phase Fork 2: *please check out the Medium Article written on this fork -new repository on GitHub for new changes: ElectraCore.git -fork block #: 182,750 (est. 19th February) -Atomic Swaps are fully integrated and working now. Testing is complete. -our blockchain will be upgraded to PoS 3.0(e) upon fork - customized, (more secure) -block time: 64 secs in anticipation for ElectraPay -block size is now variable, can handle up to 10MB -up to 50,000 tx’s per block -Segwit integrated in the fork to prepare for future scaling - will roughly double the # of transactions per block -30 day max on staking rewards is being changed to 60 -QT wallet is to be released on the 15th
Wallet Testing: (Jenova) -testing done for wallet v2.0 -code is being cleaned up atm -wallet releases on the 15th, fork should be on the 19th *all info can be found in the new wallet setup guide - DO NOT use the wallet in between the 15th-19th - after downloading, wait till the fork to make tx’s - if downloading wallet AFTER the 19th, this is fine, just don’t make any tx’s before upgrading -v2.1, once released, will eliminate orphan blocks completely, allowing ECA to be received safely with 0 confirmations.
ElectraPay: -still in development -with the new debit cards (once implemented), we can achieve instant tx’s and confirmations Marketing/Partnerships: -partnership with a hardware wallet company is in the works coming soon (post-fork) -other partnership integrations waiting to be released post-fork
Exchanges: -shortly after fork, we will see a few new exchange listings - team is still working on landing a big exchange -legal partner (Agile) established us as non-security token
Foundation: -can now accept donations in BTC/LTC/ETH and of course ECA Bitcoin: 33AJAGjPDfm6zoXFBjfemxHdqHoAAovCdt Litecoin: 38nfGmEZWQ7HENz9rDjW9QQJ23mwSbYwFv Ethereum: 0x9233d4f5629e75cef5403e5c97319bf94e1cbf33 Electra: EYPFYiy3gkS7ENJ8zFfctMXrFdiBggh2Fc
-EO1 is back from the military, 200mln deposit has been received. (Full 300mln is secure now.) -on the foundation website page, there is now a record of tx’s in and out of the wallet. With labels to make it easy to identify what the tx/s are for.
Misc: -new block explorer is up and running -Robert gave a call for business-minded community members to join the team and help push the Business Development of Electra! Message him privately for more info
submitted by Benjigumba to Electra_Currency [link] [comments]

What is up with all these Bitcoin devs who think that their job includes HARD-CODING CERTAIN VALUES THAT ARE SUPPOSED TO BE USER-CONFIGURABLE (eg: "seed servers")?

Recently, the developer of SegWit2x / BTC1, Jeff Garzik, caused some controversy by hard-coding the "seed servers" which Bitcoin uses to first start hunting for "peers".
Worse than that: apparently one of the "seeds" is a company he started, variously named Chainalysis / Skry / Bloq - which apparently specializes in de-anonymizing Bitcoin transactions and performing KYC/AML - and which also has apparently entered into agreements with Interpol.
Seriously, WTF???
This is what "Bitcoin devs" still consider to be part of their "job" - hard-coding parameters like this, which affect everyone else on the network - and which could easily be "exposed" to be made user-configurable - instead of being baked into the source code and requiring a friggin' recompile to change???
This recent event has refocused attention on the fact all these past years, most of these seed servers in "the" existing (legacy) client running on most of the network have _also been hard-coded - to domains under the control of "devs associated with Blockstream".
I don't like the list of seed servers in Bitcoin Core
Pieter Wuille - does not support BIP148 - works for Blockstream
Matt Corallo - does not support BIP148 - works for Blockstream
Luke Dashjr - supports BIP148 - works for Blockstream
Christian Decker - supports BIP148 - works for Blockstream
Jonas Schnelli - supports BIP148
Peter Todd - supports BIP148 - worked for Samson Mow who works for Blockstream
https://np.reddit.com/btc/comments/6nd50h/i_dont_like_the_list_of_seed_servers_in_bitcoin/
The corporate takeover of bitcoin illustrated in 1 commit
In The corporate takeover of bitcoin illustrated in 1 commit a user complains that btc1 changing the seed servers to servers run by some companies (see commit) equals a "corporate takeover of bitcoin". I never really took much care who runs these seed server, although they do posses a certain power over the network as correctly pointed out by P. Todd in the same thread:
...and the key thing with that is being able to control what nodes a node connects to can be a very powerful tool to attack new nodes, as it lets you prevent a node from learning about the valid chain with the most work.
[...]
4 out of 5 people running the bitcoin networks seed servers are directly associated with Blockstream!
I don't even believe that Blockstream is actually plotting an evil, forceful takeover of bitcoin using the seed servers. However it beautifully counteracts Adam's "decentralization is everything" arguments. What is most troublesome to me, is that this simple information is not allowed to appear on r\bitcoin at all.
https://np.reddit.com/btc/comments/6n8vqc/the_corporate_takeover_of_bitcoin_illustrated_in/
Seriously?
Bitcoin is almost 9 years old - and most people are still running clients which use hard-coded values (which require an inconvenient recompile to reconfigure) for the "seed servers"??
Maybe this is, in some sense, part of the reason why people like BlueMatt and Luke-Jr and Pieter Wiulle think they can lord it over us and tell everyone else what to do? ...because they have quietly (and unfairly / incompetently) hard-coded their own friggin' server domain names directly into everyone else's client code, as our "seed servers"?
Is the low level of "quality" we - as a community - have become accustomed to from our devs?
Do other clients (Bitcoin Classic, Bitcoin Unlimited and Bitcoin ABC) also gratuitously hard-code their "seed servers" like this?
Here's a post from a year ago regarding "seed servers" in Classic:
How come "classic" uses the same alert keys/DNS seeds as Core?
https://np.reddit.com/btc/comments/44atsp/how_come_classic_uses_the_same_alert_keysdns/
Meanwhile, here's the main question:
Why are any "serious" Bitcoin clients still "gratuitously" hard-coding any values like this?
Why has our "ecosystem" / "community" not naturally evolved to the point where we have some public "wiki" pages listing all the "good" (community-recognized, popular) seed servers - and every user configures their own client software by choosing who they want from this list?
(Maybe because we've been distracted by bullshit for these past few years, fighting with these very same devs because they've refused provide any support for users who want bigger blocks?)
What would users have to do if (God forbid) something were to happen to the servers of those 4-5 seed servers which are currently hard-coded into nearly everyone's clients?
In that situation (assuming some "new" seed servers quickly appeared) people would be have two options:
  • Edit their C++ source code and download/install a (trusted, verified) C++ compiler (if they don't already have one), and recompile the friggin' code; or
  • Wait until new binaries got posted online - and download them (and verify them).
Seriously?
This unnecessary "centralization point" (or major inconvenience / bottleneck) has been sitting in our code this entire time - while these supposedly knowledgeable devs keep beating us over their head with their mantra of "decentralization" - which they have actually been doing so little to maximize?
Psycho-Socio-Economic Side Bar
Serious (but delicate/senstive) question: How many of these "devs" have developed (possibly unconscious?) behaviors in life where they try to make users dependent on them?
"Vendor lock-in" is a thing - a very bad thing, which certain Bitcoin devs have exhibited a tendency to inflict on users - in many cases due to rather obvious (psychological, social, and/or economic) reasons.
We should gently (but firmly) reject these tendencies whenever any dev exhibits them.
Our community should expect and demand an accessible, user-friendly interface for all user-configurable parameters - to maximize decentralization and autonomy
  • In "command-line" versions of the client program, these kind of parameters should be:
    • in a separate config file - using some ultra-simple, standard format such as YAML or JSON
    • also configurable via options (eg, --seed-server) upon invocation on the command-line
  • In GUI versions version of the client program (using some popular cross-platform standard such as Qt, HTML, etc.) these kind of parameters should be exposed as user-configurable options.
Yes, these user-configurable values for things like "seed servers" (or "max blocksize") could come pre-configured to "sensible defaults - so that the software will work "out of the box" (immediately upon downloading and installing) - with no initial configuration required by the user.
Yes: Even the blocksize has always been user-configurable - but most users don't know this, because most devs have been hiding this fact from us.
Three recent posts by u/ForkiusMaximus explained how Adjustable-Blocksize-Cap (ABC) Bitcoin clients shatter this illusion:
Adjustable-blocksize-cap (ABC) clients give miners exactly zero additional power. BU, Classic, and other ABC clients are really just an argument in code form, shattering the illusion that devs are part of the governance structure.
https://np.reddit.com/btc/comments/614su9/adjustableblocksizecap_abc_clients_give_miners/
Adjustable blocksize cap (ABC) is dangerous? The blocksize cap has always been user-adjustable. Core just has a really shitty inferface for it.
https://np.reddit.com/btc/comments/617gf9/adjustable_blocksize_cap_abc_is_dangerous_the/
Clearing up Some Widespread Confusions about BU
https://np.reddit.com/btc/comments/602vsy/clearing_up_some_widespread_confusions_about_bu/
Note about Bitcoin ABC vs Bitcoin Unlimited:
There is a specific new Bitcoin client called Bitcoin ABC, which functions similar to Bitcoin Unlimited - with the important difference that Bitcoin ABC is _guaranteed to hard-fork to bigger blocks on August 1_.
(Please correct me if I'm wrong about this. Documentation for the behavior of these various hard-forks is currently still rather disorganized :-)
All serious devs should be expected to provide code which does not require a "recompile" to change these "initial, sensible" default parameters.
I mean - come on. Even back in the 80s people had "*.INI" files on DOS and Windows.
Nearly all users understand and know how to set user-configurable values - for decades.
How many people are familiar with using a program which has a "Preferences" screen? (Sometimes you may have to close and re-open the program in order for your new preferences to take effect.) This is really basic, basic functionality which nearly all software provides via a GUI (and or config file and/or command-line options).
And nearly all devs have been offering this kind of functionality - in either command-line parameters, config files, and/or graphic user interfaces (GUIs).
Except most Bitcoin devs.
The state of "software development" for Bitcoin clients seems really messed up in certain ways like this.
As users, we need to start demanding simple, standard features in our client software - such as accessible, user-friendly configurability of parameter values - without the massive inconvenience of a recompile.
What is a "Bitcoin client"?
After nearly 9 years in operation, our community should by now have a basic concept or definition of what a "Bitcoin client" is / does - probably something along the lines of:

A Bitcoin client is a device for reading (and optionally appending to) the immutable Bitcoin Blockchain.

Based on that general concept / definition, a program which does all of the above and also gratuitously "hard-codes" a bunch of domain names for "seed servers" is not quite the same thing as a "a Bitcoin client".
Such an "overspecialized" client actually provides merely a subset of the full functionality of a true "Bitcoin client", eg:
  • An "overspecialized" client only enables connecting to certain "seed servers" upon startup (in accordance with the "gratuitous opinion" of the dev who (mis)translated the community's conceptual specifications to C++ code)
  • An "overspecialized" client only enables mining blocks less that a certain size (in accordance with the "gratuitous opinion" of the dev who (mis)translated the community's conceptual specifications to C++ code)
One of the main problems with nearly all Bitcoin clients developed so far is that they are gratuitously opinionated: they "gratuitously" hard-code particular values (eg, "max blocksize", "seed servers") which are not part of the whitepaper, and not part of the generally accepted definition of a "Bitcoin client".
This failure on the part of devs to provide Bitcoin clients which behave in accordance with the community's specification of "Bitcoin clients" is seriously damaging Bitcoin - and needs to be fixed as soon as possible.
Right now is a good opportunity - with so many new Bitcoin clients popping up, as the community prepares to fork.
All devs working on various Bitcoin client software offerings need to wake up and realize that there is about to be a major battle to find out which Bitcoin client software offering performs "best" (in the user-interface sense - and ultimately in the economic sense) at:

reading (and optionally appending to) the immutable Bitcoin Blockchain

The Bitcoin client software offerings which can optimally (and most simply and securely :-) "satisfy" the above specification (and not merely some gratuitously overspecialized "subset" of it) will have the most success.
submitted by ydtm to btc [link] [comments]

What do you like the most about Bitcore?

Hello guys, I would like to know what you like the most about Bitcore and how you found out about its existence.
As for me, I love most of all the potential that a 10MB block with Segwit has when it comes to the number of transactions it can handle... it is amazing! Also, I love that the blockchain is very small in size: using the original qt wallet the entire blockchain at the moment is under 1Gb in size!
I found out about Bitcore last July, reading some news about Bitcoin forks, and I am in love with it ever since! <3 What about you? What do you like the most about Bitcore and how did you find out about it?
submitted by fabioganga to bitcore_btx [link] [comments]

EOT - Encryption of things

 **EOT - Encryption of things** 
There is a huge surge in devices attached to the internet, known as the Internet of Things, and it is estimated that over 80 Billion devices will be connected to the internet by 2025, from industrial machines to devices in our home. The constant hacking and cyber attacks have increased not only the demand but the necessity of secure solutions. Our privacy and digital footprint are at risk.
[b]Some examples where encryption plays a role:
[b]Secure messaging - To make messages truly secure we need a process whereby a cryptography can be applied to encrypt transaction.
[b]Secure calling - Secure calling is a process whereby the caller and the recipient of the call are identified and linked via a blockchain enabled cryptocurrency transfer, again creating public and private encryption keys making the call truly private.
[b]Secure media storage - To safely and securely store media a process is required where 1.) Access to the media is encrypted via public and private keys of the person wanting to store the media. 2.) The media itself needs to be encrypted with a set of encryption keys and 3.) Media storage costs need to be paid via cryptocurrency
[b]Secure browsing - To browse the internet securely we need to create a process of verification whereby nodes on the blockchain can verify websites as “safe”. Furthermore, the entire process needs to be encrypted as well.
[b]Verification - This is one of the most important uses of a blockchain, we can verify websites as in the example above but also various other things such as identity, title and ownership, date stamps and source of products as with the verification of the source of agricultural or other products. These are just a few examples. All of this data needs to be encrypted as well.
[b]“Smart home” security - Wi-Fi is often used for remote monitoring and control. Home devices, when remotely monitored and controlled via the Internet, are an important constituent of the Internet of Things - all needing encryption, otherwise, hackers paradise.
[b]EOT in the future - The examples we mentioned above are only “scratching the surface” of where these technologies are applicable and who knows what will be invented in future. Google, Apple and Uber are all testing cars that drive themselves. A major issue with this technology is again the security aspect and the need to protect against hacking and who want’s to get into a spaceship to Mars that might be hacked or hijacked by ransomware?
So the future for the [b]“Encryption of Things” – EOT, looks very interesting indeed and the role of crypto currencies in this will be major.
Read the full white paper here - http://eottoken.com/index.php/whitepape
The first device using EOT Coin is the BitVault®[/b] - the World's first crypto communicator and blockchain phone. The BitVault is a revolutionary new product that is built around security and privacy enabled through Blockchain technology. Biometric Security enabled through fingerprint and iris scan. Iris patterns are unique to you and are virtually impossible to replicate. This means that iris authentication is one of the safest ways to keep your BitVault locked and the contents private. Proven Biometric technology brings a whole new level of security to your crypto currency and blockchain transactions. Creating Military grade security for your device through third party independent Multilayer security.
September 2017 – Swiss Bank in Your Pocket integrates EOT Wallet(Achived)
October 2017 – BitVault®, the world’s first blockchain phone launches in London with integration of EOT for secure calling, secure messaging and secure browsing (First batch shipped)
November 2017 – BitVault® Global App Store launches for developers to develop their own applications (Achived)
November 2017 – Website EOT Payment Gateway for WordPress and WooCommerce (ACHIVED)
December 2017 – Cryptodoc stores all your documents securely and encrypted on your PC
December 2017 – Password Wallet stores all your passwords for applications and websites encrypted on your PC January 2018 – Smart Router for secure, encrypted internet which is direct, safe and easy
January 2018 – EOT Camera, an Encryption of Things connected camera
February 2018 – EOT Development Kit for hardware devices
EOT payment gateway live on swissbankinyourpocket.com, Now you can buy SBIYP and BitVault using EOT coins
More on the BitVault here:- https://swissbankinyourpocket.com/bitvault/]https://swissbankinyourpocket.com/bitvault/ https://swissbankinyourpocket.com/bitvault-apps/]https://swissbankinyourpocket.com/bitvault-apps/ https://bitcointalk.org/index.php?topic=2152534.0]https://bitcointalk.org/index.php?topic=2152534.0
JOIN US ON REDDIT : http://www.reddit.com/EncryptionOfThings]www.reddit.com/EncryptionOfThings JOIN US ON SLACK : [url=https://join.slack.com/t/eot-coin/shared_invite/enQtMjc3NzkxNzY5NzQ0LTFjMWI5NTJjOGEzYjU5ZDk0ZjRjZWE3MzBkNmI0MmQ2NTUzMTBkOGQ1YmEyNTllMmNiYzA3MGZjOGVmY2IyZGU
The EOT Token is trading on the Waves Platform, TOKENS are 1:1 image of EOT coins, EOT coins can be converted to tokens and vice versa using gateway service in SBIYP hardware wallet. if you do not have that hardware wallet, you can contact members on slack who have purchased SBIYP to do that swap for you.
TOKEN DETAILS
Name : EOT Token (Verified)
Identifier : GdnNbe6E3txF63gv3rxhpfxytTJtG7ZYyHAvWWrrEbK5
Total supply : 100,000,000
EOT token (EOT) markets added on the Tidex Exchange https://tidex.com/exchange/eot/btc https://tidex.com/exchange/eot/waves
EOT Coin details (currently minable)
https://github.com/EmbeddedDownloads/EOTCoin
windows wallet[/b] https://github.com/EmbeddedDownloads/EOTCoin/releases/download/v1.0.0.1/EOTCoin-win.exe
windows Desktop wallet[/b] https://github.com/EmbeddedDownloads/EOT-Coin-Windows-Desktop-Wallet/releases/download/1.0/EOTCoinDesktopWallet1-0.zip
MAC Wallet [/b] https://github.com/EmbeddedDownloads/EOTCoin/releases/download/v1.0.0.1/EOTCOIN-Qt-OSX-v1001.dmg
WEB wallet [/b] http://eot.digital (Closing, please withdraw your coins)
ANDROID wallet [/b] https://github.com/EmbeddedDownloads/EOTAndroidWallet/releases
Block Explorer [/b] http://www.eot.digital:3622/
Block Explorer 2 [/b] http://www.eotcoin.info (created by [b]@Luanptit[/b])
[Block reward [/b] 100 Coins, [b] ALGORITHM [/b] SCRYPT, [b] BLOCK TIME [/b] 90 seconds
MINING POOLS
Official mining pool [/b] http://www.eot.digital:3001/ Getting Started [/b] minerd -a scrypt -o stratum+tcp://www.eot.digital:3256 -u WalletAddressWhereYouWantYourMiningCoins -p 1
unofficial Mining pools http://www.altminer.net
http://antminepool.com
http://coinminers.net/
http://www.vivocryptopool.com
[red]Currently EOT is traded on WAVES DEX, Crypto-Bridge DEX and TIDEX. Big exchanges will be available soon, exchanges are in comkmunication.
Opportunities are available with EOT - from Development, Mining, Trading as well as other business opportunities built around the EOT currency and the "Encryption of Things"
[size=34px]Bitvault on Yahoo Finance https://finance.yahoo.com/news/bitvault-worlds-first-blockchain-phone-201600279.html [/size] [center][img width=770]https://i.imgur.com/UMIlRoC.png[/img][/center]
[center][size=30px]Press release 4th October 2017 [/size] [size=30px]yahoo Finance https://finance.yahoo.com/news/bitvault-announces-london-launch-161000826.html?soc_src=community&soc_trk=tw [img]https://i.imgur.com/mBDZnN7.png[/img]
Some Helpful Information
[quote author=Story777 link=topic=2091616.msg21890405#msg21890405 date=1505551168]
You have been keeping a great secret.
I've been doing a bit of research with the technology behind this coin. It looks like ALOT of research has gone into this tech, since about 2004 and shortly after a patent for this P2P system was quickly issued.
Bitvault (https://swissbankinyourpocket.com/product/bitvault/) who are using the worlds first blockchain phone as a secure communication device and ultimately taking [font=Verdana][b]encryption[/b][/font] to the Internet Of Things (IoT) keeping our personal and business data secure. All this is done using [b]EOT coin [/b](Encryption of Things).
In todays world insecure devices are rampant. Here are a couple of links about the CIA being able to use insecure devices to 'cause accidents' http://www.sandiegouniontribune.com/news/cyber-life/sd-me-wikileaks-cia-20170307-story.html and https://www.washingtonpost.com/news/innovations/wp/2017/03/08/what-we-know-about-car-hacking-the-cia-and-those-wikileaks-claims/
It's scary to think a legal entity could posses such power over life. Just the mere fact alone the governing authority can request phone records (e.g. txt msgs, voice msgs or eavesdropping) proves most if not all telecommunication companies do not encrypt, otherwise whats the point on requesting the information!? (legal or not).
Commercially sensitive information needs to be protected and most importantly in my opinion our [font=Verdana][b]rights[/b][/font] and the privacy of all citizens of the human race need to be protected.
From my understanding BitVault is a platform for reference data. This would be data that is stored for compliance reasons such as e-mails, invoicing systems and check imaging (e.g. high quality imaging for x-rays, MRI scans etc) and a prototype was developed in 2004. This would means massive amount of data storage is required with fail-safe systems so a authorised user could access this information very very quickly.
Three goals were needed to be achieved: Low cost, high reliability/availability and simplicity. This is the birth of Bitvault via EOT.
Bitvault ultimately stores immutable objects with each new version being updated and identified with a 160-bit key.
System stability is very important and must be immune to failure sequences. Parallel repair via indexing is one of the many strengths Bitvault has been able to demonstrate.
BitVault is a back-end system that uses [u][b]Applications[/b][/u] to catalog object ID's. Using a catalog utility and indexing within an application prevented scalability bottlenecking under heavy loads.
Fast forward 3 years to 2007 a very important decision was to [u][b]decentralise[/b][/u] BitVaults system. This in my opinion is one of the fundamental principles of cryptocurrency - [u][b]No one entity or person has any control of the data stored and only the authorised user can access this info[/b][/u]. Ultimate Security and thus personal safety (see above articles CIA hacks). BitVault using applications have been able to use provable communication and data storage with ease of retrieval with vital security measures.
BitVault is not alone in researching solutions for security for the IoT, such as Venti and the like are making progress, however, BitVault is 'head and shoulders' above the few competitors and are already offering practical working solutions on the market with huge scalability that is cost effective.
Well Done BitVault, well done EOT your secret is out and let the world embrace.
author=Story777 link=topic=2091616.msg21462424#msg21462424 date=1504428317]
I have had a response in Slack and it has satisfied my questions. Thank-you.
For everyone information here it is:
The currency was created with 200 Million EOT total supply on 7 July 2017 [ we showed it to the community a London Fintech week with the demonstration of the BitVault - fintechweek.com ]
100 Million was pre-mined and another 100 Million are currently being mined, 1 block every 90 seconds @ 100 coins per block.
So the pre-mined coins were listed on waves as a token so that it can create a market for the coins while we are working to get listed on other exchanges.
The 100 Million coins listed were distributed in several ways. Firstly, this was not an ICO because our business is already funded via private capital. We wanted to get the currency distributed a widely as possible. So most of the initial coins were given away to a number of interested parties. We distributed this to our whole development team, business partners, employees as well as to the waves and other communities. So we did not sell all these coins for the current price, most of it was given away for free to people that have an interest in our products and business. The price now is formed by whoever owns these coins.
The tokens on the exchange is really a representation of the currency and as such has value because it can be interchanged, just like Bitcoin and Ethereum are on the waves exchange. This whole process is explained on page 4 of the waves whitepaper, I think they call it an asset-to-asset exchange which makes it possible to list any asset that exist on waves. Unfortunately waves only has gateways currently for Bitcoin, Ethereum, Waves, Euro and USD, so we have to develop our own gateway, which will be available on Nov 1.
So to clarify 100,000,000 tokens costing $190M were not sold. It is a combination of airdrops, private sales and sales on the exchange.
Some EOT coins are needed because: "A lot of EOT will be distributed through our devices. For example our encrypted routers are pre-loaded with EOT, so we need that stock and it will be distributed that way".
And with the response to tokens on the Waves Exchange "This is how Bitcoin works on waves: - They created 21 Million BTC Tokens.. When you deposit Bitcoin into waves account, you receive an equal amount of tokens which you can either trade or even sent via the waves blockchain to another user.. Once you withdraw your tokens are exchanged for BTC and you receive it back into your BTC wallet.. Exactly the same for USD or EUR - You don't send Euro's to another client on waves if you transfer - you send a token that represents EUR -- This works exactly the w0083".
These are the answers I was looking for and make a lot of sense now. This is indeed an exciting project. :)
It's time to trade....
Now I have one question left....
Is there anyone using NiceHash to mine this coin?? I keep being disconnected because of the difficulty being too low. Can any one help?
[quote author=Shews link=topic=2091616.msg22876983#msg22876983 date=1507755312] EOT (coin) is now tradable on the CryptoBridge Decentralised Exchange, you can sign up below.
Please note this is for the EOT COIN ONLY, do not send tokens to this dex. This is a secure means to trade with the backend being on a blockchain. It is still in beta stage but has been working flawlessly so far. If you'd like more info I will post their website link is below.
https://wallet.crypto-bridge.org/?r=388691
You can sign up with a local wallet mode, meaning you are the only one with access to your keys, this is most secure. There is also the option to sign up with and account if you require access to you funds on the go.
More info:
https://crypto-bridge.org/
submitted by johningreece to crypto_currency [link] [comments]

Bitcoin block size limit concept: history of its establishment Will Bitcoin Block Size Reduction Argument Cause Another Crypto Conflict Bitcoin Fundamentals: Block Size, Bitcoin Scalability, & SegWit On Bitcoin Reaching Block Size Limits Bitcoin Block Size: Larger or smaller blocks?

Block is a permanently recorded file at Bitcoin containing information on occurred transactions. Block is the record of the every recent transaction or its part that has not been recorded in the previous blocks. Practically in all cases blocks are added to the end of the chain, which contains all transactions and is called blockchain.When a block is added to the end of the chain, it cannot be Set maximum block size in bytes (default: 750000) -blockprioritysize=<n> Set maximum size of high-priority/low-fee transactions in bytes (default: 0) (for controlling a running Bitcoin/bitcoind process) # # server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands #server=0 # Bind to given address to listen for JSON-RPC connections Bitcoin Core initial synchronization will take time and download a lot of data. You should make sure that you have enough bandwidth and storage for the full block chain size (over 200GB). If you have a good Internet connection, you can help strengthen the network by keeping your PC running with Bitcoin Core and port 8333 open. As of Oct 2014, bootstrap.dat file size is 22+GB and this block-size continues to grow making Bitcoin-Qt setup requires days. However, only miners would need the entire blockchain data. Thus, instead of using Bitcoin-Qt as your choice of Bitcoin wallet, consider using other light weight client like Multibit or Electrum. The Bitcoin blockchain data contains all transaction history from the day Bitcoin was created to till date. With 1MB block size and 10 minutes block time the size of the chain grows larger and larger. Hence the storage capacity needed to run a full node will only keeps increasing in the future.

[index] [10619] [11204] [12409] [15497] [8725] [823] [14658] [6640] [5580] [2040]

Bitcoin block size limit concept: history of its establishment

Things have been busy in crypto land this week and the big debate over Bitcoin’s block size has only just been usurped by JP Morgan’s attempt to launch its own completely centralized crypto coin. Top Bitcoin Core Dev Greg Maxwell DevCore: Must watch talk on mining, block size, and more - Duration: 55:04. The Bitcoin Foundation 19,937 views As Bitcoin grows, its blocks are starting to fill up, and thus discussion has been ongoing on how to best handle this. The block size limit is current 1mb per block, 4mb, 8mb and 20mb limits per ... A talk on the Bitcoin block size debate and a discussion of arguments for both larger and smaller block sizes give by Leonhard Weese on 18 November, 2015 at Tuspark's Causeway Bay location in Hong ... The BTC block limit is a parameter in the Bitcoin protocol that limits the size of blocks, and therefore The number of transactions that receive confirmation on the network every 10 minutes. Upon...