There has been a release of many stables coins recently. What are the differences from each? So far I know that Tether (usdt) is based out of the US banking system and everything else is in the US banking system and regulated. Also I read that the USDC and GUSD has a back door system to freeze and hold accounts if they wanted to. I wasn’t sure if PAX had this same thing. What are all the listed pros/cons of each stable coin?
I’m running several bitcoin-seeders. Under Ubuntu 14.04 & 16.04, they run fine and answer queries.
On Ubuntu 18.04, however, dnsseed does not detect the queries sent to it. I know the machine is receiving the query because DNS requests are monitored with dnstop, and every DNS query sent with ‘dig‘ is sensed by dnstop and reported, but dnsseed shows “0 DNS Requests”.
There is no firewall running and apparmor has been disabled. What tests could be run or troubleshooting strategy followed to find the problem ?
Under Ubuntu 16.04:
Loading dnsseed.dat...done Starting 4 DNS threads for ra.zmark.org on 184.108.40.206 (port 5353).......done Starting seeder...done [18-10-24 19:27:41] 274/37963 available (1258 tried in 1000s, 38980 new, 1536 active), 0 banned; 3 DNS requests, 3 db queries
Under Ubuntu 18.04:
Supporting whitelisted filters: 0x1,0x5,0x9,0xd Loading dnsseed.dat...done Starting 4 DNS threads for shido.bitmark.one on 220.127.116.11 (port 5353).......done Starting seeder...done Starting 96 crawler threads...done [18-10-24 19:25:23] 3593/87930 available (64497 tried in 3805s, 21897 new, 1536 active), 1 banned; 0 DNS requests, 0 db queries
Queries: 0 new, 1363 total Wed Oct 24 19:39:03 2018 Replies: 0 new, 191 total Query Name Count % cum% -------------------------- --------- ------ ------ shido.bitmark.one 1169 85.8 85.8 bitseed.xf2.org 117 8.6 94.4 org.members.linode.com 24 1.8 96.1 seed.bitcoin.sipa.be 20 1.5 97.6 dnsseed.bitcoin.dashjr.org 14 1.0 98.6 dnsseed.bluematt.me 12 0.9 99.5 motd.ubuntu.com 5 0.4 99.9 github.com 2 0.1 100.0
I am running a full node using Bitcoin Core GUI on Windows 10. The conf file is in my bitcoin data directory, instead of being in the appdata/roaming folder. But Bitcoin-qt points to it by default and seems to work fine.
But bitcoind and bitcoin-cli are looking for the conf file in the appdata/roaming folder, which I guess is the reason the bitcoind server never appears to start. How do I start bitcoind and check if it is running or not? I need bitcoind to run so that I can use json-rpc commands.
If I run bitcoind on cmd, it appears to start downloading the whole blockchain again, which is unnecessary because I already have all of it.
I am very new to Bitcoin. My friend and I are doing a business that will accept Bitcoin as payment. I would like to know how easy it is to use Copay as a wallet that we can both share, and that will require both our authorizations to distribute Bitcoins into separate Bitcoin wallets for us? If someone could please answer this for me, I would be very appreciative.
I’m trying to build Bitcoin core client on an LinuxMint. I’m having the following error(which have not encountered before, while making it on MSWindows or another Linux machine) in make process, right after
& I can’t figure out why:
wallet/walletutil.cpp: In function ‘std::vector<boost::filesystem::path> ListWalletDir()’: wallet/walletutil.cpp:60:32: error: ‘relative’ is not a member of ‘fs’ paths.emplace_back(fs::relative(it->path(), wallet_dir)); ^ wallet/walletutil.cpp:71:36: error: ‘relative’ is not a member of ‘fs’ paths.emplace_back(fs::relative(it->path(), wallet_dir)); Makefile:6894: recipe for target 'wallet/libbitcoin_wallet_a-walletutil.o' failed make: *** [wallet/libbitcoin_wallet_a-walletutil.o] Error 1 make: Leaving directory '/home/behrad/cprj/bitcoin/src' Makefile:10232: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1 make: Leaving directory '/home/behrad/cprj/bitcoin/src' Makefile:774: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1
My machine version is
uname -a output:
Linux anonymous 4.10.0-38-generic #42~16.04.1-Ubuntu SMP Tue Oct 10 16:32:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
One thing comes to my mind is the initial advice on
build-unix.md doc, which was warning against relative paths:
Always use absolute paths to configure and compile Bitcoin Core and the dependencies, for example, when specifying the path of the dependency: ../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX Here BDB_PREFIX must be an absolute path - it is defined using $(pwd) which ensures the usage of the absolute path.
But as I stated, I’ve passed configuration & this occurred while it was about finishing. I can installing w/o wallet, but I need it in this installation. Thank you for taking time reading so far, Any help appreciated in advance.
This is my configuration file and i followed all of the instructions for the program but it always gives me the error message about something missing. I don’t even know what programming language .conf files are written in. if someone can give me some guidance that would be much appreciated.
The blockchain consensus seems to be very related to the Game Theory, when each participant tries to achieve their “favorites“, where defining “what favorites means” is not very easy, since a participant may ex. intends to gain more coins, while another one tries to destroy the system and decrease its reputation as a “competitor crypto-currency” etc.
- Cooperative / Non-cooperative,
- Symmetric / Asymmetric,
- Zero-sum / Non-zero-sum,
- Simultaneous / Sequential,
- Perfect information and imperfect information,
- Combinatorial games,
- Infinitely long games,
- Discrete and continuous games,
- Differential games,
- Evolutionary game theory,
Metagames, Pooling games,
Mean field game theory …
Regarding to above explanations, what types of these Game Theory are more involved in the blockchain consensus?