Here is the latest chart of Log10 delta from trend, which is most helpful when considering relative bitcoin price bubbles . . . The three charts and calculations of my logistic price model are published in a shared Google spreadsheet here. If we name the zone below -0.3 as the ridiculous rock-bottom slam-dunk buy zone, we are now in the middle of it at -0.35. Yes, and accordingly I will think about you and your fount of good advice when I make my almost daily trek to the ATM to buy some fractional bitcoin. |
|
|
|
CPoS Network ProxyI have been thinking about a way to deploy CPoS in a way that minimally impacts Bitcoin Core, and their pull request regime. The idea is to have CPoS code execute as a network proxy for bitcoind - the Bitcoin Core program. A paid CPoS full node operator would launch the CPoS program - preferably automatically upon start of the server, The CPoS proxy would configure its bitcoind to have a single peer, namely the collocated proxy. That bitcoind, by default, would have generation turned off. The CPoS proxy would connect to other such proxies forming the super peer network described in my whitepaper. All the agent related code would be implemented in the proxy. The proxy-to-bitcoind communication protocol code would be adapted from bitcoind source code for complete compatibility. The proxy-to-proxy communication protocol would be inspired by FIPA agent-to-agent protocol. The single nomadic mint would launch bitcoind every 10 minutes, and configure it to generate the new block. After creating the new block, the mint would shut down its bitcoind. Alternatively if the bitcoind RPC (remote procedure call) interface permits sufficiently robust dynamic control of block generation, then that would be preferable. Bitcoind would verify transactions received from the proxy and build the blockchain replica with new blocks provided by the single nomadic mint agent via the proxy. The full-node's tamper-evident log would be maintained by the proxy. The bitcoind instance would listen on its standard Internet port for SPV nodes, e.g. mobile wallets, and process their requests. For full nodes desiring local Bitcoin-QT wallets, the proxy would launch the wallet after launching bitcoind. The wallet would communicate with bitcoind directly, and not the proxy. If and when the blockchain hard fork planned for early 2016 succeeds, the proxy code I write can be merged into the bitcoind code for a single program by willing core developers. This possibility constrains me to write the proxy in the language of bitcoind, which is C++ and the Boost library. -Stephen Reed
|
|
|
|
I am pretty confidant I am not the new wealthy elite  . Maybe one day though  . The awesomeness of Bitcoin is revealed by simply holding some over a multi-year period. Eventually one feels the exhilaration of the original poster. |
|
|
|
Here is the latest chart of Log10 delta from trend, which is most helpful when considering relative bitcoin price bubbles . . .  The three charts and calculations of my logistic price model are published in a shared Google spreadsheet here. |
|
|
|
..If BTC is doing its yearly wave, I can capture maybe 30% of the downtrend with 30% of my position, resulting in a 13% gain in my holdings...
Why so conservative in your estimations? The previous bubbles have had at least 3 times retracement from the top. Catching at least 50 percent wouldnt be that much of a problem? I plan to follow Risto's guidance with regard to the percentage of holdings to trade. I would like to capture 50% of the move - hoping for a double, but I would settle for less. My trades would be so small as to not effect the market, unlike the same percentage of Risto's holdings. Timing the peak could be different this time around, in that November 2013 had a pre-peak at $731 before the actual peak at $1163. I expect perhaps multiple of those pre-peak super-exponential rallies that mislead timers such as me. |
|
|
|
Hi SlipperySlope, You have two links of mine on the original post, but the first (Venetian Bankers Problem) is deprecated in favor of TenderMint. Also, the TenderMint link is broken due to a trailing slash. The link should be: http://tendermint.com/docs/tendermint_v04.pdfI removed the Venetian Bankers Problem link and fixed the TenderMint link. Thanks for pointing out my errors. Its interesting that defenders of Bitcoin proof-of-work believe Satoshi's Bitcoin to be the solution to the Byzantine General's Problem, or more generally the only working solution to achieving concensus in a distributed system. But the academic field of Byzantine Fault Tolerance does not mention bitcoin with the notable exception of Andrew Miller's paper whose only citation is from me. Even when granted that the bulk of such papers were issued before 2009, Satoshi did not reference any in his defining Bitcoin paper nor stimulate much discussion of BFT algorithms when posting to this forum. Google Scholar search for Byzantine Fault Tolerance-Stephen Reed |
|
|
|
It appears that Litecoin, and probably other altcoins as well, are late to this recent bitcoin rally. Here is the BitcoinWisdom 3-day resolution chart for the LTC/BTC currency pair. Observe how litecoin has fallen in price relative to bitcoin, especially in the recent nine days. In the bubble that peaked last November, litecoin was late to the rally but then appreciated more rapidly than bitcoin. A good trade might be to wait until litecoin joins the rally and then switch a portion of the at-risk capital from long bitcoin to long litecoin or your favorite altcoin. At the peak, as you judge it, sell the altcoin, and wait to buy back later for a fraction of the peak price. This is not a trade for me as I have plenty of risk exposure in bitcoin and do not desire any more volatility.  |
|
|
|
[Thinking that the bubbles repeat the same pattern.. if SlipperySlope would post his chart of the relative valuation - at least last time they did.
The rightmost data point has a value of -0.373 .  |
|
|
|
Hi, I have come up with what I believe to be at least a partial solution to the PoS problem: https://bitcointalk.org/index.php?topic=553414.msg6025343#msg6025343The gist of it is that everybody's Stake is reduced to 0 on a frequent and random basis. If the node is provably connected to the network at the time that it is randomly called up, it will receive its proportional distribution for its Stake. If it does not prove itself to be connected to the network at such time, its Stake is still reset to 0, but it does not receive any payment. For this reason, I call it Proof-of-Connection. This effectively puts an upper limit on the amount of Stake that any one address could reasonably accumulate. Presumably, this would prevent against the "if you have enough Stake, you can cheaply re-write history" attack. Interesting, In CPoS, I would pay full nodes to upgrade to 24/7 dedicated symmetric business class Internet connections. The full nodes would be expected to be permanently connected and executing the current version of the reference Bitcoin Core software. Their share of the block creation reward, paid daily, would be decreased if not always connected. The daily bitcoin creation reward is now $2,124,360. I would allocate $30 daily to each full-time full node. |
|
|
|
Did you even watch the charts? The date we reach a million is even before 2020 and I don't know about you, but I don't plan to die before that.
Yes, I simply guessed at the $1 million maximum price for bitcoin. But whether that price is $20K or $100K or higher, the rate of growth before the mid point of adoption is approximately 10x annually according to results when I varied the model's parameters. I believe that if indeed the maximum price is $1 million then we will get there before 2020 according to my model. |
|
|
|
I introduced a new thought that is not in the whitepaper and that is that the block creation reward, in addition to funding infrastructure and developers, could also subsidize transactions to the extent of negative transaction fees, should the abuse problem be addressed. Imaging paying Amazon or any other global Internet retailer a week's worth of block creation rewards, i.e. $13 million to get them to accept bitcoins as payment. I call this notion paying for order flow.
Who gets to make these decisions? This sounds more and more like a startup willing to corner marketshare than a monetary system... Shares are not money. OK. That idea is not going to gain wide acceptance in the Bitcoin community. A proof-of-stake altcoin startup might try paying for order flow. I suggest that Bitcoin full node owners have an annual convention to tweak the reward allocation policy executed in code by what I call the Reward Agent. I would not change the Satoshi block reward schedule, that cuts the reward in half in the summer of 2016 and again in 2020. But I desire that the reward be rationally spent on facilitating the adoption of Bitcoin via superior infrastructure. |
|
|
|
Meanwhile Bitcoin moving strongly upwards.  |
|
|
|
I presented my whitepaper today and engaged contributors to the Bitshares project on the Beyond Bitcoin podcast . . . https://bitsharestalk.org/index.php?topic=4713.0I was invited back for a more technical discussion after I have a chance to re-study Dan Larimer's Delegated Proof-of-Stake (DPOS)I introduced a new thought that is not in the whitepaper and that is that the block creation reward, in addition to funding infrastructure and developers, could also subsidize transactions to the extent of negative transaction fees, should the abuse problem be addressed. Imaging paying Amazon or any other global Internet retailer a week's worth of block creation rewards, i.e. $13 million to get them to accept bitcoins as payment. I call this notion paying for order flow. |
|
|
|
Thanks for mentioning my project. I am only beginning to integrate my work into Bitcoin. The Bitcoin core developers are skeptical yet encouraging, and await "neat technology". Very likely my code will be implemented into one or more altcoins next year, in parallel with system testing on a Bitcoin testnet. If the proposed system can pass all the challenging tests proposed by skeptics, then I believe that I win over many of not most of those whose approval I need before a hard-fork of Bitcoin. I would like to keep this thread focused on technical analysis - and my project is far, far from influencing price. A year from now I hope that situation changes. |
|
|
|
Altcoins are wicked risky, but the reward can be immense. Look at Mooncoin now: only worth a few Litoshis now but once 30 Satoshis......
Its all about momentum and a lot of patience.
Bitcoin has increased in price on average 10x annually. That is quite enough risk / reward for me. I get nervous whenever I sell bitcoin waiting for the price to go lower. Much better to be long in bitcoin except for the bubble peak - as Risto has guided me. |
|
|
|
GitHub notes . . . Bitcoin GitHub repository ========================= $ git clone git@github.com:StephenLReed/bitcoin.git
$ cd bitcoin
Synchronizing the my bitcoin branch with the origin bitcoin repository https://help.github.com/articles/syncing-a-fork# initialize my local bitcoin branch repository
$ git clone git@github.com:StephenLReed/bitcoin.git
Cloning into 'bitcoin'...
Warning: Permanently added the RSA host key for IP address '192.30.252.130' to the list of known hosts.
remote: Counting objects: 36043, done.
remote: Compressing objects: 100% (9795/9795), done.
remote: Total 36043 (delta 26003), reused 36043 (delta 26003)
Receiving objects: 100% (36043/36043), 28.65 MiB | 611.00 KiB/s, done.
Resolving deltas: 100% (26003/26003), done.
Checking connectivity... done
$ cd bitcoin
# list the current remotes
$ git remote -v
origin git@github.com:StephenLReed/bitcoin.git (fetch)
origin git@github.com:StephenLReed/bitcoin.git (push)
# add the upstream remote repository
$ git remote add upstream https://github.com/bitcoin/bitcoin.git
# verify the current remotes
origin git@github.com:StephenLReed/bitcoin.git (fetch)
origin git@github.com:StephenLReed/bitcoin.git (push)
upstream https://github.com/bitcoin/bitcoin.git (fetch)
upstream https://github.com/bitcoin/bitcoin.git (push)
# Grab the upstream remote's branches
$ git fetch upstream
remote: Counting objects: 1142, done.
remote: Compressing objects: 100% (587/587), done.
remote: Total 1142 (delta 758), reused 805 (delta 553)
Receiving objects: 100% (1142/1142), 2.70 MiB | 569.00 KiB/s, done.
Resolving deltas: 100% (758/758), done.
From https://github.com/bitcoin/bitcoin
* [new branch] 0.6.2 -> upstream/0.6.2
* [new branch] 0.6.3 -> upstream/0.6.3
* [new branch] 0.7.2 -> upstream/0.7.2
* [new branch] 0.8.1 -> upstream/0.8.1
* [new branch] 0.8.3 -> upstream/0.8.3
* [new branch] 0.8.4 -> upstream/0.8.4
* [new branch] 0.8.5 -> upstream/0.8.5
* [new branch] 0.8.6 -> upstream/0.8.6
* [new branch] 0.9.0 -> upstream/0.9.0
* [new branch] 0.9.1 -> upstream/0.9.1
* [new branch] 0.9.2 -> upstream/0.9.2
* [new branch] blockheaders -> upstream/blockheaders
* [new branch] freenode-verf -> upstream/freenode-verf
* [new branch] master -> upstream/master
# List all local and remote-tracking branches
git branch -va
* master 4765b8c Merge pull request #4087
remotes/origin/0.6.2 40fd689 Bump version to 0.6.2.2 for osx-special build
remotes/origin/0.6.3 6e0c5e3 Revert "Update gitian descriptors to point at stable git repo"
remotes/origin/0.7.2 32a928e Use github for final 0.7.2 release
remotes/origin/0.8.1 34d62a8 Set version numbers for 0.8.1 release
remotes/origin/0.8.3 40809ae Bump version numbers for 0.8.3 release
remotes/origin/0.8.4 839c7d1 Update the bloom state on the real object, not the temporary one.
remotes/origin/0.8.5 ef14a26 Bump version numbers for 0.8.5 release
remotes/origin/0.8.6 03a7d67 Release notes for 0.8.6
remotes/origin/0.9.0 92d25e4 build: fix explicit --disable-qt-dbus
remotes/origin/0.9.1 026a939 gitian: Version bump for Qt dependency
remotes/origin/HEAD -> origin/master
remotes/origin/blockheaders b24aa4a Saving work...
remotes/origin/freenode-verf 7612e72 FreeNode verification
remotes/origin/master 4765b8c Merge pull request #4087
remotes/upstream/0.6.2 40fd689 Bump version to 0.6.2.2 for osx-special build
remotes/upstream/0.6.3 6e0c5e3 Revert "Update gitian descriptors to point at stable git repo"
remotes/upstream/0.7.2 32a928e Use github for final 0.7.2 release
remotes/upstream/0.8.1 34d62a8 Set version numbers for 0.8.1 release
remotes/upstream/0.8.3 40809ae Bump version numbers for 0.8.3 release
remotes/upstream/0.8.4 839c7d1 Update the bloom state on the real object, not the temporary one.
remotes/upstream/0.8.5 ef14a26 Bump version numbers for 0.8.5 release
remotes/upstream/0.8.6 03a7d67 Release notes for 0.8.6
remotes/upstream/0.9.0 92d25e4 build: fix explicit --disable-qt-dbus
remotes/upstream/0.9.1 026a939 gitian: Version bump for Qt dependency
remotes/upstream/0.9.2 2585310 Add missing LOCK(cs_main)
remotes/upstream/blockheaders b24aa4a Saving work...
remotes/upstream/freenode-verf 7612e72 FreeNode verification
remotes/upstream/master 97b53b5 Merge pull request #4152
# Check out our local master branch
$ git checkout master
Already on 'master'
# Merge upstream's master into our own
$ git merge upstream/master
Updating 4765b8c..97b53b5
Fast-forward
.tx/config | 7 +
Makefile.am | 4 +-
configure.ac | 47 +-
contrib/debian/bitcoin-qt.install | 2 +-
contrib/debian/bitcoind.install | 3 +-
contrib/debian/changelog | 13 +
contrib/debian/control | 8 +-
contrib/debian/manpages/bitcoin.conf.5 | 3 -
contrib/debian/rules | 21 +-
contrib/devtools/README.md | 40 +-
contrib/devtools/symbol-check.py | 113 +++
contrib/devtools/update-translations.py | 66 ++
contrib/gitian-descriptors/gitian-linux.yml | 22 +-
contrib/gitian-descriptors/gitian-osx-bitcoin.yml | 65 ++
contrib/gitian-descriptors/gitian-osx-depends.yml | 160 ++++
contrib/gitian-descriptors/gitian-osx-native.yml | 179 ++++
contrib/gitian-descriptors/gitian-osx-qt.yml | 192 ++++
contrib/gitian-descriptors/qt-linux.yml | 263 +++++
contrib/macdeploy/macdeployqtplus | 4 +-
doc/README_osx.txt | 71 ++
doc/bootstrap.md | 7 +-
doc/build-unix.md | 43 +-
doc/release-process.md | 54 +-
doc/translation_process.md | 29 +-
qa/pull-tester/pull-tester.sh | 3 +
qa/rpc-tests/README.md | 29 +-
qa/rpc-tests/netutil.py | 134 +++
qa/rpc-tests/rpcbind_test.py | 152 +++
qa/rpc-tests/util.py | 32 +-
share/genbuild.sh | 2 +-
share/qt/Info.plist.in | 6 +-
src/Makefile.am | 2 +-
src/Makefile.include | 12 +-
src/base58.cpp | 183 ++++
src/base58.h | 259 +----
src/bignum.h | 595 ------------
src/bitcoin-cli.cpp | 2 +
src/bitcoind.cpp | 9 +-
src/chainparams.cpp | 6 +-
src/chainparams.h | 5 +-
src/compat.h | 10 +-
src/core.cpp | 4 +-
src/init.cpp | 26 +-
src/json/json_spirit_reader_template.h | 12 +-
src/json/json_spirit_value.h | 32 +-
src/key.cpp | 72 +-
src/key.h | 3 +
src/keystore.cpp | 3 +
src/leveldb/Makefile | 11 +-
src/leveldb/db/filename.cc | 9 +-
src/leveldb/db/log_reader.cc | 23 +-
src/leveldb/db/log_test.cc | 40 +-
src/leveldb/db/repair.cc | 1 -
src/leveldb/db/version_set.cc | 14 -
src/leveldb/include/leveldb/c.h | 1 -
src/leveldb/include/leveldb/db.h | 2 +-
src/leveldb/include/leveldb/slice.h | 2 +-
src/m4/ax_boost_base.m4 | 5 +-
src/main.cpp | 453 +++++----
src/main.h | 51 +-
src/miner.cpp | 15 +-
src/net.cpp | 67 +-
src/net.h | 8 +
src/netbase.cpp | 198 +++-
src/netbase.h | 36 +-
src/protocol.h | 1 +
src/qt/Makefile.am | 11 +-
src/qt/bitcoin.cpp | 24 +-
src/qt/bitcoin.qrc | 1 +
src/qt/bitcoingui.cpp | 17 +-
src/qt/bitcoingui.h | 2 +-
src/qt/bitcoinstrings.cpp | 1 +
src/qt/clientmodel.cpp | 14 +-
src/qt/clientmodel.h | 5 +-
src/qt/forms/optionsdialog.ui | 24 +
src/qt/forms/rpcconsole.ui | 33 +-
src/qt/locale/bitcoin_ach.ts | 1053 ++++----------------
src/qt/locale/bitcoin_af_ZA.ts | 1055 ++++-----------------
src/qt/locale/bitcoin_ar.ts | 1492 ++++++++---------------------
src/qt/locale/bitcoin_be_BY.ts | 1053 ++++----------------
src/qt/locale/bitcoin_bg.ts | 1271 ++++++-------------------
src/qt/locale/bitcoin_bs.ts | 1053 ++++----------------
src/qt/locale/bitcoin_ca.ts | 1053 ++++----------------
src/qt/locale/bitcoin_ca@valencia.ts | 1096 +++++----------------
src/qt/locale/bitcoin_ca_ES.ts | 1059 ++++-----------------
src/qt/locale/bitcoin_cmn.ts | 1096 +++++----------------
src/qt/locale/bitcoin_cs.ts | 1509 ++++++++---------------------
src/qt/locale/bitcoin_cy.ts | 1053 ++++----------------
src/qt/locale/bitcoin_da.ts | 1175 +++++------------------
src/qt/locale/bitcoin_de.ts | 1200 +++++------------------
src/qt/locale/bitcoin_el_GR.ts | 1101 ++++-----------------
src/qt/locale/bitcoin_en.ts | 123 ++-
src/qt/locale/bitcoin_eo.ts | 1061 ++++-----------------
src/qt/locale/bitcoin_es.ts | 1082 ++++-----------------
src/qt/locale/bitcoin_es_CL.ts | 1108 +++++-----------------
src/qt/locale/bitcoin_es_DO.ts | 1030 +++-----------------
src/qt/locale/bitcoin_es_MX.ts | 1055 ++++-----------------
src/qt/locale/bitcoin_es_UY.ts | 1053 ++++----------------
src/qt/locale/bitcoin_et.ts | 1057 ++++-----------------
src/qt/locale/bitcoin_eu_ES.ts | 1053 ++++----------------
src/qt/locale/bitcoin_fa.ts | 1065 ++++-----------------
src/qt/locale/bitcoin_fa_IR.ts | 1053 ++++----------------
src/qt/locale/bitcoin_fi.ts | 1713 ++++++++++-----------------------
src/qt/locale/bitcoin_fr.ts | 1069 ++++-----------------
src/qt/locale/bitcoin_fr_CA.ts | 1099 ++++-----------------
src/qt/locale/bitcoin_gl.ts | 1120 +++++-----------------
src/qt/locale/bitcoin_gu_IN.ts | 1053 ++++----------------
src/qt/locale/bitcoin_he.ts | 1096 ++++-----------------
src/qt/locale/bitcoin_hi_IN.ts | 1053 ++++----------------
src/qt/locale/bitcoin_hr.ts | 1063 ++++-----------------
src/qt/locale/bitcoin_hu.ts | 1067 ++++-----------------
src/qt/locale/bitcoin_id_ID.ts | 1795 +++++++++++------------------------
src/qt/locale/bitcoin_it.ts | 1468 ++++++++--------------------
src/qt/locale/bitcoin_ja.ts | 1263 ++++++------------------
src/qt/locale/bitcoin_ka.ts | 1122 +++++-----------------
src/qt/locale/bitcoin_kk_KZ.ts | 1053 ++++----------------
src/qt/locale/bitcoin_ko_KR.ts | 1145 +++++-----------------
src/qt/locale/bitcoin_ky.ts | 1100 +++++----------------
src/qt/locale/bitcoin_la.ts | 1059 ++++-----------------
src/qt/locale/bitcoin_lt.ts | 1061 ++++-----------------
src/qt/locale/bitcoin_lv_LV.ts | 1718 ++++++++++-----------------------
src/qt/locale/bitcoin_mn.ts | 3375 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
src/qt/locale/bitcoin_ms_MY.ts | 1053 ++++----------------
src/qt/locale/bitcoin_nb.ts | 1034 +++-----------------
src/qt/locale/bitcoin_nl.ts | 1216 ++++++------------------
src/qt/locale/bitcoin_pam.ts | 1053 ++++----------------
src/qt/locale/bitcoin_pl.ts | 1042 +++-----------------
src/qt/locale/bitcoin_pt_BR.ts | 1143 +++++-----------------
src/qt/locale/bitcoin_pt_PT.ts | 1564 ++++++++----------------------
src/qt/locale/bitcoin_ro_RO.ts | 1032 +++-----------------
src/qt/locale/bitcoin_ru.ts | 1077 ++++-----------------
src/qt/locale/bitcoin_sah.ts | 1096 +++++----------------
src/qt/locale/bitcoin_sk.ts | 1545 +++++++++---------------------
src/qt/locale/bitcoin_sl_SI.ts | 1073 ++++-----------------
src/qt/locale/bitcoin_sq.ts | 1053 ++++----------------
src/qt/locale/bitcoin_sr.ts | 1053 ++++----------------
src/qt/locale/bitcoin_sv.ts | 1489 ++++++++---------------------
src/qt/locale/bitcoin_th_TH.ts | 1053 ++++----------------
src/qt/locale/bitcoin_tr.ts | 1073 ++++-----------------
src/qt/locale/bitcoin_uk.ts | 1061 ++++-----------------
src/qt/locale/bitcoin_ur_PK.ts | 1096 +++++----------------
src/qt/locale/bitcoin_uz@Cyrl.ts | 1096 +++++----------------
src/qt/locale/bitcoin_vi.ts | 1053 ++++----------------
src/qt/locale/bitcoin_vi_VN.ts | 1053 ++++----------------
src/qt/locale/bitcoin_zh_CN.ts | 1073 ++++-----------------
src/qt/locale/bitcoin_zh_HK.ts | 1096 +++++----------------
src/qt/locale/bitcoin_zh_TW.ts | 1180 +++++------------------
src/qt/optionsdialog.cpp | 5 +
src/qt/optionsmodel.cpp | 15 +-
src/qt/optionsmodel.h | 3 +
src/qt/receivecoinsdialog.cpp | 19 +-
src/qt/receivecoinsdialog.h | 8 +-
src/qt/receiverequestdialog.cpp | 25 +-
src/qt/receiverequestdialog.h | 7 +
src/qt/rpcconsole.cpp | 8 +-
src/qt/rpcconsole.h | 2 +-
src/qt/test/test_main.cpp | 1 -
src/qt/transactiontablemodel.cpp | 2 +
src/qt/transactiontablemodel.h | 2 +
src/qt/transactionview.cpp | 35 +
src/qt/transactionview.h | 3 +
src/qt/winshutdownmonitor.cpp | 57 ++
src/qt/winshutdownmonitor.h | 29 +
src/rpcblockchain.cpp | 50 +-
src/rpcclient.cpp | 52 +-
src/rpcmining.cpp | 10 +-
src/rpcmisc.cpp | 17 +-
src/rpcnet.cpp | 69 +-
src/rpcprotocol.cpp | 12 +-
src/rpcprotocol.h | 24 +-
src/rpcrawtransaction.cpp | 23 +-
src/rpcserver.cpp | 192 ++--
src/rpcserver.h | 6 +
src/rpcwallet.cpp | 18 +-
src/script.cpp | 72 +-
src/script.h | 220 ++++-
src/test/DoS_tests.cpp | 5 +-
src/test/Makefile.am | 3 +-
src/test/{README => README.md} | 4 +-
src/test/base58_tests.cpp | 4 +-
src/test/bignum.h | 180 ++++
src/test/bignum_tests.cpp | 224 -----
src/test/canonical_tests.cpp | 17 +
src/test/data/script_invalid.json | 29 +
src/test/data/script_valid.json | 89 ++
src/test/data/tx_invalid.json | 63 +-
src/test/data/tx_valid.json | 68 +-
src/test/netbase_tests.cpp | 37 +
src/test/rpc_tests.cpp | 16 +
src/test/script_tests.cpp | 6 +-
src/test/scriptnum_tests.cpp | 196 ++++
src/test/transaction_tests.cpp | 50 +-
src/test/uint256_tests.cpp | 210 +++-
src/test/util_tests.cpp | 49 +-
src/txdb.cpp | 10 +-
src/txdb.h | 2 -
src/uint256.h | 528 +++++------
src/util.cpp | 99 +-
src/util.h | 39 +-
src/wallet.cpp | 6 +-
src/wallet.h | 2 +
src/walletdb.cpp | 2 +-
202 files changed, 23277 insertions(+), 66633 deletions(-)
create mode 100644 .tx/config
create mode 100755 contrib/devtools/symbol-check.py
create mode 100755 contrib/devtools/update-translations.py
create mode 100644 contrib/gitian-descriptors/gitian-osx-bitcoin.yml
create mode 100644 contrib/gitian-descriptors/gitian-osx-depends.yml
create mode 100644 contrib/gitian-descriptors/gitian-osx-native.yml
create mode 100644 contrib/gitian-descriptors/gitian-osx-qt.yml
create mode 100644 contrib/gitian-descriptors/qt-linux.yml
create mode 100644 doc/README_osx.txt
create mode 100644 qa/rpc-tests/netutil.py
create mode 100755 qa/rpc-tests/rpcbind_test.py
delete mode 100644 src/bignum.h
create mode 100644 src/qt/locale/bitcoin_mn.ts
create mode 100644 src/qt/winshutdownmonitor.cpp
create mode 100644 src/qt/winshutdownmonitor.h
rename src/test/{README => README.md} (87%)
create mode 100644 src/test/bignum.h
delete mode 100644 src/test/bignum_tests.cpp
create mode 100644 src/test/scriptnum_tests.cpp
# push my local bitcoin branch to my branch repository at GitHub
$ git push origin master
Counting objects: 1460, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (361/361), done.
Writing objects: 100% (1065/1065), 2.03 MiB | 112.00 KiB/s, done.
Total 1065 (delta 880), reused 887 (delta 702)
To git@github.com:StephenLReed/bitcoin.git
4765b8c..97b53b5 master -> master
To make a change to the bitcoin repository . . . How to create a PULL request$ git checkout -b niftynewfeature # Create a feature branch
... edit, test, re-edit, re-test...
$ git commit -a
$ git push git@github.com:StephenLReed/bitcoin.git niftynewfeature:niftynewfeature
Gavin: Submit a PULL request by going to your fork's GitHub page, selecting the branch containing the changes you want pulled ("niftynewfeature" in the above example), and then poking the "Pull Request" button. Enter a good description of what your changes do and why they're a good idea and how everybody and their brother is already using them to make the world a better place . |
|
|
|
As time goes by, more and more altcoins are eroding away bitcoin shares in the total crypto currency realm. DRK is getting interesting at this moment.
Is it reasonable to have a altcoin factor put into the price forecast algorithm?
I have a project that greatly improves Bitcoin as magnet for development, infrastructure, paid order flow, and marketing. These advantages will scale linearly with market cap and thus marginalize altchains - even as they pioneer or subsequently adopt similar improvements. If the alternative technology extends Bitcoin or otherwise runs on the Bitcoin platform, then that will survive and prosper. Sidechains for Bitcoin, under somewhat stealthy development today, could provide the platform for branded coins and niche/innovative features. In the wake of the rally now under way, I suppose that like in the November 2013 bubble, altcoins will be late to the party and fade as the bubble subsequently collapses. Assuming that altcoins as a sector are more volatile than bitcoin one could stay long in bitcoin for the moment. When the weekly price growth rate of the altcoin leaders meets or surpasses the bitcoin price growth, then switch to the altcoins you prefer, and sell at the peak, switching back long into bitcoin during the collapse. |
|
|
|
Conventional charting wisdom says that a strong resistance trendline, once broken through, becomes a source of support. In the below 3-day resolution chart that illustrates the trendline from the November 2013 peak, I suppose that this line now marks territory that bitcoin prices may never visit again, e.g. sub $400.
But the trendline that functions as support now is forever going down. It won't be long before it crosses zero. Does this not refer to the point where the trendline was broken? Roughly $440. Otherwise, we're still talking about a bear market, and this is certainly the signal of the bull. Agreed. My observation is probably good only for a short period or if there is some news-induced sell off later on. Because there was a pause at $800 for the month of January, I sort of expect prices to linger there for a while before soaring beyond the previous all time high. |
|
|
|
Conventional charting wisdom says that a strong resistance trendline, once broken through, becomes a source of support. In the below 3-day resolution chart that illustrates the trendline from the November 2013 peak, I suppose that this line now marks territory that bitcoin prices may never visit again, e.g. sub $400.  |
|
|
|
It was just example . One smart guy with shitload of money who would buy 2000Btc per day and in few years .....
What would compell such an individual to take risk while already possessing more wealth than he's going to need in the rest of his life? Using the winklevii as an example. They won $65 million from Mark Zuckerberg. They invested some millions in bitcoin for the adventure. They think big. There are others . . . |
|
|
|
|
Show Posts
