Reasons for investing in CanYa after price drops 90%
Why I Invested in CanYa Cryptocurrencies are grabbing the news headlines, and their performance has exceeded many a speculative investor’s wildest dreams. Blockchains remove the shady side of digital currencies by making all transactions fully traceable, but despite addressing the concerns raised by those who are uncomfortable with the possible ethical implications of supporting cryptocurrencies, few of them are particularly stable. CanYa seems to be bucking the system by offering a genuinely promising investment opportunity that could yield excellent returns. How safe is CanYa? Its recent selection by China’s online retail giant, JD.com is evidence of the trust that CanYa engenders, and it’s the cryptocurrency-specific accounting setup that’s one of the biggest contributors to this vote of confidence. The company admits that, following its launch, it found itself in an “accounting and compliance hole,” but its subsequent actions have dug it well and truly out of that hole. JD president Yongli Yu says that whole-process traceability is important, and that CanYa’s blockchain meets it and its clients’ requirement for transparency. And in case you’ve never heard of JD.com, we’re talking about a China-based retail platform with revenue of nearly $50 billion and over 266 million active users. Why Consumers and Investors are Turning to CanYa There is no shortage of reasons to get involved with CanYa. The blockchain-powered marketplace allows for cryptocurrency-based business transactions covering freelance services. The platform allows users to choose between currencies like Bitcoin and Ethereum and its own token, the CAN. And if users still prefer to transact using Australian Dollars, there’s room for that option too. CAN might sound like just another crypto, but CanYa says that its coin can’t be created out of thin air. The number of coins in circulation will decrease over time as a result, and that will boost the value of the currency still further. The company purchased a stake in crowdfunding and bounty service Bountysource, an established platform that first began to do business back in the 2000s and CAN coins can be used as an actual currency that nevertheless manages to duck the currency exchange fees that would ordinarily apply to international transactions. With stability and value assured, consumers and investors around the world are turning to CanYa as a viable and trustworthy alternative to traditional transaction platforms and currencies. It’s a Real Business The cryptocurrency boom has given rise to a lot of hype, and there are almost certain to be casualties, but CanYa is a real business with concrete assets at its disposal. Investor trust is evidenced by the $12 million in investment already raised, while the company itself is probably significantly undervalued at a worth of $15 million when its successful projects to date are taken into account. CanYa is achieving worldwide recognition, and JD.com’s recent endorsement of the blockchain is CanYa’s latest triumph. I’m confident that it won’t be the company’s last. With JD’s business development acumen, marketing power, and existing network to boost the business, CanYa seems destined to grow from strength to strength. Will CanYa disrupt the services platforms industry by providing a peer to peer platform that doesn’t charge ridiculously high commissions to freelance service providers and their clients? It’s already doing so, and with cryptocurrencies becoming a mainstream means of payment, CanYa’s own digital currency is sure to thrive. You may be asking how low can it go? Valid point, while you may be concerned about how much further the price of CanYa can go, you have to go back to market fundamentals before making the decision of buy or sell. Sure, the crypto market is falling at the time of writing this blog (BTC: $8,900 ETH: 691 XRP: 0.80). You need to remember the blockchain markets are just like any other financial market, plus some. In February 2018, the Dow Jones [DJIA] dropped close to 10% in only a week of trading and every investor started hitting the panic button; however what followed was nearly a full recovery which is still in progress. The point being when you are investing in an asset, you have to look at two things, the market conditions and the fundamental value of the asset. For CAN, it can be argued at this level they are nearly cash backed, which leaves very little room for potential price failure. Taking the current market cap of $15m (USD), the cash they hold from the cap raise, the $2m CAN buy-back, the joint venture potential with JD.com, the Bountysource.com investment, and the upcoming launch of the CanYa platform, there’s lots to look forward to! Another important factor when looking at price action on any financial market is the volume. In the instance of CAN, the volume is averaging 0.6% of the market cap which is relatively low compared to its peers. Price drops on low volume generally don’t sound the panic buttons for investors. That’s all for now, we will keep you updated with our views for CAN as things develop further over the next few months with some exciting developments coming.
Sustainable Emacs development - some thoughts and analysis
Influenced by some recent posts, I have decided to outline some ideas I've written about monetarily sustaining Emacs development. Emacs is amazing software. Although not without its shortcomings, there are many things that Emacs gets right. One of the best things(if not the best) about Emacs is the community. With the latest developments in text editing being "Let's put the editor in the browser!" and "Let's rewrite stuff", let's take a look at packages that came about in the Emacs world:
Magit. It is truly git porcelain. It makes me enjoy git.
Projectile: Abstraction on top of your file system for a kickass project management? Yes please.
Interactive searches on top of any structure inside Emacs? There are too many awesome packages to name.
Awesome pre-build configs? Pick your flavor.
And there are many old and new ones including org, fireplace.el, lispy, cider, and so forth. Writing and maintaining these packages is no simple task. Not only does it require creativity and ingenuity to come up with better ways of pressing on keys, it also requires understanding Emacs and its API(not easy) and being a good Emacs Lisp programmer(not easy). Not to mention the core maintainers and developers. While I might not agree with certain opinions, I admire the amount of work and soul they put into this project. So how do we, as a community, support it? Monetarily, not well. It's hard to find stats on how much money is donated through FSF(more on that later), let's examine publically available information on how much money is donated to emacs projects: Magit - 244 dollars a month.[https://www.patreon.com/tarsius] Projectile - 17$ a month on bontysource, 8$ a month of gratipay [https://www.bountysource.com/teams/projectile/members] [https://gratipay.com/Projectile/] Helm - [https://www.patreon.com/emacshelm] 6% a month on patreon. and so forth. I find it shameful, and I wish for it to change. Before I move forward with the post, I'd like to play some devil advocate with myself: "I support projects by writing packages and making contributions" - sure, but that doesn't mean that you shouldn't be rewarded for your contribution. "This is a problem with Libre Software in general - there's little incentive in people to pay for it" - true, but I think we can also smooth certain corners. More on that below. "Well, what have you done to change this?" - Nothing. I'm the worst of both worlds, haven't contributed anything in terms of code or money to the community. That's not the point. "People do it for fun and not for money" - again, doesn't mean they shouldn't be rewarded. I look at this selfishly. Emacs has been attracting some top-notch guys that do some incredible things, and I want them to stay there working on the editor that I use. But alas, so far I have contributed 0$ in support. Why? I see myself spending anywhere around 100$ supporting the Emacs community for what I already have access for and maybe setting up monthly contributions if I believe that these money goes to further work on my editor. So why haven't I donated so far? While it is true that there are market failures that are characteristic of any open-source market, there are certain transaction costs that could be brought down with the kind of brainpower this community has. Firstly, let's take a look at supporting Emacs core. There's actually no way to do that I could find. You can donate to FSF project in general here, and while it is certainly worthy of your money to support the non-profit and their cause, I have following concerns(controversial): For my reasons, I don't use/know of many of the projects that FSF owns/supports. I use Emacs, and I wish to donate to Emacs. I believe FSF is missing out on valuable information when they make one big sink donation called "Support Free Software". How do you know which projects are needed by the users and which ones are not? It's akin to having an Android phone and instead of it being an open market it is "pay 100$ a year for a bunch of apps". However, the above critique is not enough to justify not supporting their cause, so in writing this post I decided to contribute. I encourage you to do so too. Emacs core out of the way, Why don't I donate money on Patreon or bountysource or gratipay? There is, of course, the obvious pain of tracking and setting up accounts and fussling with cards. There's the feeling that "It'll be fine", or "I'll do it some other time". So let's think how can we make a monkey with a short attention span like me to actually donate for his/her editor. When I find the desire to donate, I would like to donate for my entirety of Emacs experience - starting from Emacs Core and Magit to fireplace.el and tetris. I desire to mentally figure out a sum that I'm willing to donate(let's say 70$), a period of time(one-time or recurring), and spend as little time doing so. The way things are right now, the above is not possible. Time for some self-made criticism again. "You are just a lazy fuck. Invest some time in your day and pay some money. How much time a working day you spend messing around with your config? Wouldn't you want to more things to mess with?" I fully agree. There's little excuse. However, we are not done examining my editor yet - the vast majority of packages I use do not have a donation page at all. Given all of the above, I started writing a system that would alleviate some of my concerns. My first idea was the donate-emacs package/website combo. By installing(or just distributing with emacs) a donate-emacs package, it would parse your package-alist and make a post request to the donate-emacs server. It would then parse generate a page that looks something like this and presents you with dials customizing how you want to donate - one-time payment, once in a period, etc. This quickly presented the following problems: Suppose they donate money, how should they be transferred to contributors/maintainers?
Magit has something like over 100 contributors. Registering 100 bank accounts for users is silly. Measure it by commit numbers? Transfer the money to maintainer and let them do their thing? I'm not sure I can figure out the right way on my own.
Setting up credit card payments is a pain. These are donations that are supposed to be going to different bank accounts - and it's already a pain in the ass setting up a credit card system for one bank account(which would be mine and no one would donate money that way).
After some time, I decided in the making that I should manage cryptocurrency payments only - they are far easier to manage and don't present the third party problem inherent to credit cards. That is when I realized, why bother with websites at all? My potential users are Emacs users - if something can be done within Emacs why not do so? Why not make improvements to package-list that would include the interface I've outlined above? A user would pull the list of packages installed, press some C-c bindings to register a Bitcoin wallet and setup the donations however they want, and manage it anytime from emacs. Hence, I started to write wallet.el to manage cryptocurrencies within Emacs. This approach quickly presented problems too. It's easy to setup a Bitcoin wallet somewhere on some website and then forward the money from it to some Bitcoin address, but I haven't found an API or a cli that I could use that I would be able to do the above from emacs. So, I admit I'm way over my head and have decided to reach out. I know literally next to nothing about bitcoins and cryptocurrencies, and I haven't even finished reading through the Emacs manuals yet. Besides, I'm not even sure if the above is the right way to do it. What do you guys think?
#namecoin-meeting notes, 2016 08 21 # Present: Jeremy Jonas Brandon Midnightmagic Pigeons Joseph Namecoin Core The wallet name operation bug in Brandon's name tab PR has been isolated by Jeremy. Appears to be a bug in upstream Bitcoin Core (or perhaps Namecoin Core master branch) that has been fixed. https://github.com/namecoin/namecoin-core/pull/67#issuecomment-231316792 Whit Jackson submitted a documentation PR for building on OS X. https://github.com/namecoin/namecoin-core/pull/97 If anyone can test, please do so! Jonas will test this. Jeremy noticed that Travis CI accidentally flagged our repo as "potential abuse detected". Jeremy contacted Travis CI support and got our account whitelisted. Jonas notices that the Travis CI builds for our 0.13 branch are failing at the moment. Jeremy suggests filing a GitHub issue. Jeremy asked Jonas to submit a PR for Gitian builds for OS X. https://github.com/namecoin/namecoin-core/issues/38#issuecomment-236101580 DrHaribo of BitMinter requested that getblocktemplate be re-added to Namecoin Core. https://github.com/namecoin/namecoin-core/issues/98 Jeremy points out that since nVersion=4 blocks are nearing the lock-in point, we should deal with this sooner rather than later so that BitMinter doesn't get kicked off the network. Brandon asked on GitHub about how wallet unlocking should be done with the name tab GUI. https://github.com/namecoin/namecoin-core/pull/67#issuecomment-240852324 Upon discussion, Brandon currently plans to try using the raw transaction API for this. Daniel submitted a PR to temporarily disable the low-S standardness check. This should improve confirmation times for the old 0.3.80 clients. The check will be restored after AAA activates. https://github.com/namecoin/namecoin-core/pull/100 Test reports would be great. Jeremy points out that this needs to be done before nVersion=4 blocks are locked in. Jeremy wonders whether we should cancel plans to release 0.12 as stable, and focus on 0.13 branch. Tentative plan: keep maintaining 0.12 until Bitcoin Core releases v0.13.0; backport the name tab to whatever stable branch exists at the time that it's merged to master. SPV Jeremy's initial PR for Namecoin support has been merged to libdohj. https://github.com/dogecoin/libdohj/pull/18 Jeremy still needs to rebase the bitcoinj-addons code based on the libdohj changes made during review, and then submit a pull request. In the meantime, Jeremy's latest bitcoinj-addons and libdohj code is posted. https://forum.namecoin.org/viewtopic.php?p=16788#p16788 Someone please test it? Jeremy asks if he should post a link on Reddit. Jonas says yes. Jeremy will do so. ncdns Jeremy asked about the old fork of a Conformal library (see previous meeting); Hugo doesn't recall details but thinks it had to do with pre-Namecoin-Core not following spec properly. Hugo would be happy to accept a PR to make it use the current Conformal libs. https://github.com/hlandau/ncdns/issues/12#issue-163964219 Jeremy pointed out that sometime in the future we should fix the Extended Key Usage Critical flag on the dehydrated cert template. Go's standard library doesn't have a built-in way of setting that flag, which is why it's not in the first draft. Jeremy and Ryan can't think of any plausible attacks where it matters. Jeremy suggests a 1.0 BTC bounty for an ncdns NSIS installer. Possibly funded 50/50 by NMDF and a fundraiser. https://forum.namecoin.org/viewtopic.php?f=18&t=2566 Mining Cassini noticed that BTCC and ViaBTC have started mining Namecoin. https://forum.namecoin.org/viewtopic.php?p=16703#p16703 This is good news for mining diversity. F2Pool's share of Namecoin blocks is down to circa 43% as of July 26, 2016. Public Relations Cassini represented us at GETD#4 in Berlin July 22-23. Jeremy mentions that we should think about translation workflow. https://github.com/namecoin/meta/issues/35 Jeremy notes that Bitcoin Core is using Transifex. https://github.com/namecoin/namecoin-core/blob/mastedoc/translation_process.md Jeremy says that whatever works for Bitcoin Core, should probably work for us. Midnightmagic concurs. Joseph believes that Armory (post-ATI) is trying Transifex. Brandon asks what the pricing looks like for Transifex. Joseph believes it's gratis for open-source projects. Jeremy notes that Wikipedia confirms this. Jeremy wonders what safeguards are in place on Transifex to reduce risk of malicious translations. Joseph isn't sure. Jeremy points out that the way we organize the list of exchanges doesn't make sense for decentralized exchanges like Bitsquare. https://github.com/namecoin/namecoin.org/issues/70 Jeremy suggests listing decentralized exchanges at the top of the list. Jeremy notes that this might annoy the centralized exchanges who pay us for placement, but that this doesn't bother him at all. Midnightmagic concurs. Pigeons mentions that he's seen an increase in Namecoin offers on Bitsquare recently. Jeremy will have a table at the OU CS welcome party on Sept. 9. Let's try to recruit some developers! Brandon asks what the status is of the students from last year. Jeremy is sad to report that the SPV student and the UX student from last year are not participating this semester. Pigeons says a "Namecoin vs Blockstack" FAQ entry would be helpful. Jeremy will work on it. Midnightmagic asks if a meetingbot would be welcome. Jeremy says yes. Midnightmagic will look at setting one up. Funding Jeremy has filed a complaint with Tip4Commit about their usage of CloudFlare CAPTCHAs. https://github.com/tip4commit/tip4commit/issues/300 Tip4Commit has not responded after 25 days. BountySource balance: $5/month from 1 recurring supporter Total funds available: $304 USD Pigeons suggests looking into Patreon. Jeremy notes that they have CloudFlare CAPTCHAs. Jeremy notes that Wikipedia says they take a 5% commision, which is half of BountySource's 10%. Jeremy notes that some free software projects use them currently. https://www.reddit.com/linux/comments/33dp6n/should_open_source_projects_use_patreonkickstartecqkrlkf Jeremy will look into this in more detail later. NMDF incoming funds: 0 mBTC received since 2016 07 03 0 NMC received since 2016 07 03 Pigeons suggests looking into Flattr. Jeremy notes that they have CloudFlare CAPTCHAs. Jeremy notes that Wikipedia says they take a 10% fee (same as BountySource). Jeremy will look into this in more detail later.
Note: I made a typo in the title of this post on Reddit; the quoted date of the meeting is correct. (I can't see a way to edit the title of a Reddit post.)
#namecoin-meeting notes, 2016 07 03 # Present: Jeremy Jonas Samurai pigeons midnightmagic Decentralized Web Summit Jeremy attended DWS. Blog post summary is in namecoin.org PR. https://github.com/namecoin/namecoin.org/pull/64 Note the new News layout / links, the Earlier News link, and the new post from June 20. Jonas ACKs. Namecoin Core Merged Mining Jorge Timon suggested replacing the MM chain ID with the BIP 122 chain ID. https://github.com/namecoin/namecoin-core/pull/75#issuecomment-228597157 OS X Gitian Builds Jonas posted an OS X Gitian binary of Brandon's name tab PR Jonas will look into submitting a PR. Look into deterministically generating SDK input. PGP keys Jonas reminds everyone that we need to get our PGP keys into GitHub for Gitian. AAA hardfork Samurai asks if any problems expected short-term. Jeremy is pretty sure we're fine until Bitcoin schedules bit 0x100 for VersionBits. SegWit is bit 0x2. SPV Jeremy sent PR to libdohj. Currently undergoing review. https://github.com/dogecoin/libdohj/pull/18 Specs Jeremy posted draft Dehydrated Cert spec. https://github.com/ifa-wg/proposals/pull/24 Review would be appreciated. ncdns Jeremy noticed a bug in ncdns's JSON-RPC library that breaks connecting to the SPV client. Jeremy fixed it, but wonders why we're even using that library. It appears to be a very old library from Conformal that was abandoned over a year ago. Bring this up with Hugo (he didn't attend this meeting). Public Relations A bunch of website PR's have been ACKed by Jonas and merged by Jeremy. https://github.com/namecoin/namecoin.org/pull/59 https://github.com/namecoin/namecoin.org/pull/60 https://github.com/namecoin/namecoin.org/pull/62 https://github.com/namecoin/namecoin.org/pull/65 https://github.com/namecoin/namecoin.org/pull/66 https://github.com/namecoin/namecoin.org/pull/67 https://github.com/namecoin/namecoin.info-dotbit/pull/10 Jeremy added new "Donations" page to website. https://namecoin.org/donate/ Jeremy added new FAQ to website. https://namecoin.org/docs/faq/ Funding libcoin-related bounties have been refunded by BountySource. BountySource balance: $5/month from 1 recurring supporter Total funds available: $299 USD NMDF incoming funds: 98.4 mBTC received since 2016 05 15 0 NMC received since 2016 05 15
I felt that i understood the blockchain by now, but the range of transactions that are possible, their usefulness, and the apparent ease with which they could be implemented in that understanding dont seem to match reality. The question then is, either there is a reason it isnt being implemented, in the newer coins, or my understanding is off. In older coins, maybe they are afraid it will break things in existing coins, but then the question is the same about the new coins. Now for my understanding of the blockchain: Basically you take a checksum of appended:
checksum_of_previous block miners_pubkey value_you_scan_for_mining (each one gives a new checksum with a shot of beating the difficulty) accepted_transactions ... (whole list)
The result of the checksum is the score, if you get a score below the current difficulty for a correct block. (Havent figured out how that is agreed on yet) You win the block, and may refer to it, to use it as money in your reward. A block is correct only if the transactions are also valid; i.e. dont send more than a wallet contains, all signatures must check out.(most transactions have signature, unless they're attached to the miner somehow) Of course some point in the network may not know about better scores existing, to avoid that, the longest chain wins. Miners and nodes would become aware of longer chains implying their earning would go lost if those chains won outright, so they'd switch. Edit: whether the above is correct is essentially the question, the below indicates the kinds of transactions that seem missing. However in this understanding transactions can be really arbitrary, basically anything the other nodes can check. And apparently bitcoin has a whole scripting language for them, but why isnt it being used? There are many potential uses:(not neccesarily of the scripting language, but in principle doable with transactions)
Regular transactions just send money, of course.
"Transact, but leave on hold" and "finalize transaction", when a buyer is unsure the seller will actually deliver, the seller or buyer both put coins attributed to no-one, when the product arrives, the buyer can put a transaction on the blockchain that releases the coin in both directions. The seller gets paid and some of his 'promise coin' back, and the buyer gets the incentive to release back.(edit: promise coin by the seller need agreement from the seller first. The seller can sign something for the buyer so the buyer cant do it one sidedly, but the seller doesnt have to put something on the blockchain for it)
Gather inputs, miners could earn coin for taking accounts with a really old inputs and put a transaction on the blockchain saying 'this pubkey has this much coin, no need look further'.(and it would have to be correct of course) This achieves two things 1) the next transaction of that pubkey only needs to look at one input. 2) eventually, beyond some age, there is nothing you need to look further back in the past for. That past becomes irrelevant and can be thrown out.(this one is signed by the miner itself, doesnt need a secondary signature)
Crowdfunders would hang coin in the air, diverting it to the person that started it if enough coin is gathered in time, or cancelling it all if it isnt.
Bountysource releases coin by vote. However this one is actually difficult, as you have to figure out how to do the voting. Stake doesnt help because a big player could add a lot of money and vote to send it to himself.
Sending people a signed message giving them a probability of being able to detract coins. The purpose is to have exceptionally small transactions be turned into bigger transactions that also just have a small probability of occuring. The sender signs probsend the receiver only has a shot at getting the coin though, he has to put a transaction out: probsend_success but it would only be accepted if the checksum meets the difficulty.
This one is likely difficult too. A variation on that idea is for data serving basically pubkeys with some coin in them can view data stored on servers, to request it they sign view and send the request and signature. The server serves it up, and waits for the viewer to send the signature of viewed . Once it received that, they can get a transaction if served and a given number of attempts, reward and difficulty of the checksum of such a transaction. To give the viewer incentive to actually send back the signature, the first signature, asking for the data can alternative used to destroy coins of both the server and viewer.(that approach may not actually work, of course)
Asking Bountysource.com to add other forms of payment
Bountysource! is growing by day having accepted projects in all areas. So a request was made towards their support to accept other forms of payment:
To whom it may concern, Bountysource growth and acceptance in the community proves that the initiative has an open minded view of new technology. One of the best way to further reach to the community would be to accept new forms of payments. Some would be even easy to integrate and others might require contracts and other financial agreements. Some of the suggestions include:
Credit card payments (administrative heavy for such a project)
Matching Donations: Register/Manage Names with Libcoin Rebase / Lite Client
Hi, As you may know, the Namecoin dev team has been working to rebase namecoind and Namecoin-Qt on a newer codebase, specifically libcoin (a refactorization of Bitcoin Core by Michael Gronager of the Kraken exchange). This is because namecoind and Namecoin-Qt are based on the Bitcoin 0.3.x codebase, which is not really maintainable. libcoin has a lot of nice benefits: most notably it makes it easier to produce trust-free lite clients (we've already done some experiments getting the stored blockchain reduced in size significantly, see http://blog.namecoin.org/post/91019719220/libcoin-lite-client-storage-mode ). Right now libcoin does not support the name_new, name_firstupdate, and name_update RPC commands, which are a prerequisite to the rebase. (It already supports name_show, name_filter, and name_scan.) To help speed up development, the FreeSpeechMe fund will be matching donations for this feature 1:1 up to $50 USD (so up to $100 bounty total). The bounties are handled via BountySource; this means that no one can redeem the bounty until the GitHub issue is closed. BountySource's escrow services are built in to protect against fraud. Both USD and BTC are accepted by BountySource. So, if you'd like to support Namecoin development and have a few dollars to spare, please consider posting a bounty. You can do so at the link below. https://www.bountysource.com/issues/3161846-name-management Cheers! -Jeremy
This week the popular funding platform Bountysource announced that it will accept Bitcoin for developer and software funding efforts. Bountysource is a funding platform for open-source software, and is a place where users can improve the projects they are passionate about by creating or collecting bounties and pledging to fundraisers. By using the platform, developers can earn money from ... CanYa has recently announced the purchase of Bountysource, a global peer-to-peer (P2P) open source software bounty system.CanYa, as a blockchain-based decentralized autonomous organization, fits well with Bountysource’s business model and will build an international community where any number of digital services can be provided. Bitcoin Private BTCP Community Update 13 The Rebase and BountySource Update News • bitcoin private btcp bounty cryptocurrency blockchain crypto update • • cryptoking: 1: WCN Bitcoin Group 146 – UAHF – Price Tumbles – Coinbase Freeze – Dennis Rodman: 1: آموزش جامع و کامل کسب در آمد از سایت freebitcoin: 1 BountySource is a funding platform for open-source bugs and features. Anyone can can post a monetary bounty on an open source project's issues (currently only projects hosted on Github are supported), encouraging other developers to come and work on a solution. Bitcoin Private Update – BTCP Pay – Zeltrez Wallet – BountySource – Get Down On It! February 21, 2019 admin Bitcoin For Beginners 19 In this video I revisit Bitcoin Private and the progress they’ve made with BTCP Pay, their Merchant Payment Platform, as well as their requests for community …
History Suggests HUGE Bitcoin Bull Run Incoming ...
BITCOIN TODAY: In this video, I'll go through the Bitcoin news today & I'll make a Bitcoin price analysis. The BTC news & analysis can be inspiration for you... A LOT OF GOOD NEWS TODAY! Bitcoin's Energy Value just hit an ALL TIME HIGH! This is "Super Bullish" according to Charles Edwards of Capriole Investments. Lik... In this video I revisit Bitcoin Private and the progress they've made with BTCP Pay, their Merchant Payment Platform, as well as their requests for community development via BountySource and the ... Bitcoin Technical Analysis & Bitcoin News Today: I'll use technical analysis on the Bitcoin price to make a Bitcoin price prediction. Watch the video to learn more! MY INTERVIEW: ... Skip navigation Sign in. Search