bitcoinplusmagic
|
|
September 29, 2017, 05:08:41 AM |
|
Bitcoin is facing the wall with its saturated mempool and high transaction fees. There is even the threat of a hardfork happening this year. There is division in the community about the solutions to be implemented, whether it is Segwit, Lightning network, Bitcoin Unlimited or simply doing nothing.
While many are pondering about which form will take the new Bitcoin, the solution already exists and is there. The new, better Bitcoin is called Bitcoin Plus. Many are now realizing this including me, that's why moving from BTC into XBC is a logical step, at least for me.
I do not think Bitcoinplus is a realistic alternative for bitcoin because the user base is not global and it is not distributed evenly enough.Also it is not like bitcoin really because it is not forked directly from bitcoin code.Too many bagholders with big coin amounts dumping constantly will not allow price to remain high and in the end it will remain here or go back to only a few cents value but only time will tell as only 10% of total coins are mined so far.Developers can only do so much but if bagholders and community do nothing I can not see anything big in the future as there are many coins to choose from. BitcoinPlus Market Cap remains around $6,500,000 which is superb. It has natural ups and downs. It has minimal coin supply so yes it can be easily manipulated by a relatively small amount of capital. See the last couple of pumps beginning and end of July for instance. Every coin goes through these cycles. There is nothing that XBC Team can do to stop that. Outside of these pumps I don't see bagholders dumping. Liquidity isn't great on the XBC Market on Poloniex which makes the price extremely volatile and over reacts to even a few XBC being traded. Other than the top coins, all markets on Poloniex have less BTC then a year ago due to the decline in Poloniex Trust from Market Makers. Every person I know, has drastically reduced their exposure to Poloniex and moved to other exchanges. Total Poloniex Volume is massively down compared to a year ago. However, overtime as Poloniex reputation improves again, market makers should come back to Poloniex and liquidity on the smaller coins (such as XBC) should increase. Manipulating prices or fake volume is absolutely something XBC Project will NOT entertain and be a part of. You are absolutely right in that the XBC user base is small compared to the larger coins and prior to the Current Development this was the Number 1 priority for the XBC Project. However, as the priority is now updating the XBC Code base so that it is on a par with BTC so that we can actually piggyback developing technology and even develop our own, all funds are diverted into that. In the background you can see our Freelance Dev updating the entire BitcoinPlus code base so that we will be based on Bitcoin but Proof of Stake. The intention at the moment is to also keep the TOR feature and our encrypted messaging feature. These are big differences. Once the updates are complete the XBC Project will start the Marketing side of BitcoinPlus again. It is not simple process. We are trying to avoid any hard forks and we are trying to make everything as seamless as possible. It may take many months to get to where we want to be but we WILL get there. XBC has made good progress but only the rich get richer and those who have the most money to buy coins and accumulate large bags can do no work and get the most returned due to proof of stake concept.Of course large mining farms can do this with bitcoin but bitcoin is better distributed.Bitcoinplus can only hope to fill some niche use case such as some type of settlement layer with easy privacy and security,efficiency improvements but why bother when we can already use bitcoin segwit for this?There are many better options than XBC where one or two large bagholders do not dominate the staking process and price is stable exchange rate. As with ALL coins there are bagholders. That is the risk you take with all coins. As only 10% of all coins are currently minted there is plenty of scope for people to accumulate their own bags.
|
|
|
|
bitcoinplusmagic
|
|
September 29, 2017, 05:15:08 AM |
|
Is Bittrex not a better option than Poloniex for the main exchange for XBC liquidity?
I agree. Bittrex would be a great secondary exchange for XBC. However. As has previously been discussed numerous times on here, Bittrex require very large fees just to review the coins code with no agreement in place at the end of the review that XBC would be listed. Bittrex also require funds allocated to act as market makers. Priority for XBC is wallet development. Everything is reviewed every few months, so who knows in the future.
|
|
|
|
BitcoinPlusBus (OP)
Legendary
Offline
Activity: 1484
Merit: 1032
|
|
September 29, 2017, 06:12:58 AM |
|
Is Bittrex not a better option than Poloniex for the main exchange for XBC liquidity?
Poloniex is the leading crypto currency exchange in the business.
|
|
|
|
BitcoinPlusBus (OP)
Legendary
Offline
Activity: 1484
Merit: 1032
|
|
September 29, 2017, 06:13:23 AM |
|
2017-09-29 06:03 UTC
Difficulty POW: 0.01442156 POS: 0.00024414 Coin Supply (XBC) 101056.98879024 419279 blocks 30 connections
Last Price 0.01634298 24hr Change +4.75% 24hr High 0.01750000 24hr Low 0.01540000 24hr Volume: 26.63015181 BTC / 1643.50911322 XBC
|
|
|
|
raimch89
Legendary
Offline
Activity: 1169
Merit: 1000
|
|
September 29, 2017, 06:48:32 AM |
|
rushmybitcoin quit the team? don't seen him here since a long time sorry about this because was doing a good job for the promo of xbc
|
|
|
|
egghead123
Legendary
Offline
Activity: 1330
Merit: 1000
|
|
September 29, 2017, 10:25:44 AM Last edit: September 29, 2017, 10:44:24 AM by egghead123 |
|
rushmybitcoin quit the team? don't seen him here since a long time sorry about this because was doing a good job for the promo of xbc
XBC can neither be hyped nor "promoted" as an investment.Also making market predictions etc etc aren't doable.XBC like ANY altcoin can go up or down in price and the 20% stake is only an incentive to mine the coin into existence just like any PoW miner with the most hashing power can do the same thing.
|
|
|
|
egghead123
Legendary
Offline
Activity: 1330
Merit: 1000
|
|
September 29, 2017, 10:30:27 AM |
|
New features in 0.8 and 0.9 Bitcoin codebaseBitcoin 0.8“Bloom filter” support in the network protocol for sending only relevant transactions to lightweight clients. contrib/verifysfbinaries is a shell-script to verify that the binary downloads at sourceforge have not been tampered with. If you are able, you can help make everybody’s downloads more secure by running this occasionally to check PGP signatures against download file checksums. contrib/spendfrom is a python-language command-line utility that demonstrates how to use the “raw transactions” JSON-RPC api to send coins received from particular addresses (also known as “coin control”). New/changed settings (command-line or bitcoin.conf file) dbcache : controls LevelDB memory usage. par : controls how many threads to use to validate transactions. Defaults to the number of CPUs on your machine, use -par=1 to limit to a single CPU. txindex : maintains an extra index of old, spent transaction ids so they will be found by the getrawtransaction JSON-RPC method. reindex : rebuild block and transaction indices from the downloaded block data. New JSON-RPC API Featuresl ockunspent / listlockunspent allow locking transaction outputs for a period of time so they will not be spent by other processes that might be accessing the same wallet. addnode / getaddednodeinfo methods, to connect to specific peers without restarting. importprivkey now takes an optional boolean parameter (default true) to control whether or not to rescan the blockchain for transactions after importing a new private key. Default block size increase for miners. (see https://gist.github.com/gavinandresen/7670433#086-accept-into-block) Remove the all-outputs-must-be-greater-than-CENT-to-qualify-as-free rule for relaying (see https://gist.github.com/gavinandresen/7670433#086-relaying) Lower maximum size for free transaction creation (see https://gist.github.com/gavinandresen/7670433#086-wallet) -OSX block chain database corruption fixes -Update leveldb to 1.13 -Use fcntl with F_FULLSYNC instead of fsync on OSX -Use native Darwin memory barriers -Replace use of mmap in leveldb for improved reliability (only on OSX) -Fix nodes forwarding transactions with empty vins and getting banned -Network code performance and robustness improvements -Additional debug.log logging for diagnosis of network problems, log timestamps by default -Fix Bitcoin-Qt startup crash when clicking dock icon on OSX -Fix memory leaks in CKey::SetCompactSignature() and Key::SignCompact() -Fix rare GUI crash on send -Various small GUI, documentation and build fixes
|
|
|
|
egghead123
Legendary
Offline
Activity: 1330
Merit: 1000
|
|
September 29, 2017, 10:32:45 AM |
|
Bitcoin 0.9.0
Autotools build system For 0.9.0 we switched to an autotools-based build system instead of individual (q)makefiles. Using the standard “./autogen.sh; ./configure; make” to build Bitcoin-Qt and bitcoind makes it easier for experienced open source developers to contribute to the project.
Be sure to check doc/build-*.md for your platform before building from source. Bitcoin-cli Another change in the 0.9 release is moving away from the bitcoind executable functioning both as a server and as a RPC client. The RPC client functionality (“tell the running bitcoin daemon to do THIS”) was split into a separate executable, ‘bitcoin-cli’. The RPC client code will eventually be removed from bitcoind, but will be kept for backwards compatibility for a release or two. walletpassphrase RPC The behavior of the walletpassphrase RPC when the wallet is already unlocked has changed between 0.8 and 0.9. The 0.8 behavior of walletpassphrase is to fail when the wallet is already unlocked: > walletpassphrase 1000 walletunlocktime = now + 1000 > walletpassphrase 10 Error: Wallet is already unlocked (old unlock time stays)
The new behavior of walletpassphrase is to set a new unlock time overriding the old one: > walletpassphrase 1000 walletunlocktime = now + 1000 > walletpassphrase 10 walletunlocktime = now + 10 (overriding the old unlock time)
Transaction malleability-related fixes
This release contains a few fixes for transaction ID (TXID) malleability issues: -nospendzeroconfchange command-line option, to avoid spending zero-confirmation change IsStandard() transaction rules tightened to prevent relaying and mining of mutated transactions Additional information in listtransactions/gettransaction output to report wallet transactions that conflict with each other because they spend the same outputs. Bug fixes to the getbalance/listaccounts RPC commands, which would report incorrect balances for double-spent (or mutated) transactions. New option: -zapwallettxes to rebuild the wallet’s transaction information
Transaction Fees This release drops the default fee required to relay transactions across the network and for miners to consider the transaction in their blocks to 0.01mBTC per kilobyte. Note that getting a transaction relayed across the network does NOT guarantee that the transaction will be accepted by a miner; by default, miners fill their blocks with 50 kilobytes of high-priority transactions, and then with 700 kilobytes of the highest-fee-per-kilobyte transactions. The minimum relay/mining fee-per-kilobyte may be changed with the minrelaytxfee option. Note that previous releases incorrectly used the mintxfee setting to determine which low-priority transactions should be considered for inclusion in blocks. The wallet code still uses a default fee for low-priority transactions of 0.1mBTC per kilobyte. During periods of heavy transaction volume, even this fee may not be enough to get transactions confirmed quickly; the mintxfee option may be used to override the default.
Note:All figures re fees to be converted to relevant XBC ratios etc.
|
|
|
|
egghead123
Legendary
Offline
Activity: 1330
Merit: 1000
|
|
September 29, 2017, 10:35:52 AM |
|
RPC: New notion of ‘conflicted’ transactions, reported as confirmations: -1 listreceivedbyaddress now provides tx ids Add raw transaction hex to gettransaction output Updated help and tests for getreceivedby(account|address) In getblock, accept 2nd verbose parameter, similar to getrawtransaction, but defaulting to 1 for backward compatibility Add verifychain, to verify chain database at runtime Add dumpwallet and importwallet RPCs keypoolrefill gains optional size parameter Add getbestblockhash, to return tip of best chain Add chainwork (the total work done by all blocks since the genesis block) to getblock output Make RPC password resistant to timing attacks Clarify help messages and add examples Add getrawchangeaddress call for raw transaction change destinations Reject insanely high fees by default in sendrawtransaction Add RPC call decodescript to decode a hex-encoded transaction script Make validateaddress provide redeemScript Add getnetworkhashps to get the calculated network hashrate New RPC ping command to request ping, new pingtime and pingwait fields in getpeerinfo output Adding new addrlocal field to getpeerinfo output Add verbose boolean to getrawmempool Add rpc command getunconfirmedbalance to obtain total unconfirmed balance Explicitly ensure that wallet is unlocked in importprivkey Add check for valid keys in importprivkey Command-line options: New option: -nospendzeroconfchange to never spend unconfirmed change outputs New option: -zapwallettxes to rebuild the wallet’s transaction information Rename option -tor to -onion to better reflect what it does Add -disablewallet mode to let bitcoind run entirely without wallet (when built with wallet) Update default -rpcsslciphers to include TLSv1.2 make -logtimestamps default on and rework help-message RPC client option: -rpcwait, to wait for server start Remove -logtodebugger Allow -noserver with bitcoind Block-chain handling and storage: Update leveldb to 1.15 Check for correct genesis (prevent cases where a datadir from the wrong network is accidentally loaded) Allow txindex to be removed and add a reindex dialog Log aborted block database rebuilds Store orphan blocks in serialized form, to save memory Limit the number of orphan blocks in memory to 750 Fix non-standard disconnected transactions causing mempool orphans Add a new checkpoint at block 279,000 Wallet: Bug fixes and new regression tests to correctly compute the balance of wallets containing double-spent (or mutated) transactions Store key creation time. Calculate whole-wallet birthday. Optimize rescan to skip blocks prior to birthday Let user select wallet file with -wallet=foo.dat Consider generated coins mature at 101 instead of 120 blocks Improve wallet load time Don’t count txins for priority to encourage sweeping Don’t create empty transactions when reading a corrupted wallet Fix rescan to start from beginning after importprivkey Only create signatures with low S values Mining: Increase default -blockmaxsize/prioritysize to 750K/50K getblocktemplate does not require a key to create a block template Mining code fee policy now matches relay fee policy Protocol and network: Drop the fee required to relay a transaction to 0.01mBTC per kilobyte Send tx relay flag with version New reject P2P message (BIP 0061, seehttps://gist.github.com/gavinandresen/7079034 for draft) Dump addresses every 15 minutes instead of 10 seconds Relay OP_RETURN data TxOut as standard transaction type Remove CENT-output free transaction rule when relaying Lower maximum size for free transaction creation Send multiple inv messages if mempool.size > MAX_INV_SZ Split MIN_PROTO_VERSION into INIT_PROTO_VERSION and MIN_PEER_PROTO_VERSION Do not treat fFromMe transaction differently when broadcasting Process received messages one at a time without sleeping between messages Improve logging of failed connections Bump protocol version to 70002 Add some additional logging to give extra network insight Added new DNS seed from bitcoinstats.com Validation: Log reason for non-standard transaction rejection Prune provably-unspendable outputs, and adapt consistency check for it. Detect any sufficiently long fork and add a warning Call the -alertnotify script when we see a long or invalid fork Fix multi-block reorg transaction resurrection Reject non-canonically-encoded serialization sizes Reject dust amounts during validation Accept nLockTime transactions that finalize in the next block Build system: Switch to autotools-based build system Build without wallet by passing --disable-wallet to configure, this removes the BerkeleyDB dependency Upgrade gitian dependencies (libpng, libz, libupnpc, boost, openssl) to more recent versions Windows 64-bit build support Solaris compatibility fixes Check integrity of gitian input source tarballs Enable full GCC Stack-smashing protection for all OSes GUI: Switch to Qt 5.2.0 for Windows build Add payment request (BIP 0070) support Improve options dialog Show transaction fee in new send confirmation dialog Add total balance in overview page Allow user to choose data directory on first start, when data directory is missing, or when the -choosedatadir option is passed Save and restore window positions Add vout index to transaction id in transactions details dialog Add network traffic graph in debug window Add open URI dialog Add Coin Control Features Improve receive coins workflow: make the ‘Receive’ tab into a form to request payments, and move historical address list functionality to File menu. Rebrand to Bitcoin Core Move initialization/shutdown to a thread. This prevents “Not responding” messages during startup. Also show a window during shutdown. Don’t regenerate autostart link on every client startup Show and store message of normal bitcoin:URI Fix richtext detection hang issue on very old Qt versions OS X: Make use of the 10.8+ user notification center to display Growl-like notifications OS X: Added NSHighResolutionCapable flag to Info.plist for better font rendering on Retina displays. OS X: Fix bitcoin-qt startup crash when clicking dock icon Linux: Fix Gnome bitcoin: URI handler Miscellaneous: Add Linux script (contrib/qos/tc.sh) to limit outgoing bandwidth Add -regtest mode, similar to testnet but private with instant block generation with setgenerate RPC. Add linearize.py script to contrib, for creating bootstrap.dat Add separate bitcoin-cli client
RPC: Add getwalletinfo, getblockchaininfo and getnetworkinfo calls (will replace hodge-podge getinfo at some point) Add a relayfee field to getnetworkinfo Fix RPC related shutdown hangs and leaks Always show syncnode in getpeerinfo sendrawtransaction: report the reject code and reason, and make it possible to re-send transactions that are already in the mempool getmininginfo show right genproclimit Command-line options: Fix -printblocktree output Show error message if ReadConfigFile fails Block-chain handling and storage: Fix for GetBlockValue() after block 13,440,000 (BIP42) Upgrade leveldb to 1.17 Protocol and network code: Per-peer block download tracking and stalled download detection Add new DNS seed from bitnodes.io Prevent socket leak in ThreadSocketHandler and correct some proxy related socket leaks Use pnode->nLastRecv as sync score (was the wrong way around) Wallet: Make GetAvailableCredit run GetHash() only once per transaction (performance improvement) Lower paytxfee warning threshold from 0.25 BTC to 0.01 BTC Fix importwallet nTimeFirstKey (trigger necessary rescans) Log BerkeleyDB version at startup CWallet init fix Build system: Add OSX build descriptors to gitian Fix explicit –disable-qt-dbus Don’t require db_cxx.h when compiling with wallet disabled and GUI enabled Improve missing boost error reporting Upgrade miniupnpc version to 1.9 gitian-linux: –enable-glibc-back-compat for binary compatibility with old distributions gitian: don’t export any symbols from executable gitian: build against Qt 4.6 devtools: add script to check symbols from Linux gitian executables Remove build-time no-IPv6 setting GUI: Fix various coin control visual issues Show number of in/out connections in debug console Show weeks as well as years behind for long timespans behind Enable and disable the Show and Remove buttons for requested payments history based on whether any entry is selected. Show also value for options overridden on command line in options dialog Fill in label from address book also for URIs Fixes feel when resizing the last column on tables (issue #2862) Fix ESC in disablewallet mode Add expert section to wallet tab in optionsdialog Do proper boost::path conversion (fixes unicode in datadir) Only override -datadir if different from the default (fixes -datadir in config file) Show rescan progress at start-up Show importwallet progress Get required locks upfront in polling functions (avoids hanging on locks) Catch Windows shutdown events while client is running Optionally add third party links to transaction context menu Check for !pixmap() before trying to export QR code (avoids crashes when no QR code could be generated) Fix “Start bitcoin on system login” Miscellaneous: Replace non-threadsafe C functions (gmtime, strerror and setlocale) Add missing cs_main and wallet locks Avoid exception at startup when system locale not recognized Changed bitrpc.py’s raw_input to getpass for passwords to conceal characters during command line input devtools: add a script to fetch and postprocess translations
|
|
|
|
egghead123
Legendary
Offline
Activity: 1330
Merit: 1000
|
|
September 29, 2017, 10:37:22 AM |
|
Bitcoin 0.9.2
RPC: Add getwalletinfo, getblockchaininfo and getnetworkinfo calls (will replace hodge-podge getinfo at some point) Add a relayfee field to getnetworkinfo Fix RPC related shutdown hangs and leaks Always show syncnode in getpeerinfo sendrawtransaction: report the reject code and reason, and make it possible to re-send transactions that are already in the mempool getmininginfo show right genproclimit Command-line options: Fix -printblocktree output Show error message if ReadConfigFile fails Block-chain handling and storage: Fix for GetBlockValue() after block 13,440,000 (BIP42) Upgrade leveldb to 1.17 Protocol and network code: Per-peer block download tracking and stalled download detection Add new DNS seed from bitnodes.io Prevent socket leak in ThreadSocketHandler and correct some proxy related socket leaks Use pnode->nLastRecv as sync score (was the wrong way around) Wallet: Make GetAvailableCredit run GetHash() only once per transaction (performance improvement) Lower paytxfee warning threshold from 0.25 BTC to 0.01 BTC Fix importwallet nTimeFirstKey (trigger necessary rescans) Log BerkeleyDB version at startup CWallet init fix Build system: Add OSX build descriptors to gitian Fix explicit –disable-qt-dbus Don’t require db_cxx.h when compiling with wallet disabled and GUI enabled Improve missing boost error reporting Upgrade miniupnpc version to 1.9 gitian-linux: –enable-glibc-back-compat for binary compatibility with old distributions gitian: don’t export any symbols from executable gitian: build against Qt 4.6 devtools: add script to check symbols from Linux gitian executables Remove build-time no-IPv6 setting GUI: Fix various coin control visual issues Show number of in/out connections in debug console Show weeks as well as years behind for long timespans behind Enable and disable the Show and Remove buttons for requested payments history based on whether any entry is selected. Show also value for options overridden on command line in options dialog Fill in label from address book also for URIs Fixes feel when resizing the last column on tables (issue #2862) Fix ESC in disablewallet mode Add expert section to wallet tab in optionsdialog Do proper boost::path conversion (fixes unicode in datadir) Only override -datadir if different from the default (fixes -datadir in config file) Show rescan progress at start-up Show importwallet progress Get required locks upfront in polling functions (avoids hanging on locks) Catch Windows shutdown events while client is running Optionally add third party links to transaction context menu Check for !pixmap() before trying to export QR code (avoids crashes when no QR code could be generated) Fix “Start bitcoin on system login” Miscellaneous: Replace non-threadsafe C functions (gmtime, strerror and setlocale) Add missing cs_main and wallet locks Avoid exception at startup when system locale not recognized Changed bitrpc.py’s raw_input to getpass for passwords to conceal characters during command line input devtools: add a script to fetch and postprocess translations
|
|
|
|
egghead123
Legendary
Offline
Activity: 1330
Merit: 1000
|
|
September 29, 2017, 10:38:29 AM |
|
Bitcoin 0.9.3RPC: Avoid a segfault on getblock if it can’t read a block from disk Add paranoid return value checks in base58 Protocol and network code: Don’t poll showmyip.com, it doesn’t exist anymore Add a way to limit deserialized string lengths and use it Add a new checkpoint at block 295,000 Increase IsStandard() scriptSig length Avoid querying DNS seeds, if we have open connections Remove a useless millisleep in socket handler Stricter memory limits on CNode Better orphan transaction handling Add -maxorphantx=<n> and -maxorphanblocks=<n> options for control over the maximum orphan transactions and blocks Wallet: Check redeemScript size does not exceed 520 byte limit Ignore (and warn about) too-long redeemScripts while loading wallet GUI: fix ‘opens in testnet mode when presented with a BIP-72 link with no fallback’ AvailableCoins: acquire cs_main mutex Fix unicode character display on MacOSX Miscellaneous: key.cpp: fail with a friendlier message on missing ssl EC support Remove bignum dependency for scripts Upgrade OpenSSL to 1.0.1i (see https://www.openssl.org/news/secadv_20140806.txt - just to be sure, no critical issues for Bitcoin Core) Upgrade miniupnpc to 1.9.20140701 Fix boost detection in build system on some platforms
|
|
|
|
egghead123
Legendary
Offline
Activity: 1330
Merit: 1000
|
|
September 29, 2017, 10:43:48 AM |
|
All the above changes to get us to 0.9.3 are also listed here: https://docs.google.com/document/d/1TYxjS3S33lFTM87OYoMEWymwzH3e33h4encJ6cor1uk/edit?usp=sharing XBC is not an easy coin to wok on due to some of the extra features we have and keeping them.It would be easier if we were a vanilla codebase but the reality is the opposite.Also gutting out the codebase from the beginning back to a starting point and keeping the native tor wallet and the messaging was no easy task not to mention the fact this is all being done without a hard fork (soft forks only) to cause the least disruption to exchanges/service providers and users.There is still a lot of work ahead (BIPs/newer version changes etc) before we are even ready to activate segregated witness.
|
|
|
|
jhannlenris
|
|
September 29, 2017, 10:48:47 AM |
|
Bitcoin Plus is doing perfectly fine. XBC has been performing very well in the past few months, with a 10X increase in value, more than Bitcoin itself. It's hard to ask for more with such an achievement in a very short amount of time. While it would be nice to see it listed on new exchanges in the near future, that is not a necessity. I agree it would be foolish to pay large amounts for new listings. Money is better invested in technology development. When the fundamentals get better and stronger (as it is the case right now with XBC development), it naturally attracts investors. XBC doesn't need Bittrex. Let's change that state of mind. If anything, it is Bittrex (or any other exchange) that does need XBC.
Coinexchange and Cryptopia are good markets for XBC, even if volume is low at this time, it will slowly increase with time, as more and more new users get into the cryptosphere.
|
|
|
|
BitcoinPlusBus (OP)
Legendary
Offline
Activity: 1484
Merit: 1032
|
|
September 30, 2017, 10:25:03 AM |
|
Sat, 30 Sep 2017 10:20:36 GMT
Current Block 420122 Difficulty 0.00024414 Coin Supply 101090.9976 34 connections
XBC/BTC Last Price 0.01589937 24hr Change -0.17% 24hr High 0.01621489 24hr Low 0.01553007 24hr Volume: 6.13461354 BTC / 385.43163287 XBC
|
|
|
|
BitcoinPlusBus (OP)
Legendary
Offline
Activity: 1484
Merit: 1032
|
|
October 01, 2017, 11:08:51 AM |
|
2017-10-01 10:52 UTC
Difficulty POS: 0.00024414 Coin Supply (XBC) 101115.45179622 420814 blocks 31 connections
XBC/BTC Last Price 0.01620073 24hr Change +1.89% 24hr High 0.01797000 24hr Low 0.01570000 24hr Volume: 24.36480744 BTC / 1461.93744548 XBC
|
|
|
|
BitcoinPlusBus (OP)
Legendary
Offline
Activity: 1484
Merit: 1032
|
|
October 02, 2017, 10:09:23 AM |
|
2017-10-02 09:47 UTC
POS Difficulty: 0.00026492 Coin Supply (XBC): 101150 421532 blocks 38 connections
XBC/BTC Last Price 0.01550730 24hr Change -4.28% 24hr High 0.01620073 24hr Low 0.01508049 24hr Volume: 6.99032781 BTC / 444.26116110 XBC
|
|
|
|
BitcoinPlusBus (OP)
Legendary
Offline
Activity: 1484
Merit: 1032
|
|
October 02, 2017, 11:38:46 AM |
|
We have been working on the Ultraprune, it is going to be required going forward. Again the challenge is that the changes brought in by Ultraprune are partially implemented, it is when Bitcoin moved to LevelDB. Novacoin added LevelDB but not UltraPrune or many of the other changes introduced during the major refactor to storage of everything except the wallet.
Peter is running a version of Bitcoin Plus that does not have LevelDB at all. The LevelDB implementation was at odds to Bitcoin's so he has rolled it back to Berkley DB and will add LevelDB in a Bitcoin standard fashion.
|
|
|
|
BitcoinPlusBus (OP)
Legendary
Offline
Activity: 1484
Merit: 1032
|
|
October 02, 2017, 11:46:02 AM |
|
Anyone currently trying to compile the code on ubuntu with latest openssl version might get the following error: tor/aes.c:93:18: error: field 'evp' has incomplete type EVP_CIPHER_CTX evp; ^ makefile.unix:285: recipe for target 'obj/aes.o' failed make: *** [obj/aes.o] Error 1 We are implementing autotools and Peter is doing the ultraprune.This leads to the split of daemon from GUI.
|
|
|
|
BitcoinPlusBus (OP)
Legendary
Offline
Activity: 1484
Merit: 1032
|
|
October 03, 2017, 09:50:29 AM |
|
Tue, 03 Oct 2017 09:42:34 GMT
Difficulty POS: 0.00030276 Coin Supply (XBC) 101173.69398079 422273 blocks 33 connections
XBC/BTC Last Price 0.01455030 24hr Change -6.17% 24hr High 0.01584508 24hr Low 0.01455030 24hr Volume: 3.79915428 BTC / 253.52252843 XBC
|
|
|
|
pumpxbc
Newbie
Offline
Activity: 11
Merit: 0
|
|
October 03, 2017, 07:46:39 PM |
|
All the above changes to get us to 0.9.3 are also listed here: https://docs.google.com/document/d/1TYxjS3S33lFTM87OYoMEWymwzH3e33h4encJ6cor1uk/edit?usp=sharing XBC is not an easy coin to wok on due to some of the extra features we have and keeping them.It would be easier if we were a vanilla codebase but the reality is the opposite.Also gutting out the codebase from the beginning back to a starting point and keeping the native tor wallet and the messaging was no easy task not to mention the fact this is all being done without a hard fork (soft forks only) to cause the least disruption to exchanges/service providers and users.There is still a lot of work ahead (BIPs/newer version changes etc) before we are even ready to activate segregated witness. So we will still have the tor and messaging service after finished upgrade?Why do we need the segwit and maybe only have bigger blocksize?
|
|
|
|
|