Last night I ordered a pizza for my family and I. I used a gift card to pay. I don’t carry cash but I have a bunch of unused paper wallets. When the delivery girl got to my house I asked, “Do you use bitcoin?” I could tell she knew of it, but wasn’t to familiar. So, I told her I want to tip her, but would she accept bitcoin. Her eyes lit up and she agreed.

So, I grabbed a spare paper wallet, scanned the QR code, sent the tip, gave her the wallet, and before she left I told her to google “bitcoin paper wallet cash out” or something like that if she wants fiat. She genuinely seemed excited.

I did same thing a few days ago and that delivery boy had the same reaction.

For people who are unsure or skeptical, I think this is a good idea for everyone in the space bc 1)it’s a direct connection to one’s labor, 2) the face-to-face voluntary transaction of tipping is apart of the Satoshi ethos, 3)its something physical, 4)the physical paper will help them understand the abstract aspect of money and 5)it creates a financial incentive for them to give bitcoin cursory examination, at least.

At that point, I hope they continue  down the Rothbardian hole and see the fed (and all central banking) for the criminal instruction they are.

Thoughts?

Excuse any ignorance I may have and please consider that I am attempting to use Cunningham's Law here; posting the wrong answer and waiting for someone to correct me.

Could modular exponentiation, some form of modular math (a concept that I’m new to), or some other mathematical computation be used to infinitely scale bitcoin?

Im this case, a block wouldn’t be an aggregate of the block data but a mathematical computation that (when solved) reveals the data of the block. Similar to a trapdoor function. Bc the data requirement for a single function is much smaller than the result of the aggregate block data (esp. as it grows) and the computation required is “simple” when the trapdoor is solution is available. So, a theoretically infinite amount of transactions could exist in a single computation. The difficulty in finding this trapdoor might be prohibitive, but I could it be reasonable?

root@60009:~# sudo apt install -y software-properties-common
Reading package lists... Done
Building dependency tree       
Reading state information... Done
software-properties-common is already the newest version.
The following package was automatically installed and is no longer required:
  libdb4.8
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@60009:~# sudo add-apt-repository ppa:bitcoin/bitcoin
 Stable Channel of bitcoin-qt and bitcoind for Ubuntu, and their dependencies

Note that you should prefer to use the official binaries, where possible, to limit trust in Launchpad/the PPA owner.

No longer supports precise, due to its ancient gcc and Boost versions.
 More info: https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin
Press [ENTER] to continue or ctrl-c to cancel adding it

gpg: keyring `/tmp/tmpmg6m7ve7/secring.gpg' created
gpg: keyring `/tmp/tmpmg6m7ve7/pubring.gpg' created
gpg: requesting key 8842CE5E from hkp server keyserver.ubuntu.com
gpg: /tmp/tmpmg6m7ve7/trustdb.gpg: trustdb created
gpg: key 8842CE5E: public key "Launchpad PPA for Bitcoin" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
OK
root@60009:~# sudo apt update && sudo apt upgrade -y && sudo apt install -y build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils libboost-all-dev libdb4.8-dev libdb4.8++-dev python-virtualenv nano git libminiupnpc-dev libdb-dev libdb++-dev libboost1.54-all-dev
Ign http://ubuntu-archive.mirror.serveriai.lt trusty InRelease
Hit http://ubuntu-archive.mirror.serveriai.lt trusty-updates InRelease         
Hit http://ubuntu-archive.mirror.serveriai.lt trusty Release.gpg               
Hit http://ubuntu-archive.mirror.serveriai.lt trusty Release                   
Hit http://ubuntu-archive.mirror.serveriai.lt trusty-updates/main amd64 Packages
Hit http://ubuntu-archive.mirror.serveriai.lt trusty-updates/restricted amd64 Packages
Hit http://ubuntu-archive.mirror.serveriai.lt trusty-updates/universe amd64 Packages
Hit http://ubuntu-archive.mirror.serveriai.lt trusty-updates/main i386 Packages
Hit http://ubuntu-archive.mirror.serveriai.lt trusty-updates/restricted i386 Packages
Hit http://ubuntu-archive.mirror.serveriai.lt trusty-updates/universe i386 Packages
Hit http://ubuntu-archive.mirror.serveriai.lt trusty-updates/main Translation-en
Hit http://ubuntu-archive.mirror.serveriai.lt trusty-updates/restricted Translation-en
Hit http://ubuntu-archive.mirror.serveriai.lt trusty-updates/universe Translation-en
Hit http://ubuntu-archive.mirror.serveriai.lt trusty/main amd64 Packages       
Hit http://ubuntu-archive.mirror.serveriai.lt trusty/restricted amd64 Packages
Hit http://ubuntu-archive.mirror.serveriai.lt trusty/universe amd64 Packages   
Hit http://ubuntu-archive.mirror.serveriai.lt trusty/main i386 Packages       
Hit http://ubuntu-archive.mirror.serveriai.lt trusty/restricted i386 Packages 
Hit http://ubuntu-archive.mirror.serveriai.lt trusty/universe i386 Packages   
Hit http://ubuntu-archive.mirror.serveriai.lt trusty/main Translation-en       
Hit http://ppa.launchpad.net trusty InRelease                                 
Hit http://ubuntu-archive.mirror.serveriai.lt trusty/restricted Translation-en
Hit http://ubuntu-archive.mirror.serveriai.lt trusty/universe Translation-en   
Ign http://archive.canonical.com trusty InRelease                             
Hit http://ppa.launchpad.net trusty/main amd64 Packages                       
Hit http://ppa.launchpad.net trusty/main i386 Packages                         
Hit http://archive.canonical.com trusty Release.gpg                           
Hit http://ppa.launchpad.net trusty/main Translation-en                       
Hit http://archive.canonical.com trusty Release                               
Hit http://archive.canonical.com trusty/partner amd64 Packages                 
Hit http://archive.canonical.com trusty/partner i386 Packages                 
Hit http://archive.canonical.com trusty/partner Translation-en                 
Hit http://security.ubuntu.com trusty-security InRelease                       
Hit http://security.ubuntu.com trusty-security/main amd64 Packages
Hit http://security.ubuntu.com trusty-security/restricted amd64 Packages
Hit http://security.ubuntu.com trusty-security/universe amd64 Packages
Hit http://security.ubuntu.com trusty-security/multiverse amd64 Packages
Hit http://security.ubuntu.com trusty-security/main i386 Packages
Hit http://security.ubuntu.com trusty-security/restricted i386 Packages
Hit http://security.ubuntu.com trusty-security/universe i386 Packages
Hit http://security.ubuntu.com trusty-security/multiverse i386 Packages       
Hit http://security.ubuntu.com trusty-security/main Translation-en             
Hit http://security.ubuntu.com trusty-security/multiverse Translation-en       
Hit http://security.ubuntu.com trusty-security/restricted Translation-en       
Hit http://security.ubuntu.com trusty-security/universe Translation-en         
Reading package lists... Done                                                 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  libdb4.8
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
autotools-dev is already the newest version.
bsdmainutils is already the newest version.
build-essential is already the newest version.
libdb++-dev is already the newest version.
libdb-dev is already the newest version.
libtool is already the newest version.
libminiupnpc-dev is already the newest version.
libboost1.54-all-dev is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libdb++-dev : Conflicts: libdb4.8++-dev but 4.8.30-trusty1 is to be installed
 libdb-dev : Conflicts: libdb4.8-dev but 4.8.30-trusty1 is to be installed
 libdb4.8++-dev : Conflicts: libdb++-dev
 libdb5.3++-dev : Conflicts: libdb4.8++-dev but 4.8.30-trusty1 is to be installed
 libdb5.3-dev : Conflicts: libdb4.8-dev but 4.8.30-trusty1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

After putting the above command I get the following:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libdb++-dev : Conflicts: libdb4.8++-dev but 4.8.30-trusty1 is to be installed
 libdb-dev : Conflicts: libdb4.8-dev but 4.8.30-trusty1 is to be installed
 libdb4.8++-dev : Conflicts: libdb++-dev
 libdb5.3++-dev : Conflicts: libdb4.8++-dev but 4.8.30-trusty1 is to be installed
 libdb5.3-dev : Conflicts: libdb4.8-dev but 4.8.30-trusty1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

What is soon? Days, weeks, months?

I put https://coinsmarkets.com/api.php A trading looking object came up, but seemed to have no functionality.

I’ve sent two BTC deposits from two different wallets to no avail. Super irritating since coinsmarkets went down.

I submitted a ticket. Do you have any update?