|
Maybe they could.
But why would they want to destroy it? If they only regulate it, they can tax it heavily, so they will have a huge income and they don't need to do anything but collecting the taxes.
If they ban it and want to destroy it, they won't be able to do that in the end and also they won't have any tax, any income from bitcoin transactions or profits.
|
|
|
|
...
Thanks for the involvement! my question is not about fees, I trust LN for Micro payments! as well as segwit and additionally Litecoin, but my point is, how is it possible to make receiving addresses look easier for users, think of domain names and ip addresses
would you remember 156.214.235.114 OR someword.com ?
Why not just use an app like the Mycelium mobile wallet or anything else where you can save an address and label it for yourself with anything you like, you won't need to deal with numbers and letters in a row anymore... I think the future will be something like you'll have a new category inside a contact, which will be a crypto address, you'll be able to easily scan someone's QR code to attach it to the person's details. You'll be able to use these stored addresses in every app, so you won't need to remember the addresses itself if they are stored on your phone. |
|
|
|
My problem is that my lnd neutrino node can't find any node to connect to, so I'm still struggling with it, but somehow sometime I'll get it working... Can you upload log file? Is there any error? There's no particular error, it just doesn't find a node to connect to. I have several things that seem suspicious in the log, first one is a DNS problem (or something in connection with DNS (what can be the :53: after the router's IP address...) 2018-04-11 23:59:53.598 [INF] CMGR: DNS discovery failed on seed x49.dnsseed.bluematt.me: lookup x49.dnsseed.bluematt.me on 192.168.1.254:53: no such host
2018-04-11 23:59:54.097 [INF] CMGR: DNS discovery failed on seed x49.seed.bitcoin.sipa.be: lookup x49.seed.bitcoin.sipa.be on 192.168.1.254:53: no such host
2018-04-11 23:59:55.864 [INF] CMGR: DNS discovery failed on seed x49.seed.bitcoin.jonasschnelli.ch: lookup x49.seed.bitcoin.jonasschnelli.ch on 192.168.1.254:53: server misbehaving I've searched the sourced for this :53: but found nothing, so it's interesting, what's that... The log: lnd –bitcoin.active –bitcoin.mainnet –debuglevel=debug –bitcoin.node=neutrino --noencryptwallet
2018-04-11 23:59:52.308 [INF] LTND: Version 0.4.0-beta commit=
2018-04-11 23:59:52.308 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2018-04-11 23:59:52.309 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0
2018-04-11 23:59:52.716 [INF] LTND: Primary chain is set to: bitcoin
2018-04-11 23:59:52.717 [INF] BTCN: Loaded 0 addresses from file '/home/pi/.lnd/data/chain/bitcoin/mainnet/peers.json'
2018-04-11 23:59:53.181 [INF] CMGR: 38 addresses found from DNS seed dnsseed.bitcoin.dashjr.org
2018-04-11 23:59:53.257 [INF] CMGR: 40 addresses found from DNS seed seed.bitnodes.io
2018-04-11 23:59:53.532 [INF] CMGR: 25 addresses found from DNS seed x49.seed.bitcoinstats.com
2018-04-11 23:59:53.598 [INF] CMGR: DNS discovery failed on seed x49.dnsseed.bluematt.me: lookup x49.dnsseed.bluematt.me on 192.168.1.254:53: no such host
2018-04-11 23:59:54.097 [INF] CMGR: DNS discovery failed on seed x49.seed.bitcoin.sipa.be: lookup x49.seed.bitcoin.sipa.be on 192.168.1.254:53: no such host
2018-04-11 23:59:55.864 [INF] CMGR: DNS discovery failed on seed x49.seed.bitcoin.jonasschnelli.ch: lookup x49.seed.bitcoin.jonasschnelli.ch on 192.168.1.254:53: server misbehaving
2018-04-11 23:59:58.231 [INF] BTCN: Disconnecting peer 51.15.139.246:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.232 [INF] BTCN: Lost peer 51.15.139.246:8333 (outbound)
2018-04-11 23:59:58.416 [INF] BTCN: Disconnecting peer 96.43.135.210:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.416 [INF] BTCN: Lost peer 96.43.135.210:8333 (outbound)
2018-04-11 23:59:58.513 [INF] BTCN: Disconnecting peer 89.163.146.185:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.514 [INF] BTCN: Lost peer 89.163.146.185:8333 (outbound)
2018-04-11 23:59:58.526 [INF] BTCN: Disconnecting peer 96.43.135.210:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.526 [INF] BTCN: Lost peer 96.43.135.210:8333 (outbound)
2018-04-11 23:59:58.625 [INF] BTCN: Disconnecting peer 49.64.216.82:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.625 [INF] BTCN: Lost peer 49.64.216.82:8333 (outbound)
2018-04-11 23:59:58.677 [INF] BTCN: Disconnecting peer 79.160.18.218:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.677 [INF] BTCN: Lost peer 79.160.18.218:8333 (outbound)
2018-04-11 23:59:58.759 [INF] BTCN: Disconnecting peer 185.101.93.105:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.759 [INF] BTCN: Lost peer 185.101.93.105:8333 (outbound)
2018-04-11 23:59:58.809 [INF] BTCN: Disconnecting peer [2002:43db:9616::43db:9616]:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.809 [INF] BTCN: Lost peer [2002:43db:9616::43db:9616]:8333 (outbound)
2018-04-11 23:59:58.860 [INF] BTCN: Disconnecting peer 176.9.42.4:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.860 [INF] BTCN: Lost peer 176.9.42.4:8333 (outbound)
2018-04-11 23:59:58.911 [INF] BTCN: Disconnecting peer [2a02:e00:fff0:1b9::a]:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.931 [INF] BTCN: Lost peer [2a02:e00:fff0:1b9::a]:8333 (outbound)
2018-04-11 23:59:58.931 [INF] LNWL: Opened wallet
2018-04-11 23:59:59.370 [INF] BTCN: Disconnecting peer 5.135.215.19:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:59.371 [INF] BTCN: Lost peer 5.135.215.19:8333 (outbound)
2018-04-11 23:59:59.576 [INF] BTCN: Disconnecting peer 39.72.4.56:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:59.576 [INF] BTCN: Lost peer 39.72.4.56:8333 (outbound)
2018-04-12 00:00:00.038 [INF] BTCN: Disconnecting peer 103.82.56.24:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.039 [INF] BTCN: Lost peer 103.82.56.24:8333 (outbound)
2018-04-12 00:00:00.172 [INF] BTCN: Disconnecting peer 173.249.39.131:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.173 [INF] BTCN: Lost peer 173.249.39.131:8333 (outbound)
2018-04-12 00:00:00.254 [INF] BTCN: Disconnecting peer 43.229.76.49:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.255 [INF] BTCN: Lost peer 43.229.76.49:8333 (outbound)
2018-04-12 00:00:00.295 [INF] BTCN: Disconnecting peer 94.110.16.97:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.295 [INF] BTCN: Lost peer 94.110.16.97:8333 (outbound)
2018-04-12 00:00:00.375 [INF] BTCN: Disconnecting peer 78.227.49.100:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.376 [INF] BTCN: Lost peer 78.227.49.100:8333 (outbound)
2018-04-12 00:00:00.461 [INF] BTCN: Disconnecting peer 5.9.2.145:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.462 [INF] BTCN: Lost peer 5.9.2.145:8333 (outbound)
2018-04-12 00:00:00.732 [INF] BTCN: Disconnecting peer 27.217.15.63:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.732 [INF] BTCN: Lost peer 27.217.15.63:8333 (outbound)
2018-04-12 00:00:00.829 [INF] BTCN: Disconnecting peer 72.177.89.166:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.829 [INF] BTCN: Lost peer 72.177.89.166:8333 (outbound)
2018-04-12 00:00:01.281 [INF] BTCN: Disconnecting peer 103.45.236.44:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.282 [INF] BTCN: Lost peer 103.45.236.44:8333 (outbound)
2018-04-12 00:00:01.382 [INF] BTCN: Disconnecting peer 103.45.236.44:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.383 [INF] BTCN: Lost peer 103.45.236.44:8333 (outbound)
2018-04-12 00:00:01.497 [INF] BTCN: Disconnecting peer 88.202.180.233:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.497 [INF] BTCN: Lost peer 88.202.180.233:8333 (outbound)
2018-04-12 00:00:01.504 [INF] BTCN: Disconnecting peer 193.110.113.28:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.504 [INF] BTCN: Lost peer 193.110.113.28:8333 (outbound)
2018-04-12 00:00:01.725 [INF] BTCN: Disconnecting peer 95.163.71.126:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.725 [INF] BTCN: Lost peer 95.163.71.126:8333 (outbound)
2018-04-12 00:00:01.775 [INF] BTCN: Disconnecting peer 49.64.216.200:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.776 [INF] BTCN: Lost peer 49.64.216.200:8333 (outbound)
2018-04-12 00:00:01.792 [INF] BTCN: Disconnecting peer 35.184.79.142:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.793 [INF] BTCN: Lost peer 35.184.79.142:8333 (outbound)
2018-04-12 00:00:01.987 [INF] BTCN: Disconnecting peer 141.226.254.221:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.987 [INF] BTCN: Lost peer 141.226.254.221:8333 (outbound)
2018-04-12 00:00:02.094 [INF] BTCN: Disconnecting peer 54.37.84.178:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.094 [INF] BTCN: Lost peer 54.37.84.178:8333 (outbound)
2018-04-12 00:00:02.233 [INF] BTCN: Disconnecting peer 58.208.120.20:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.233 [INF] BTCN: Lost peer 58.208.120.20:8333 (outbound)
2018-04-12 00:00:02.234 [INF] BTCN: Disconnecting peer [2a02:27a8:0:1:acdc:77:0:9b]:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.235 [INF] BTCN: Lost peer [2a02:27a8:0:1:acdc:77:0:9b]:8333 (outbound)
2018-04-12 00:00:02.330 [INF] BTCN: Disconnecting peer 46.4.65.10:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.330 [INF] BTCN: Lost peer 46.4.65.10:8333 (outbound)
2018-04-12 00:00:02.428 [INF] BTCN: Disconnecting peer [2403:9800:c048:a10:960c:6dff:fe80:61b]:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.429 [INF] BTCN: Lost peer [2403:9800:c048:a10:960c:6dff:fe80:61b]:8333 (outbound)
2018-04-12 00:00:02.447 [INF] BTCN: Disconnecting peer [2001:638:a000:4140::ffff:191]:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.447 [INF] BTCN: Lost peer [2001:638:a000:4140::ffff:191]:8333 (outbound)
2018-04-12 00:00:02.637 [INF] BTCN: Disconnecting peer [2604:67c0:2001::2]:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.637 [INF] BTCN: Lost peer [2604:67c0:2001::2]:8333 (outbound)
2018-04-12 00:00:02.729 [INF] BTCN: Disconnecting peer 98.7.64.249:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.729 [INF] BTCN: Lost peer 98.7.64.249:8333 (outbound)
2018-04-12 00:00:02.826 [INF] BTCN: Disconnecting peer 31.3.135.183:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.826 [INF] BTCN: Lost peer 31.3.135.183:8333 (outbound)
2018-04-12 00:00:03.310 [INF] BTCN: Disconnecting peer 114.219.7.100:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:03.311 [INF] BTCN: Lost peer 114.219.7.100:8333 (outbound)
2018-04-12 00:00:03.713 [INF] BTCN: Disconnecting peer 180.106.133.61:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:03.713 [INF] BTCN: Lost peer 180.106.133.61:8333 (outbound)
2018-04-12 00:00:05.098 [INF] LNWL: The wallet has been unlocked without a time limit
2018-04-12 00:00:05.098 [INF] LTND: LightningWallet opened
2018-04-12 00:00:05.108 [INF] LNWL: Catching up block hashes to height 382320, this will take a while...
2018-04-12 00:00:05.124 [INF] LNWL: Done catching up block hashes
2018-04-12 00:00:05.127 [INF] HSWC: Restoring in-memory circuit state from disk
2018-04-12 00:00:05.127 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0
2018-04-12 00:00:05.136 [INF] LNWL: Started rescan from block 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f (height 0) for 0 addresses
2018-04-12 00:00:05.137 [INF] LNWL: Catching up block hashes to height 0, this might take a while
2018-04-12 00:00:05.155 [INF] LNWL: Done catching up block hashes
2018-04-12 00:00:05.155 [INF] LNWL: Finished rescan for 0 addresses (synced to block 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, height 0)
2018-04-12 00:00:05.159 [INF] RPCS: RPC server listening on 127.0.0.1:10009
2018-04-12 00:00:05.160 [INF] LTND: Waiting for chain backend to finish sync, start_height=0
2018-04-12 00:00:05.160 [INF] RPCS: gRPC proxy started at 127.0.0.1:8080
2018-04-12 00:02:12.423 [INF] BTCN: Disconnecting peer 94.199.178.17:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:12.423 [INF] BTCN: Lost peer 94.199.178.17:8333 (outbound)
2018-04-12 00:02:12.479 [INF] BTCN: Disconnecting peer 82.136.99.98:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:12.480 [INF] BTCN: Lost peer 82.136.99.98:8333 (outbound)
2018-04-12 00:02:12.594 [INF] BTCN: Disconnecting peer 91.211.191.15:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:12.595 [INF] BTCN: Lost peer 91.211.191.15:8333 (outbound)
2018-04-12 00:02:12.995 [INF] BTCN: Disconnecting peer [2002:674a:7892::674a:7892]:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:12.996 [INF] BTCN: Lost peer [2002:674a:7892::674a:7892]:8333 (outbound)
2018-04-12 00:02:17.629 [INF] BTCN: Disconnecting peer 212.51.14.72:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:17.630 [INF] BTCN: Lost peer 212.51.14.72:8333 (outbound)
2018-04-12 00:02:17.694 [INF] BTCN: Disconnecting peer 185.181.176.246:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:17.695 [INF] BTCN: Lost peer 185.181.176.246:8333 (outbound)
2018-04-12 00:02:17.879 [INF] BTCN: Disconnecting peer 208.93.231.240:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:17.879 [INF] BTCN: Lost peer 208.93.231.240:8333 (outbound)
2018-04-12 00:02:17.967 [INF] BTCN: Disconnecting peer 78.46.221.56:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:17.968 [INF] BTCN: Lost peer 78.46.221.56:8333 (outbound)
2018-04-12 00:02:18.208 [INF] BTCN: Disconnecting peer 58.56.252.254:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:18.209 [INF] BTCN: Lost peer 58.56.252.254:8333 (outbound)
2018-04-12 00:02:18.393 [INF] BTCN: Disconnecting peer 46.188.55.31:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:18.393 [INF] BTCN: Lost peer 46.188.55.31:8333 (outbound)
2018-04-12 00:02:18.554 [INF] BTCN: Disconnecting peer [2001:41f0:0:4:62:6974:636f:696e]:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:18.555 [INF] BTCN: Lost peer [2001:41f0:0:4:62:6974:636f:696e]:8333 (outbound)
2018-04-12 00:02:18.996 [INF] BTCN: Disconnecting peer [2002:45ac:57a7::45ac:57a7]:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:18.996 [INF] BTCN: Lost peer [2002:45ac:57a7::45ac:57a7]:8333 (outbound)
2018-04-12 00:02:19.023 [INF] BTCN: Disconnecting peer 101.180.234.134:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:19.023 [INF] BTCN: Lost peer 101.180.234.134:8333 (outbound)
2018-04-12 00:02:19.111 [INF] BTCN: Disconnecting peer 94.242.232.92:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:19.111 [INF] BTCN: Lost peer 94.242.232.92:8333 (outbound)
2018-04-12 00:02:19.592 [INF] BTCN: Disconnecting peer 180.107.22.33:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:19.593 [INF] BTCN: Lost peer 180.107.22.33:8333 (outbound)
2018-04-12 00:02:19.735 [INF] BTCN: Disconnecting peer 217.73.91.118:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:19.735 [INF] BTCN: Lost peer 217.73.91.118:8333 (outbound)
2018-04-12 00:02:20.088 [INF] BTCN: Disconnecting peer 32.209.17.99:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:20.089 [INF] BTCN: Lost peer 32.209.17.99:8333 (outbound)
2018-04-12 00:02:20.220 [INF] BTCN: Disconnecting peer [2a00:1a48:7810:101:be76:4eff:fe08:c774]:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:20.220 [INF] BTCN: Lost peer [2a00:1a48:7810:101:be76:4eff:fe08:c774]:8333 (outbound)
^C
|
|
|
|
So, lnd has been updated again, it's 0.4.1 now, so I thought why not to update on the PI too... I'm writing this post because the update was not as easy as 1-2-3 (OK, maybe just for me, but anyway) So I've logged in to the PI, and changed the working directory to the lnd source: cd $GOPATH/src/github.com/lightningnetwork/lnd After, I've started the update with a git pull command, but got this error message: pi@Lightning1:~/projects/src/github.com/lightningnetwork/lnd $ git pull remote: Counting objects: 4, done.
remote: Total 4 (delta 3), reused 4 (delta 3), pack-reused 0
Unpacking objects: 100% (4/4), done.
From https://github.com/lightningnetwork/lnd
12cb35a6..bc029b9c master -> origin/master
Updating a0fe4fb7..bc029b9c
error: Your local changes to the following files would be overwritten by merge:
Gopkg.lock
config.go
Please commit your changes or stash them before you merge.
Aborting
So something has been changed locally, but I don't need those changes (I guess), so I was about to discard those changes and let the pull sync my local copy of the lnd code, but I had no clue what to do (this is my first time I've used git, so pardon me) After heavy googling, I've found the solution here: https://techsparx.com/software-development/git/reset-local-changes.htmlSo I have used this: After, the was OK, it run without any error. My problem is that my lnd neutrino node can't find any node to connect to, so I'm still struggling with it, but somehow sometime I'll get it working... |
|
|
|
I came across in a news where I read that the coming FIFA WorldCup is going to be hosted in Russia and in this worldcup Russia has decided to support bitcoin in a way that it will accept bitcoin in their hotels for getting rooms by the visitors and for all other facilities they will need. Then it is sure that the coming June is coming with a great boost in the price of bitcoin as we all are the crazy of football and we all will need to buy bitcoin to pay for these hotels. So the demand will be increased and it is also sure that the community of it will increase much more.
This is great news, however I can only imagine to accept bitcoin for hotels to pay in bitcoin in advance. The ligthning network is not ready yet, so if there will be a huge demand, the transactions will stuck again, so you won't be able to pay for the room with your bitcoin in the morning when you're rushing to the airport... Another interesting thing is, if you pay with bitcoin in advance (e.g. 50% of the room price) and the bitcoin price will be doubled by the time you get to the hotel, will that mean that you have payed the whole price of the room already, because of the price raise? |
|
|
|
|
If you want to spend frequently from the wallet, buy a hardware wallet, it's the easiest way.
You should search the forum before asking these kind of questions, there are tons of thread asking for secure wallets, so there's no use to open a similar thread every day. Read a lot and after if you are still in a doubt, ask a specific question, someone will surely help.
|
|
|
|
...
Well, bitcoin debit cards are nothing new on the market. There are several providers that offer such services like Xapo, Advcash, Wirex etc. They are usualy Visa or Master cards but credit cards are still not available, only debit. The advantage is that you can spend your bitcoins in the shops like with any other card orr withdraw the cash at the ATM .
But I'm not sure I understud what is the actual idea of the project that has been introduced here so I would like more details. But I'd like to see bitcoin cards to be developed further.
Just don't forget that most of the bitcoin debit card were shut down, because the issuer (WaveCrest) had not fullfilled VISA's expectations so VISA has banned all the cards, issued by WaveCrest. This means that XAPO and the others are not able to provide the debit cards at the moment. There are only a few of the debit cards available still, but you should have a detailed identification in order to be able to use that card. As banks (and VISA and MasterCard) is (understandably) against bitcoin, I can't see any positive news in connection with the bitcoin debit cards in the near future, unfortunately. |
|
|
|
It's interesting to see how these top business schools are aware of the future of bitcoin and the role that it will play in the world in the coming years. With regard to the question raised, I think that the effect of these classes in schools would be positive since people would be familiar with bitcoin from a young age.
Maybe the business schools are not aware of the future of bitcoin, but this is a kind of fancy course so why not to include it in the curriculum. It will draw the attention of the youth, so they will most likely choose this school instead of the other where there's nothing about blockchain. This can also be a point. On the other hand, I'm sure that if those young people are not too lazy, they would find (nearly) everything on the internet. If they are really interested, they don't need a class about it because they will search for it in their freetime and they will discuss it when having a beer with the classmates in the pub. |
|
|
|
Hate to bump my own thread, but the money is still just sitting there.
You should advertise it in the local newspapers  I would be happy to go to a trip to the location but to get there and to get home would cost much more than the value of the bitcoins in the wallet (maybe if the price of bitcoin will rise again around $20.000 there would be more interest finding that wallet...) |
|
|
|
Don't blame yourself at all. It's an honor to be part of this campaign, so I think I can speak on behalf of everyone, when I say that it's OK to wait if it's needed, there's no problem at all. Thanks for the regular payments, anyway |
|
|
|
Are you sure, that it's not a fake?
As far as I heard, Soros said recently that the crypto-currencies won't finish well and sooner or later they will die.
Maybe he is already in short position and this is the manipulation to let the price go even more down. Or, maybe he is preparing to buy even more lower, this is why he's trying to move the market... |
|
|
|
Nobody will support this idea, believe me. The main reason is Merit system was made to award quality posters, to stay away shitposters and spammers from ranking up. Your idea may look helpful, but it is not what for merit system was created.
OK, understood. I'm thinking about locking this thread in order to prevent shitposters/spammers starting to post their one liners here too (I don't know if they like the Meta section or not...) |
|
|
|
This would result in a lot of spammers creating fake accounts to copy-paste and report them with their main accounts.
We would have a increase in the number of copy-pasted posts and reports. Mods wouldn't be able to ban everyone and we would have even more shitposts (and spammers would be rewarded with underserved merit points).
That's a serious objection, you're right. The problem is, I cannot think the way like a spammer/shitposter do, so I haven't even thought that my idea can cause a bigger problem instead of helping the system. |
|
|
|
|
Fine for me, it was just an idea...
Just a thought: the new generation of un-knowledgeable but merited users already exist (the merit abusers) and we cannot prevent people meriting their alts, only if it's a real abuse (giving like 5-10 merits to a e.g. newbie for an average post)
I think my idea is not the kind of merit giveaway that would ruin the whole merit system...
But OK, it seems it was not a good idea...
|
|
|
|
First of all, I don't want to get merit for reporting copypasters. Also, I don't hunt for copypasters, I only find them accidentally as I read thru the topics. I usually report them in the appropirate thread: https://bitcointalk.org/index.php?topic=1926895.0It takes time and it's not my favorite task anyway... So why not offer a merit to the users after successfully reporting 10 or 20 (or 25 or even more) copypasters? (not spammers, because it's much harder to prove and to decide) they will get the merit after the copypasters are banned, not automatically. The users at lower ranks will fight for the merit and it will help to clear the forum from the copypasters (at least). Just an idea, why not to let the forum to clear itself, it will reduce the tasks of the admin staff |
|
|
|
Keep in mind that government backed crypto's will be fully centralized!
But, good thing is that will reduce corruption, because every transaction is stored in blockchain and can not be changed!
This won't reduce the corruption this will only help the country to make the black/grey economy a bit more traceable (transactions between companies and people or between people). Governments will be smart enough (if they develop their own system) to find a way to preserve the 'old' channels too at least for a while and it won't stop the corruption... |
|
|
|
Banks were initially designed to store money. But eventually scopes and aims of banks have changed. Cryptocurency is the new possibility. We won’t have to pay to any third party for storing our money and then for spending our money. I think, if everything goes right for Crypto, tasks of Bank will become very limited in future.
It's only valid if we think about the wire transfer service of the Banks (on the short run). It needs much more time to implement such features for cryptos that can create a competition to banks e.g. in loans, investments, etc. ICOs are a good competitor to IPOs on the stock market, and crypto exchanges are competitors to forex companies. But banks have so much services to customers, not all of them (tbh just a little part of them) are covered with the proper crypto services now. |
|
|
|
This would not be a surprise if it happens. Already many countries have said about their intentions of doing the same thing. The blockchain will bring many advantages to the country such as regulatory compliance, transparency, quality assurance, smart contracts, etc. And yes, the government will surely ignore Bitcoin as they will never want cryptocurrencies to replace the fiat currency.
They don't want it to replace the fiat money, but they can accept it, like it was a currency of a foreign country. In this case, bitcoin can be accepted and of course, taxed. Like you are not forced to use your national fiat in your country, it's just easier to use that. If you want, you can use USD in the EU countries, they will accept your USD fiat (or you have it exchanged to the local currency) but it's an accepted currency. This can happen to bitcoin, if the countries will regulate (and accept) it. When you pay with your debit/credit card, the merchant doesn't care if the card is denominated in EUR or USD, in the end they will have the money, this can be true for bitcoin too, if you will use a bitcoin debit card (if there will be a working one with cheap fees), merchants won't care about it, they will accept it if the card will be a VISA or MasterCard. The situation will be a bit different if it's about direct bitcoin payments... |
|
|
|
|
Show Posts
