TXID - How Does Bitcoin Work?

Recap of AMA with Zac on July 3 and Q2 report

Dear Pundians,
Thank you for participating in the AMA session with Pundi X co-founder and CEO Zac Cheah.
For those of you who may have missed it, the live recording of the AMA session held on July 3 at 10:00 am GMT+8, tackling Q2 progress and addressing questions and concerns by the community members, can be viewed here. A side note that today’s AMA video quality and setting was not ideal. We acknowledge this situation and will make improvement for our next AMA session.
You may also find a summary of the Q2 progress presentation as well as all the detail Q&A below.
## Pundi X Q2 2019 Highlights
* Pundi X has integrated more public chains into our products. In Q2, we completed integration of Binance Chain. NEM chain is in the work. As of today we’ve launched BNB, the Binance Chain native Coin and XEM, NEM native coin on Pundi X payment platform. We will integrate at least one more public chain in Q3.
* The transactions on XPOS for Q2 is 15.5 million in USD, which is close to 300% quarterly growth. The number of transactions is 29,367, which leads to a 11% growth QoQ.
* XPOS has successfully received FCC and KC certifications. A new certification for Latin American market is on the way. * To expand XPOS footprint, Pundi X’s integration with a new leading mainstream point-of-sales device is in the work. Stay tuned for the announcement.
* Pundi X Open Platform was launched in May, 2019, which now supports ERC20 and BEP2 token listing. Moving forward, we will continue to support tokens from other public chains.
* A 3,000 XPASS order from DigiX, a gold-based token, and a 10,000 XPASS order from BitCobie this quarter.
* XPOS is spread in use in over 30 countries. We’ve published a map of XPOS location of self-report XPOS merchant directory. You can find a list of selected XPOS merchants at [https://www.pundix.com/products\](https://www.pundix.com/products). * The QoQ growth of XWallet is tremendous at 43%. In the previous quarter, we have less than 20k users, whereas in Q2 we have hit 297k XWallet users.
More updates on XWallet:
* Supported BNB and NEM tokens; 2FA, face ID, and optimized SMS serviceAvailable on iOS, Android as well as in Samsung Galaxy Store
New features coming up in Q3:- DApp integration - Decentralized wallet- In-app crypto payments - Chat service, which will be compatible with a commonly used chat app- f(x) testnet features to be rolled out first in XWallet
## Other notices coming up in Q3 2019
* The Q2 token removal will take place on July 14, 2019, which will involve in total 34 billion of NPXS and NPXSXEM (22 million worth in USD) removal. In the past 365 days, we’ve removed a total of 36.1 million US dollar worth of NPXS and NPXSXEM.
Before Q2 removal, the total supply of NPXS ERC20 is 266,962,422,906.53 and NPXSXEM is 95,816,218,929. [See Q1 removal here.](/pundix/recap-of-ama-with-zac-on-july-3-and-q2-report-a23de165dd28)
* [NPXSXEM will be ported to Binance Chain from July 20](/pundix/npxsxem-will-be-on-binance-chain-c6485f17726b). * XPhone pre-order will start in late July with a new product name. Stay tuned. Check out the teaser video that we are releasing it across our communication channels. ## Q&A
## On XPOS
* **Where are we on official global location of XPOS?**
Zac: We have made a map on our official website that merchants can self report and feature their locations. It’s at [https://www.pundix.com/product\](https://www.pundix.com/product). We’ll be increasing and updating the map once we have permission form the merchants to update their locations.
* **The marketing from pundi has shifted from 100,000–700,000 xpos units by 2021 to 100,000. I understand the bear market has affected this but please share the strategy moving forward to hit your goal. How do you feel about hitting this goal?**
Zac: The 100K XPOS target has always been the initial goal and it’s stated in our whitepaper. And we are still working on achieving the goal by the end of 2021. Part of our growth strategy is to also explore the possibility to port our platform to traditional POS manufacturers to increase the adoption, which is ongoing at the moment.
* **1 year ago you sent 5000 XPOS somewhere. When, at least half of them, will be working? 3 year target was 100,000 by 2021. Now we have only 150 units, how do you expect to reach this goal?**
Zac: Yes, we have shipped thousands of XPOS to over 30 countries in the world. The 150 you’ve mentioned are the featured merchants which are published on the map. The active XPOS devices are deployed over 33 countries and we are actively talking to B2B partners to have higher wholesale and big deployments.
* **How many XPOS are live and used?**
Zac: We have gone through a very serious bear market, and some of the initial inbound requests for XPOS are not delivered. However, we are working slowly but surely with our Business Development team to not just roll-out into individual buyers, such as what we did on Pizza Day, but also to B2B partners. With the certifications approved, that will also help us to officially roll out to some of the key markets.
Individual merchants can use XWallet collection feature to accept crypto payment with QR code. For the merchants who have physical offline storefronts, they can use XPOS to enable the instant crypto transaction seamlessly. Moreover, as mentioned previously, we are exploring the integration on leading traditional POS terminal so that their distributors have option to enable crypto transaction feature. As for the challenge to adopt XPOS, it is the regulatory compliance in different countries. For this, our legal team think ahead and encourage our merchants to complete KYC.
I must be very honest to say the activation takes longer time than we expect but it will be worth at the end.
* **What’s the average number of transactions per xpos in use?**
Zac: The transaction number has increased very well. The number of each XPOS differs, due to the frequency of using crypto currency to purchase item or crypto assets. There’s no standard answer to this, but overall we see the transaction number and volume are going up.
* **How do you plan to reach the target of 100,000 by 2021?**
Zac: One of the challenges that we have is regulatory compliances in different countries. There are certain markets that do not allow crypto currencies and some require a clear approval for us to deploy XPOS. We are working on both challenges by talking to governments and applying for certifications. So how we plan to reach 100,000 XPOS user by 2021 is to work with distributors, B2B partners on a government / business level, and with existing POS companies to integrate our software solution into the system.
* **We understand as there was bear market and hence Xpos usage demand was low. Are you guys seeing growth of Xpos usage with current market conditions. Can you guys put some statistics comparison like last 30 days Xpos usage vs any month from bear market usage?**
Zac: It is very clear that as we moved out from the bear market, the demand for XPOS has been increasing. As we’ve shared just now both the transaction number and volume of Q2 have beaten Q1. We’ll be able to share more transaction numbers once we receive approval from our XPOS merchants.
One exciting thing is that, with the listing of different tokens, we also see users using these tokens as a way to transact on XPOS, which means we will be having more ways to transact and this is a growth point for XPOS.
* **When will there be more details for XPHONE and XPOS HANDY?**
Zac: For XPOS handy, we have finished production and it will be released in Q3
* **When will the iOS version of XWallet and XPOS be fully translated to other languages?**
Zac: Right now, the XWallet has Traditional Chinese, Korean, Spanish, German and English. With the latest version update, it now includes Portuguese. XPOS also comes with many languages and we hope to finish with more language, either working with professionals or volunteers. If you’re interested in volunteering, please contact us.
* **When will the Merchant back office have Product Registration and SKU id ability and also integrate with other POS software?** * **When will the top-up feature go away for XPOS to allow liquidity for XPOS**
Zac: We constantly update features in XPOS and merchant backend to make it easier for distributors and merchants to use. We understand that one of the ways for mass adoption is to enhance our distributor management system. With that, the distributors can manage manay XPOS at one time with different merchants.
Please stay tuned as we announce more and more functions of this feature.
## On Dubai
* **When will we see the deployment of the XPOS in Dubai?** * **Can we spend NPXS on the Dubai XPOS?**
Zac: As with all big projects there are a lot of moving parts, that includes working very closely with the local government, in Dubai’s case, the Credit Bureau of the Finance Ministry. Things are progressing for the Dubai project but due to confidentiality agreements with the parties involved, we cannot reveal much. All we can say is that we and our Dubai partners are working hard to have XPOS roll-out in the Dubai market and the UAE.
We are also discussing aggressively with Dubai partners whether to include crypto assets in the XPOS in Dubai. That clearly will involve local compliance and legal for that to happen.
* **Your system upgrades expect merchants to have downtime on their XPOS terminals, can you explain if you plan to run a business why this would be considered feasible (specially at the rate you have been doing your upgrades)?**
Zac: Yes, the benefit / strength of the XPOS is that most of the updates can be done on the fly. For example, when we have a token update on our XPOS where developers submit their tokens on Open Platform, the updates of this token are on the fly, which means that once we approve the token on our Open Platform, it will automatically appear on XPOS without any software updates.
The great thing that we believe about XPOS is not just the support of crypto assets, but also the ability to update most things on the fly, which means that whenever we have a good feature or a new token, the updates will be done instantaneously.
* **Can you guys arrange at least a community voting which is the next blockchain we would like to see next in XPOS? Voting will help to prioritize to chose the projects.**
Zac: One of the reasons why BNB is being listed on the XPOS is simply because of its popularity and also our user demand, in a way that we are already answering to our community’s request.
Right now, our main focus is getting all the tokens submitted on Open Platform to be listed on the XPOS. The submission process includes legal and compliance valid, so our legal and compliance teams are working hard to make sure that we have more tokens to roll out onto Open Platform, which means that they will be on XPOS, XWallet, and XPASS.
As to a specific voting mechanism, we’d like to consider that and hopefully we’ll be able to run a specific voting for the chain which users would like to see.
* **While comparing Xpos handy to Square POS devices at least with mobile it’s very cheap like under $30 and easy to use. When can we expect such light weight and cheaper version for XPOS? Is team working on such devices ?**
Zac: There are different POS companies around the globe and pour focus is to work with these POS companies with our software, so that a crypto sales feature will be part of the existing POS system. The more support of crypto asset usage using our software on existing POS, the better it is for global adoption.
We actually strongly believe that the pricing of our POS system is competitive in the market. And one of the great features of the XPOS is that the merchants will not need not to pay a certain percentage to existing acquirer but to be able to earn certain percentage from each transaction. That is the key differentiator for merchant to want to adopt this.
* **From the website with some of the key Countries for XPOS adoption looks great. However, the concern is for Venezuela, there is no reference link like the others have. Can you guys add the link with details to clear the ambiguity?**
Zac: Let’s give a little bit more patience so that we can actually release more information about our Venezuelan partnership. The good news is that we expect concrete news from Venezuela in the coming 2 weeks. So stay up-to-date about our Venezuelan roll out on XPOS, the best way is to subscribe to our telegram group for Venezuela.
## On Partnerships
* **Are there some major partnership in the works? I’m also interested in how you do immediate transactions? Do you anticipate scaling issues?**
Zac: The way XPOS is being designed is that when you use your crypto assets to purchase, it will have instantaneous confirmation because the action is an off-chain process. An on-chain action happens when a user who owns crypto assets in our system transferring the assets out of the Pundi X ecosystem to their own wallets; or to transfer crypto assets in Pundi X from an off-chain to a private wallet, which we will have very soon on XWallet itself.
That is why we are able to handle scaling. When a person wants to use crypto currency to buy a coffee, the transaction will happen instantaneously.
For specific partnership, especially with B2B partnership, we oblige to the NDA that we have signed. But if you follow us closely, you’ll know that we go to different parts of the world, talking to major companies to try to land more deals so that NPXS usage will increase dramatically.
* **Any big partnerships for making xphone or using the software for xBlockchain?**
Zac: These partnerships are also subjected to NDA, so please be patient for us to release more news.
* **When will XPOS have approval to process Visa and MasterCard payments?**
Zac: We have met representatives from these players including some of the key management people. They are obviously looking into crypto currency attentively, and we hope that there’s something we can do with MasterCard and/or Visa.
This is something that the community has suggested and we agree fully. Please allow us with some time to work on this. We have also showcased XPOS to the CEO of MasterCard. For what or when will anything happen, please wait for our official announcement.
* **What’s the status on Quantum fund and their contribution or involvement with Pundi’s project?**
Zac: We announced last year that we are creating a fund to invest in projects beneficial to our ecosystem. We’ve identified some interesting projects, and we have invested in at least 1 project. The reason why we’re investing in that project is because of the services that it will bring onto the Pindi X ecosystem. So the purpose of the investment of the companies is that these companies in turn will benefit on our ecosystem. This is our key consideration.
The team has evaluated the projects that will benefit the Pundi X / Function X ecosystem. Vic and his team will be able to reveal more details on the companies we have invested in and how they will contribute to our ecosystem in Q3.
* **Recent update on NPXSXEM is highly ambiguous as mentioned that it will be now BEP token and later once FX goes live it will get back to Fx platform. Why you guys had so rush to use Binance chain only for few months? Isn’t you guys switching to much in a short time span?**
Zac: Liquidity and utility have been an issue for NPXSXEM. Due to the design philosophy and the limit of token that can be created on NEM’s smart contract, we are only able to create a small number of tokens on NPXSXEM. By moving into the Binance chain for NPXSXEM, the BEP2 token version will be able to support all the NPXSXEM tokens, which means that we’ll migrate and also be able to make sure all the NPXSXEM tokens are under the same contract address.
We believe with the strong liquidity, we will be able to give our NPXSXEM token holders a good reason of what the token holders have been waiting for. We hope to bring NPXSXEM to match the level of NPXS.
* **When #XRP?**
Zac: Our OpenPlatform is a currency agnostic platform, which means that we will work on integrating public chain as well as tokens that are most requested by the users. We’ll also be looking into the listing of different tokens that are being mentioned by the community.
As said, we will have at least one more public chain integration in Q3, perhaps even more.
* **Are you as a company going to try and connect with libra? If they have said they want to be a payment remittance service, have Square, PayPal, Visa on board I as an investor would prefer you try to join them rather than beat such large competitors**
Zac: Of course, we’ll be delighted to work with Facebook and also the Libra coin. Pundi X and XPOS is a currency agnostic / currency neutral platform, if there’s opportunity to list Libra coin or work with Facebook in different ways to promote crypto currency adoption, we’ll certainly look into that and work on reaching out to them.
## On Trading
* **Can you confirm during AMA, Pundi team is not involved with any trading with their own token like selling over time to manage the fund to run the company.**
Zac: All the wallet addresses of the team holdings are disclosed and transparent. This is one of the first things that we did after ICO. Hence, our token holdings are transparent and everyone can monitor our fund transactions. Also, we have strict internal financial regulation and compliance, shows that we are here to build a long-term project.
The best way to make NPXS or the NPXSXEM to rise is real daily life use case.
* **When will you stop manipulating NPXS chart?**
Zac: Our focus has always been and will be building great products. The more product usage, the demands for NPXS and NPXSXEM will increase. Let’s address again that, Pundi X the company is NOT involved in any manipulation of the NPXS price.
There are trading teams, market makers, financial institutions that profit from the drop and rise of token prices in the crypto market. The good thing about NPXS is that we have managed to create a high liquidity by listing on 40+ exchanges and having global trades and demand from all over the world. We hope this and coupled with the fact that we are a solid product and roll out the use cases, the demand of NPXS will only continue to rise and will be able to deter any of the traders or speculators there is for NPXS.
These traders gain profit from manipulating tokens whether BTC or other tokens. In fact, the traditional financial markets have similar challenges as well. What I want to stress is that, we at Pundi X, do NOT speculate or manipulate the price. We work very hard to create demands for NPXS and as a company, it is only beneficial for us to see the prices of NPXS and NPXSXEM rise.
* **Can we please address the elephant in the room which is the Binance bot with huge sell walls and buy walls causing huge distress and concern among users?**
Zac: First, I cannot confirm nor deny that whether Binance has a bot. I think this is something that you need to ask Binance. We need to work with Binance because Binance has one of the biggest liquidities, if not the greatest liquidity, for NPXS. The best way to counter manipulators is to create more use case, more demand and more acceptance of our tokens.
* **Why on almost all exchanges do you not offer a USDT trading pair?**
Zac: We have USDT trading pairs on Bittrex, Bittrue, and more. In addition, we have fiat pairs in Korean Won, IDR, INR, and Turkish liras. We will continue to work on adding trading pairs for NPXS to make it more liquidate.
* **Why don’t you offer a stable coin sell and purchase on the xpos to help with adoption? Places in Africa with volatile currencies would go crazy for this.**
Zac: It’s a great observation. This is a request that’s been asked from many users. We’re working on stable coin listing on XPOS and hopefully it’ll come soon. Stable coin requires a greater compliance and legal validate, which we have been working on since months ago and we hope to have the stable coin up in XPOS soon.
* **When will you add an active tracker for coin burn, whether its measured in usd, NPXS or whatever you choose. The community has been asking for this on twitter, reddit and telegram for this entire year.**
Zac: It will be hard for us to have a daily tracker of the coin burn, but what we might be able to work on is a tracker which have shown all of the tokens that have been removed from the usage. Thank you for giving us this great suggestion and we will work on it in some form.
Zac: Our token supply has always been specified in our white paper, and as promised in our white paper, we will continue to remove tokens through usage and use cases, which we’re working on all the time.
* **Price movement. When will NPXS go to which price?**
Zac: We cannot comment on the change of the price. Our focus is on building products. We hope by doing that the NPXS value will go up. Again, there’s no way that we can comment on the price.
**I believe that burning tokens every 14 weeks keeps the price suppressed and will only lead to huge pumps and dumps. Imo, If the burns were more frequent, the price would move organically.**
Zac: We continue removing tokens quarterly per advised by our legal and compliance team.
**Is it mandatory npxs swap? What happens for token we have in binance?**
Zac: No it’s not a mandatory NPXS swap for FX.
**How many NPXS or NPXSXEM was converted?**
Zac: In Q2, we will remove 29B NPXSXEM and 9B NPXS.
## On XWallet
* **Why not put in XWallet like the place where we can buy and sell like restaurants and shops?**
Zac: You are correct. In fact, if you look at XWallet, there is a merchant feature, whereby you can register as a merchant. By becoming a merchant, you will be able to print out your QR code and stick it on your restaurant. People are able to make payment through this QR code. This will act like a mini-XPOS.
* **In addition to that having multiple different blockchain in XWallet will increase the XWallet adoption. Hence, we would like to see aggressive game plan and execution from the team and would like to hear that**
Zac: That’s a great suggestion. Every day we want to increase use cases for XWallet. In fact, our XWallet update is one of the most frequent in the market. Within 5 months, we have over 10 updates on iOS and Google Play. This does not include soft update which happens every several days. In my view, the effort is very tremendous.
* **Is there any plan to add Swap option within XWallet so that people can trade the coins within XWallet?**
Zac: Yes, there’s such plan and in fact there is an upcoming feature that people will be able to use coins in XWallet to exchange into other things. The exact form and format have not been reviewed. We hope to share more when we have concrete example. But what you suggested is what we are planning for months ago.
* **When will XPOS and XWallet have fiat on ramps?**
Zac: This is a good question. It’s not only involved with regulatory compliance but also involved the technical part. This is also something we are planning for months. Once approved, hopefully we are able to support fiat currency on ramps and off ramps on XWallet.
**On Others*\*
* **How is the internal organization doing? Currently how many employees work for Pundi? Currently how many job positions are open?**
Zac: Pundi X has grown tremendously. We are now having over seven offices around the globe. I’m sitting in the Singapore office. We have office in Jakarta, Taiwan, Tokyo, Shenzhen, São Paulo and London. These are the places we have physical offices and house approximately 100 full time employees of Pundi X.
The positions open from Pundi X are legal associate in Singapore and other offices. We are looking for more R&D people, especially in Taiwan. We are looking at marketing and PR people in different parts of the world. And we are looking for POS distributors. As a POS distributor, you will work with our business development team and also our technical team to roll out many XPOS which you have a network to control in your local market.
* **Would you consider removing the KYC to allow u.s. holder to stake and be rewarded?**
Zac: We would love to have more users, including US. However, our compliance and legal advisors have not allowed us to accept US holders to stake and be rewarded.
I’m sorry to say that but this is after serious consideration to make such a decision. In fact, it is a very hard decision because we have healthy user base in the US.
will continue to monitor the situation in the different markets and be compliant. There are also ways to be rewarded when using XWallet service without KYC. We are looking into to explore more on this and launch new features. Hopefully we are able to bring the beta version for you to test this week or next.
**On XPhone*\*
* **Where are we on pre-sale announcement of Xphone? It was highlights of Q2 goal. If we are getting delay, that’s ok. But at least community will have some clarification why it’s getting late and when approximately it coming?**
Zac: Pre-sale order will start this month. It’s likely the end of July. Pre-sale will take place in different channel including the official website and XWallet. Apart of our own channel, the pre-sale will go live on a 3rd party channel. People will be able to pre-order crypto either in crypto or in fiat.
* **Can you discuss in AMA, is participants can pay with Crypto or Credit/debit card or in both ways?**
Zac: As a crypto company, we prefer payment in crypto, but fiat, Visa, MasterCard, and other traditional payment methods will be accepted on different pre-order channels. Stay tuned for pre-order which will happen in late July.
* **Will the Xphone be open to purchase in all regions of the world?**
Zac: Yes, pre-orders will be able to be done on-line, and products will be shipped from our offices to users in different parts of the world.
* **Will the blockchain mode on the Xphone be operable during the testnet or will this function not work until mainnet?**
Zac: XWallet and XPhone are the first channel and avenue for Function X testnet, so once the testnet is operateble, we will start to engage certain services on XWallet and XPhone into Function X testnet, and ultimately into mainnet. Slowly but surely.
* **Does Xphone have hard protective cover,extra Sim slot, also is it enhanced with ip68 water rating?**
Zac: XPhone will not be waterproof, so please do not submerge XPhone into water. XPhone will definitely be eavesdrop-proof because we’re using a blockchain mode, only you and you control your own conversation.
* **Which country accept the Xphone?** * **Will I also be able to use the SIM-card?** * **The blockchain modus will work in every country (what in the absense of nodes)?** * **Will the XPhone I buy now support updates in the future?**
Zac: People from any country will be able to buy XPhone on-line. You will be able to use a SIM for we have built a SIM slot. Wherever you are, the XPhone can be turned on to become a node.
Will XPhone support future updates? Yes, of course. Just like the XPOS, we support silent update. It will be like how we support XPOS, many updates. The updates will always be supported on XPhone.
**On Function X*\*
* **When is the detail white paper coming for FunctionX? Why the team is very resistive to have well documented white paper? We need scientific approach and well documentation on FunctionX to have developers to be more involved.**
Zac: Yes, developer involvement is a key criterion of the growth of Function X. We have done 2 things, one is that we have set up Function X Foundation which is led by David Ben Kay and will involve third party adviser and board members. Second, we have set up a developer relations team led by one of our own members as well. This team will work on creating developer documents, developer demos and sample, so that excellent developers can tap into working with Function X resources.
The first version of developer documentation is ready in English and Chinese. We are still polishing up the documents and hopefully to release them soon.
We are also working with third party developers, and are engaging at least 2 third party developer companies, so that we can help create their services on Function X and also XWallet.
We are hoping to showcase a smooth and usable service to the audience, we think this is the key criterion of the Function X growth.
Thank you for this suggestion. We need to update more often on github developer documentation as well.
As for the white paper, we did not have one per se because Function X did not do an ICO. But we will continue to update our white paper and include not only technical details, but also details on the chain and how we can get more developers and users so that the future hardware will be added as a node and you will be rewarded financially, at least through our ecosystem genesis fund. Please stay tuned and there are a lot of things going on in the company. Each and one of us is working hard.
* **Why does the FX ecosystem need a decentralized OS?**
Zac: The mantra of Function X is decentralization and having private control of your data. A full private control of your data comes with a decentralized system not just in transmission of your data, but with the operating system built fully for decentralization , which includes a transmission protocol replacing http. The apps uploaded into Function X will be decentralized as well as the data that is stored on the app, which means that how BitCoin or crypto assets are verified on different nodes will also be part of the way we store data and content.
The decentralized OS is key to fulfilling a decentralized environment for a more private and free usage.
* **What about FX are you most excited about?**
Zac: We are actually creating a shift of how people view of blockchain and how decentralization is not just about transacting commercial commodity, but also data, including your identity, are all decentralized. That is what we are most excited about.
The only way for us to achieve this is to have developer support, for we need the developers to build on the foundation we have to offer those exciting services.
* **We understand that developing a new blockchain is time consuming. As a community we are in a dark space to understand where exactly the development of FX right now.**
Zac: We are working hard on creating the testnet and eventually the mainnet. For the latest updates of Function X, what I can encourage you to do is to go on and subscribe to the Function X telegram group where discussions are made. We have formed the Function X Foundation and created the developer relations team, so that the Function X progress will go smoother and with more partnership from outside, whether it’s developers, third party companies, teleco, etc.
* **When FX goes live on the mainnet, will FX coin be used to stake and earn NPXS? how will staking work on that new mainnet?**
Zac: The NPXS/NPXSXEM staking will last till March 9, 2020 as announced. What we are committed is to create more use cases. For FX tokens, the use cases will be focusing on the Function X Chain and the use cases on Function X that include DApp on Function X and different hardware/software services.
* **When fx testnet will be available?**
Zac: First I would like to thank you for your constant support. In Q3, we plan to open Function X testnet so that we will be migrating and creating certain use cases that can be used on Function X testnet, starting with our own XWallet. Which means, the XWallet will migrate some features into Function X testnet, and slowly followed by our other Pundi X products, including XPhones, XPASS, Open Platform and Function X own developer related products from third parties.
submitted by crypt0hodl1 to PundiX [link] [comments]

[uncensored-r/Bitcoin] I'm attempting to return stolen bitcoin and warning soon to be victims

The following post by MrBeanCoin is being replicated because the post has been silently removed.
The original post can be found(in censored form) at this link:
np.reddit.com/ Bitcoin/comments/7lnsdx
The original post's content was as follows:
Hello!
My name is MrBeanCoin (Not a obvious throw away! Of course not!). I'm my professional life I am a Malware Analyst, Pen Tester, and Engineer. However when im not working my eyes have been glued to the BTC charts, kicking myself for spending my BTC back when times were rough. But enough about me, lets get to the point.
 
Since the rise in price and popularity of Crypto's, Malware Authors have been leaving Ransomware, Botnets, and Spam in droves to create very simple Bitcoin and Altcoin stealing Malware, in a attempt to make the most money quicker, and separate good people like yourself from your coins. Miners have also reached unbelievable heights (Surpassing even when BTC first came out), and they make sure not to use safe settings, and a lot have been causing hardware damage. The spike has been so large that this week, the GTX 1080 i have in my Cuckoo Server (Automated Malware Analysis Platform) burned out from the constant throttling up and down.
 
So obviously, with my job, i have been having to deal with these fuckers and their shitty coded applications a lot. Some go as far as ripping your wallets from your machine and uploading them to a C2 server, but the absolute most common way people are losing bitcoins by the THOUSANDS is by the most simplest application i have ever seen. It simply lays low on the machine, and when it detects a BTC Address on the clipboard, it replaces the address you copied, with the Malware Authors. I know, right? At first i thought it would never be effective. However, so many newcomers are coming on the scene, it is paying off big. Nearly every wallet i have seen had at least 1 Million USD in it or more..... From a damn copy and paste switch. The worst part is, most people's security protection will not help them here, because the application does not look Malicious! All it is, is 3 lines of code changing the clipboard. Whats wrong with that? Well in this case, everything is. Please Please be on the look out for these. They make me so angry.. Other common ones are applications that try to pass as a update to , Bitcoin Duplicators (Ya...), Bitcoin Accelerators (I get this one, Noobs aren't getting why the TX's are fucking around), Fake Miners (If no one has heard of it, DONT USE IT), and Fake Wallets. I can go into these later if people are interested.
 
Anyways, I was looking at a sample today, and noticed this was one of the braver ones that scoop up the whole Wallet.Dat (Or similar) file, and kick it off to their servers. It does this for nearly 25 popular clients, even one called Armory which i thought was ironic.
 
This sample is hitting people through fake ad's to update their miners when visiting Crypto Sites, and more commonly, through email they are somehow getting for many exchange users. The emails claim either that they found your wallet publicly online! And that you should verify right away that it is actually yours. Its conveniently named "Wallet.dat .exe" with the spaces allowing the exe to hide in some email clients. When downloading and running, of course, you are infected. Other emails include free books on Crypto Currency that have a surprise for you inside! And Insider Information that you could use on a up coming pump and dump!
 
I loaded it into a IDA on a VM, and noticed that it wasn't sending the wallets to a domain, but rather a IP, and not only that, but what looked like a residential ISP IP. I allowed it to send up my fake wallets so i could get the scheme of the HTTP POST, and then started investigating the server. The guy receives loads of wallets a day, but he also runs a small botnet, proxy server, and password unhashing service on the same server. What was weird is i didn't see any templates, control panels, or mail for a web hosting company, which i normally see right away. I was starting to think this guy was actually dumb enough to use some server sitting at his house for this shit.
 
On further investigation of the client code talking to the server, i noticed he had a exploitable vulnerability in the way he uploaded files to the server. This allowed me to send up a payload with my wallet that later became my backdoor and reverse shell into his server. He was running a older kernel, so i was able to also exploit my way to root, and at this point i had full control over the server.
 
After further investigation, it was clear that indeed he IS running this out of his house. I somehow got lucky and out of 350 proxy servers, i managed to hop on his main node. Which he is a idiot anyways for accepting connections from anything but his proxies on this machine, or even using a home machine! Don't worry, i will be handing the needed information over to the feds for this little prick.
 
Now to my main point. It's obvious i must stay anonymous in this whole ordeal because, even though this dude is a POS, some people still might not be okay with what i did. And i also would like to keep my job haha. But seeing as i had full access, and this guy was dealing with BTC, this was a first for me. Most take overs i have done before, never had the actual wallets on the server. I really want to warn the victims he has FRESH wallets for ( IT COULD BE YOU! ), and also attempt to recover some BTC in the criminals wallets back to some, most likely worried sick, people.
 
I'm posting this today not only for the hope that if someone did notice Malware stole their coins, they can contact me and see if we can verify it was him, BUT ALSO in hopes that maybe any of you here would have any ideas on how i could go about finding these people, and then verifying its actually their BTC? I really can't think of any sure fire way accepting hoping people contact me and can match up the exact Transaction ID, Date, and Amount that was stolen from them. Please let me know your ideas.
 
I also want to finish this with a small list of FRESH VICTIMS that will most likely be getting hit very soon if they do not make a different wallet ASAP. I have hindered his processing further, but this doesn't help for already uploaded wallets. If these machine names match yours, PLEASE MAKE A NEW WALLET RIGHT AWAY: (Format is _.dat )
   
  • BitcoinQT_PC-4A095E27CB
  • BitcoinQT_KRK8HCPUDQP-PC
  • BitcoinQT_DESKTOP-MD6CE0T
  • BitcoinQT_EEW8HH-PC
  • BitcoinQT_JCNHJN8XRO0-PC
  • BitcoinQT_L1MKEWAMYWOT-PC
  • BitcoinQT_QBEY678-PC
  • BitcoinQT_DESKTOP-AJMCAK1
  • BitcoinQT_I3HOM1VJGV2Y-PC
  • BitcoinQT_DESKTOP-GKAN490
  • BitcoinQT_SMQYPJPO-PC
   
This is just a small list i could make tonight, i will hopefully be able to recover more and get more people switched to new wallets.
Thank you for your time.
submitted by censorship_notifier to noncensored_bitcoin [link] [comments]

12-23 11:03 - 'I'm attempting to return stolen bitcoin and warning soon to be victims' (self.Bitcoin) by /u/MrBeanCoin removed from /r/Bitcoin within 89-99min

'''
Hello!
My name is MrBeanCoin (Not a obvious throw away! Of course not!). I'm my professional life I am a Malware Analyst, Pen Tester, and Engineer. However when im not working my eyes have been glued to the BTC charts, kicking myself for spending my BTC back when times were rough. But enough about me, lets get to the point.
 
Since the rise in price and popularity of Crypto's, Malware Authors have been leaving Ransomware, Botnets, and Spam in droves to create very simple Bitcoin and Altcoin stealing Malware, in a attempt to make the most money quicker, and separate good people like yourself from your coins. Miners have also reached unbelievable heights (Surpassing even when BTC first came out), and they make sure not to use safe settings, and a lot have been causing hardware damage. The spike has been so large that this week, the GTX 1080 i have in my Cuckoo Server (Automated Malware Analysis Platform) burned out from the constant throttling up and down.
 
So obviously, with my job, i have been having to deal with these fuckers and their shitty coded applications a lot. Some go as far as ripping your wallets from your machine and uploading them to a C2 server, but the absolute most common way people are losing bitcoins by the THOUSANDS is by the most simplest application i have ever seen. It simply lays low on the machine, and when it detects a BTC Address on the clipboard, it replaces the address you copied, with the Malware Authors. I know, right? At first i thought it would never be effective. However, so many newcomers are coming on the scene, it is paying off big. Nearly every wallet i have seen had at least 1 Million USD in it or more..... From a damn copy and paste switch. The worst part is, most people's security protection will not help them here, because the application does not look Malicious! All it is, is 3 lines of code changing the clipboard. Whats wrong with that? Well in this case, everything is. Please Please be on the look out for these. They make me so angry.. Other common ones are applications that try to pass as a update to , Bitcoin Duplicators (Ya...), Bitcoin Accelerators (I get this one, Noobs aren't getting why the TX's are fucking around), Fake Miners (If no one has heard of it, DONT USE IT), and Fake Wallets. I can go into these later if people are interested.
 
Anyways, I was looking at a sample today, and noticed this was one of the braver ones that scoop up the whole Wallet.Dat (Or similar) file, and kick it off to their servers. It does this for nearly 25 popular clients, even one called Armory which i thought was ironic.
 
This sample is hitting people through fake ad's to update their miners when visiting Crypto Sites, and more commonly, through email they are somehow getting for many exchange users. The emails claim either that they found your wallet publicly online! And that you should verify right away that it is actually yours. Its conveniently named "Wallet.dat .exe" with the spaces allowing the exe to hide in some email clients. When downloading and running, of course, you are infected. Other emails include free books on Crypto Currency that have a surprise for you inside! And Insider Information that you could use on a up coming pump and dump!
 
I loaded it into a IDA on a VM, and noticed that it wasn't sending the wallets to a domain, but rather a IP, and not only that, but what looked like a residential ISP IP. I allowed it to send up my fake wallets so i could get the scheme of the HTTP POST, and then started investigating the server. The guy receives loads of wallets a day, but he also runs a small botnet, proxy server, and password unhashing service on the same server. What was weird is i didn't see any templates, control panels, or mail for a web hosting company, which i normally see right away. I was starting to think this guy was actually dumb enough to use some server sitting at his house for this shit.
 
On further investigation of the client code talking to the server, i noticed he had a exploitable vulnerability in the way he uploaded files to the server. This allowed me to send up a payload with my wallet that later became my backdoor and reverse shell into his server. He was running a older kernel, so i was able to also exploit my way to root, and at this point i had full control over the server.
 
After further investigation, it was clear that indeed he IS running this out of his house. I somehow got lucky and out of 350 proxy servers, i managed to hop on his main node. Which he is a idiot anyways for accepting connections from anything but his proxies on this machine, or even using a home machine! Don't worry, i will be handing the needed information over to the feds for this little prick.
 
Now to my main point. It's obvious i must stay anonymous in this whole ordeal because, even though this dude is a POS, some people still might not be okay with what i did. And i also would like to keep my job haha. But seeing as i had full access, and this guy was dealing with BTC, this was a first for me. Most take overs i have done before, never had the actual wallets on the server. I really want to warn the victims he has FRESH wallets for ( IT COULD BE YOU! ), and also attempt to recover some BTC in the criminals wallets back to some, most likely worried sick, people.
 
I'm posting this today not only for the hope that if someone did notice Malware stole their coins, they can contact me and see if we can verify it was him, BUT ALSO in hopes that maybe any of you here would have any ideas on how i could go about finding these people, and then verifying its actually their BTC? I really can't think of any sure fire way accepting hoping people contact me and can match up the exact Transaction ID, Date, and Amount that was stolen from them. Please let me know your ideas.
 
I also want to finish this with a small list of FRESH VICTIMS that will most likely be getting hit very soon if they do not make a different wallet ASAP. I have hindered his processing further, but this doesn't help for already uploaded wallets. If these machine names match yours, PLEASE MAKE A NEW WALLET RIGHT AWAY: (Format is _.dat )
   
  • BitcoinQT_PC-4A095E27CB
  • BitcoinQT_KRK8HCPUDQP-PC
  • BitcoinQT_DESKTOP-MD6CE0T
  • BitcoinQT_EEW8HH-PC
  • BitcoinQT_JCNHJN8XRO0-PC
  • BitcoinQT_L1MKEWAMYWOT-PC
  • BitcoinQT_QBEY678-PC
  • BitcoinQT_DESKTOP-AJMCAK1
  • BitcoinQT_I3HOM1VJGV2Y-PC
  • BitcoinQT_DESKTOP-GKAN490
  • BitcoinQT_SMQYPJPO-PC
   
This is just a small list i could make tonight, i will hopefully be able to recover more and get more people switched to new wallets.
Thank you for your time.
'''
I'm attempting to return stolen bitcoin and warning soon to be victims
Go1dfish undelete link
unreddit undelete link
Author: MrBeanCoin
submitted by removalbot to removalbot [link] [comments]

Blockchain summit report: Day 1 - "Enterprise cloud"

previous days
`
Event details
Today was day 1 of the 2 day "International Blockchain summit" presentations. On every seat was a little bag that had 3 books about the Blockchain! Unfortunately they were all in Chinese.
http://imgur.com/jmkRYVj http://imgur.com/g66KeRD
`
Presentations summary
Whereas DEVCON2 was all about development, and leveraging the network effects of leveraging other projects in the ecosystem, the presentations today were VERY high level talks.
There was a massive stark difference between "the old guard" in the Fintech space, and the disruptors that are shaking things up.
Take a look at the BOC (Bank of China) and ChinaLedger presentations. They talk about how Distributed computing is dangerous. ChinaLedger go on to say that they need the power to be able to go in and halt transactions, modify smart contracts on the fly, liquidate accounts when they need. While also saying that they will make sure they will do everything to help privacy and use encryption… which only the Government can unlock ("Golden keys"?). It was the most centralised "Blockchain" I have ever heard of.
On the flip side I was inspired by the forward thinking of the Consensys presentation, and their long term vision for where to drive the Ethereum platform. They are helping to create open tools and platforms that will be leveragable by a multitude of projects (as demonstrated with Ujo and BHP project "Rai stones").
http://imgur.com/AXHw1Df
After the Consensys presentation, my 2nd favourite presentation was by Wanxiang labs "10 years to build a city", talking about how they plan on taking some land and creating from scratch a smart city powered by the blockchain and electric vehicles. While the other old guard are squabbling about how it is going to impact their "business as usual" profits, there were the new projects out there envisioning and disrupting.
The BHP presentation was also pretty cool, a great implemenation of using Blockchain to improve a business process.
`
Presentations
New Finance: Technical & Legal rules - BoC He is from bank of China. Entire presentation was him being scared and trying to justify why current Blockchain tech is an unregulated wasteland, and why there needs to be regulation from banks and government.
For Fintech they think Blockchain will not be successful without proper regulations Blockchain finance - it is distributed. Storing all of the transactions will take a lot of storage space. What to do once the transaction rates exceed what can be processed. Thinks that public distributed transactions will not be more than a toy like with Bitcoin. For real FinTech they need something different for a high frequency. Thinks that decentralisation should not be the core feature of Blockchains (due to transaction limit). Thinks it should be decentralised, not distributed.
Should be done with private consortiums. Needs legal rules and technical rules. They think that self rulemaking currencies (Bitcoin) can not be regulated. So need to stop them, to prevent bad things like money laundering. This is showing the loopholes brought about by Bitcoin. So when using digital currencies, they need certifications and tracking.
"We need more regulations and rules to facilitate the healthy development of this space. Only with support of regulations can new technology take off".
Me: I totally disagree… (if not already apparent)
Blockchain futures & realities - CSDC
China Securities Depository and clearinghouse
He was much more open minded and forward looking. Is a pep talk for "things are going to change", how are we going to use these new things. He said that he recorded it into English that should be able to be downloaded, would be worth watching if you are into this space.
Summary: Genie is out of the bottle, we need to embrace this and think how we are going to put the requirements of securities ("real name transactions") in a decentralised way. And the registration and tracking of assets to real names.
People have ideals because they are not happy with reality. Due to this dissatisfaction, people are passionate about trying to make that dream a reality. Need to play by the rules, or the market will be chaos. So now we have facilities law, regulations, etc. This forms the framework of China economic. This is very different from Blockchain. This is at odds to the distributed systems. Seems like we are dissatisfied with this, so trying to reconcile these differences.
All securities transactions need to follow "real name" transactions, but want to do this in a decentralised manner. Market cap is 54 trillion (of something in China). GDP is over 70 million
They are researching Blockchain, but not just in the lab. Need to find potential applications and use cases for it. If we want to implement Blockchain technologies, we need to see what the hurdles will be, so we can get closer to the ideal. As BoC speaker said, the number of transactions per seconds is HUGE. Daily may reach 10s of millions at its peak. How are we going to handle this with a theoretical framework. Need to start from the reality of China. And the reality is it is a giant country with a huge population, which depends on the capital market. If you just implement within a lab it is okay. But if it is going to be put into the industry, then we need to work with the government. We can't just get rid of the government, it is impossible (REVOLUTION!!). So need to focus on key senarios to tackle, as you can't just apply Blockchain everywhere simultaneously. Or all your efforts will fruitless. How to complement it initially, not replace it.
Ten years efforts to build a city (Wanxiang Labs)
Me: I reallly liked this presentation. I've been keeping notes for months around building this type of innovative city in Australia. I plan on rewatching this one again later.
Going to build a city in 10 years. An energy gathering city in HangZhou 10KM2. Their US company is starting to build new energy vehicle. 900m RMB? 90k people. Deploy the city into the cloud. Intelligent life, traffic & services. Everything will be connected. IoT, Internet, smart living, smart transport. Once this is successful, they plan on launching it across the world. Will publish their learnings. Launching incubators and accelerators. Their own cloud Blockchain as a Service. Many scenarios in this smart city that could utilise Blockchain. Distribution for Solar power. ID & Vehicle registration. Intelligent community services. Can promote a sharing economy throughout the community. Partnering with Microsoft, IBM, Consensys, Ethereum foundation, WeBank, AliCloud
Vitalik Buterin keynote
Talking of the progress China has made in Blockchain innovation in such a short period of time. He visited China 3 years ago and visited a number of Bitcoin companies and was impressed on the scale of what China had, much more than what was happening in USA. But all the focus was just on cryptocurrencies, not Blockchain technologies, Just mining. 2nd time, he saw some kind of experimentation happening with interesting things (like coloured coins?) 3rd time saw more interest in Blockchains. 4th? time, he did a hackathon with Wanxiang labs (event sponsor), and there were ~30 projects. The growth since then has been rapidly growing. The scale of projects we couldn't have imagined 3 years ago. Was just theoretical, now a lot of ideas are almost reality. e.g. Self-sovereign identity, instant settlement.
Hyperledger
https://www.hyperledger.org/ Goals. Build an opensource dev focused community of communities to build a hyperledger based solution. Create a family of "etnerprise grade" open source blockchain framework, platform & libraries.
Because it is an enterprise opensource project, they need to track contributions, patent details, etc. Is part of the Linux Foundation, which has 16 years of providing governance stucture support for major open source projects. 80 project partners. IBM, Intel, Accenture, JP Morgan, Airbus, ANZ bank, Cisco, etc. 20 of the 80 project partners, are based in China. Apache license v2.
A world or many chains. There will not be only one blockchain. There will be many public chians and millions of private chains. Each may use different consensus mechanisms.
Major projects are: Fabric: Developed by IBM. PBFT, moving to Raft and other pluggable consensus mechanisms. Written in Go. Sawtooth Lake: Proof of Elapsed Time. Runs on secure enclaves. Written in Python. Hyperledger explorer: GUI for navigating Fabric & swatooth lake. Fabric-py SDK. (Java proposed later).
Future: Smart contract engines. Portable identities. Will never see a "HyperCoin". It is about making Hyperledger a standard, and a governance group.
IBM keynote - IBM Blockchain & Hyperledger
Today if you want to do something in your business on Blockchain it is difficult. Hard to scale, issues with privacy. No Enterprise support. Need tools to write tests for smart contracts. Need good solution patterns. Difficult to scale up, especially around transaction rates.
Built Fabric to support "serious business" Permissioned blockchains can't scale. Every node shouldn't execute every transaction. The 2 peers that are interacting are the only ones that should execute. IBM has implemented this internally to resolve invoice disputes with their suppliers.
IBM
All the slides were in Chinese. Difficult to follow unfortuantely. The (original) Silk Road was important for trade. Blockchain may be just as important for trade in the future People are debating the need of distributed systems being an important thing of Blockchains, is it really necessiary? Blockchain should instead be focused on unblocking instead. IBM will provide an IBM certified docker container. IBM Blockchain. http://www-31.ibm.com/ibm/cn/blockchain/index.html Has a concept of a "shadow chain"?
Blockchain Platform @ Microsoft
At Devcon1 Microsoft announced Blockchain as a Service. Rolled out DevTest Labs to allow you to spin up public, private, permissioned, and consotrium blockchians quickly. Provisoin with 1 click. Mix & match from best available blockchain tech.
Bletchley: Open infrastructure, Enterprise capabilities. Microsoft is not building their own Blockchain.
Blockchain has some missing parts (identity, privacy, key management lifecycle, tools). Asked our partners what are the missing parts. A database in itself isn't an application.
(re)Announcing: Bletchley v1. 2 parts. Distributed infrastructure layer (Blockapps, R3, bitpay, parity, Eris). There isn't going to be 1 Blockchain to rule them all, so allow you to leverage any of them. Lots of customers were taking a long time trying to spin up private consortiums, and trying to secure them correctly. Used to take 3 weeks, now down to 8 questions and 5 minutes. Spins up a private Ethereum consortium. 4-100s of nodes.
Distributed middleware "fabric" layer. Tools that can work across many blockchain technologies. Cryptlets are a way of doing offchain processing. Receive market data based on an event (market price daily closing, CRM event). Need to have trusted execution of the logic, to attest that it was not tampered with. Secure IP protected algorithms. Scale an algorithm for max performance by running it off blockchain in a secure & attested way in the cloud. Oracles may be malicious, or they may be intercepted during transmission. Cryptlets run on a secure host with a secure communication channel in a trust envelope. Marketplace for publishing the cryptlets into a market for others to consume. Azure cloud is twice the size of Amazon & Google COMBINED.
Bletchley Cryptlet Fabric. Supports Ethereum, will support more Blockchains. It is middleware that will support many. Secure execution on demand. Standard way of publishing and accessing external resources.
BaaS roadmap. DevTest labs, will continue to onboard more. Bletchley v1. Kinakuta to help improve security. Bletchley SDK
Longer range implications of Ethereum & other decentralising technologies (Consensys) LOVED this presentation.
Simplest view: Next gen database. Blockchain based, maximal replication, Prevents rogue actors Force for universal disintermediation, will distrupt every industry. Previously it was mostly just Bitcoin. Future projects were "BitCoin 2.0", instead of "Blockchain 2.0". So Ethereum project built the most powerful and capable Blockchain platform, both public (permisionless) and private (permissioned) Deeply secure, non-repudiable shared source of truth. Dapp is a set of smart contracts. And a user interface to interact with it. Was important to get an initial version of Ethereum out into the hands of devs, to start thinking how to start building decentralised applications. Ethereum has a vision for scalability, which includes sharding and state channels. Privacy, state channels is one option. Zcash/zk-Snarks is another way.
Currently building out an ecosystem of decentralised applications. Building core components: Identity/persona (uPort, metamask). Wallet (uPort wallet). Registries (Regis, ENS). Token Factory. Do private enterprise Blockchains make sense? Yes, large entities can have a complex internal mix of business units, having a shared source of truth can help. If enterprises have their own private consortium Blockchains, will be a harder target to infiltrate and modify databases. Business processes emboided as state transition graphs.
If you plan on building your own tools or technology on top of Blockchain tech (public or private), build it on Ethereum so it can be reused in many different places by other entities running their private chains Developed "Balance" for real time compliance, accounting auditing and monitoring. Real time dashboard for companies & regulators. Organisations using certified software wil not be able to break or bend any financial accounting rules.
The Blockchain will last for years or decades giving a persistent database. Gives a chance to do persistent portable identity. uPort self-sovereign identity.
Blockapps Announcement
Is Ethereum for Enterprise. Partnered with Microsoft to announce Blockchain as a Service (BaaS). Over 1k projects have used it, over 300 customers. Being released in Azure China datacentre (mooncake), and other Chinese clouds : Alibaba cloud, tencent cloud, Wancloud. Initial China projects: Minsheng insurance, Wanxiang smart city, Qianhai smart city, Shanghai smart city. China is going to be the country leading the world in Blockchain projects.
The Rise of Blockchain Consortia: Uniting the Banking World
One of the largest banks in Spain. Banks are just a ledger (a very large ledger). Each bank has its own ledger. They don't trust each others. Which is why you need clearing houses and things like this. What if there was a shared ledger trusted by all banks. "It's not about the coin, its about the ledger.
`
New development of ChinaLedger: Forging a powerful tool for Chinese capital market in the FinTech era
Was literally the most centralised blockchain I have ever heard of. Please excuse me as I rant inline.
ChinaLedger is a consortium. 11 founders established it. Chinese financial institutions and Wanxiang labs. "we created our own Blockchain and tools". Will come up with their own custom software and implementation. Will create a whitepaper and create reference architecture. Partners will use the network to do transactions. Need facilities to be able to freeze or take over acounts, and get access to all data. A need to be able to halt or freeze a transaction or smart contract. A need to be able to halt or freeze a transaction or smart contract. and the facility to liquidate an account or smart conract or manually change the state of a smart contract We need to be able to stop the trading of certain stocks. Let regulators control things. Will be fully in control of the gas. Wants to support 100k/s and 1 ms latency.
Then ironically says tries to say they are going to put privacy into this. "Everything will be encrypted and private. Except that CCP & regulators who will have ability to read everything". I'm SURE that won't be abused…
http://imgur.com/Qt4qh3O You keep using that word... Blockchain, distributed ledger, privacy, encryption
Re-imagining Global Payments (For business)
Banks make a LOT of money from bank wires. So they have no incentive to come up with anything better. The person sending the money needs to give 26 pieces of information. Don't know when you'll get the money, what the rate will be. About $20 to send, $20 to receive, plus lose a few percentage through the conversion.
Their solution (for business payments). Register for an account, can use online. No fees. Transparent FX rate. Can track the payment. Uses Bitcoin in the middle. Before international calls used to call many $s per minute. Now with VoIP (Skype) you can do it for cents. Same thing will happen to international money transfers.
Enabling Global P2P Cash Transfers with Abra (For consumer)
https://www.goabra.com/ http://www.coindesk.com/abra-remittance-app-us-launch/
Nowadays you can send an IM to anyone else in the world instantly for free. Why can't you do the same thing with money? Can do it locally in some domestic markets, like paytm (india, WeChat pay (China), mpesa (Africa). But not for cross border transactions. iOS & Android. Real digital cash wallet. Send & receive globally. No FX risk. Add cash via bank or in person. As private as paper cash. Abra tellers earn $$ (as a percentage fee). The wallet is stored locally on the phone. So you "physically" control it. (need to back up your private key). Use an Abra teller (someone else using the app) to exchange buy/sell cash for digital cash. Anyone can be a teller. Tellers charge a fee. Teller & user rate each other. When 2 people send money each other via Abra, happens instantly, . No FX volatility.
Awaking the Sleeping Giant: The Natural Resource Industry and the Blockchain
Note: Hispresentation was in English, but I thought it was extremely considerate that he had his slides translated into Chinese as well. Every slide had simultaneous English & Chinese descriptions so that the attendees using the live translation headsets could follow along easier. If I ever present in another country again, I'll try and plan ahead like he did. Was very thoughtful.
Why is BHP interested in the Blockchain? They are the largest mining company in the world (natural resources mining, not Bitcoin mining. Hehe) They are a global distributed organisation. So a distributed Blockchain
Project Rai Stones. Sample tracking of geological samples. They are highly valuable resources. Some of the wells cost $100M, and you only get 1 chance to take the sample. They currently only track the samples manually through emails & spreadsheets. They are working with Consensys & Blockapps. Runs on Ethereum & IPFS, on top of Microsoft Azure. 1 node at BHP, 1 at their collaborator, 1 at their regulator. 3 roles in the business flow, BHP out in the field, the analysis team, and BHP corp. They create/register a smart contract on the network for each sample. When the person collects the sample, they go to the dashboard, click the checkboxes to say they acquired, that updates the smart contract. They ship it off, so they put in the details of which analysis office it is being sent to, updates state from collected to shipped. Analysis team can log in, see what samples are in transit to them to be analysed. They receive it, give it a unique Id based on their internal process. They get trusted tracking of samples, and real time updates.
What if they could automatically operate machines, they could help avoid bad combinations of machines operating at the same time. Like a crane operating on an oil rig, when a helicopter is coming in. Disable a piece of machinery if it is past its allowed usage before routine preventative maintenance. Disabled until it is tested, and certified as okay on the Blockchain. Stop unqualified people from using a tool or vehicle.
Ore gets mined and put onto shipping freighters. Need to track Provenance, custodians, entire supply chain.
Need to give regulatory data to the regulators in each country the operate in. All the mines in the industry need to submit this public data to gov, it all gets aggregated, and disseminated. But it costs HEAPS to do this. What if they built a consortium chain. They can all publish the public data, ready to be analysed instantly by peers. Could make the entire industry more effienct and transparent by making the consortium not just for the 1 country, but a public one. Give a global transparent view of the entire industry. Would help drop costs of compliance.
They started on Ethereum Mainnet & Testnet. Now they are seeing the emergence of many private chains. They will see the bridging between chains. Seen that Ethereum plans on sharding (many chains). Forsees that there will be a global mesh of these Public & Private chains all supporting each other.
Cotricity – “a prosumer to business”- virtual energy market on the Ethereum blockchain (Consensys)
https://co-tricity.com Energy meets Blockchain Joint venture between Consensys & an energy company in Germany. Energy sector is changing rapidly. Prosumer is someone with generative capacity (eg. Solar panels & battery storage). Normal smart meter collects usage about production & consumption. Tracked on Ethereum. Matches up Prosumers to local community things like Schools. The local environmental and economic benefits of keeping it in the local community.
Mechanism design, "reverse game theory". Goal is to effectiveise the energy market and reduce costs. Means creating incentives such that the optimal strategy for every participant results in the realisation of this goal. e.g. Help to smooth out the peak in the morning, give a small reward for not using energy in the morning
submitted by DavidBurela to ethereum [link] [comments]

Bitcoin Core 0.10.0 released | Wladimir | Feb 16 2015

Wladimir on Feb 16 2015:
Bitcoin Core version 0.10.0 is now available from:
https://bitcoin.org/bin/0.10.0/
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
The whole distribution is also available as torrent:
https://bitcoin.org/bin/0.10.0/bitcoin-0.10.0.torrent
magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn;=0.10.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrading warning
Because release 0.10.0 makes use of headers-first synchronization and parallel
block download (see further), the block files and databases are not
backwards-compatible with older versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.
Notable changes

Faster synchronization
Bitcoin Core now uses 'headers-first synchronization'. This means that we first
ask peers for block headers (a total of 27 megabytes, as of December 2014) and
validate those. In a second stage, when the headers have been discovered, we
download the blocks. However, as we already know about the whole chain in
advance, the blocks can be downloaded in parallel from all available peers.
In practice, this means a much faster and more robust synchronization. On
recent hardware with a decent network link, it can be as little as 3 hours
for an initial full synchronization. You may notice a slower progress in the
very first few minutes, when headers are still being fetched and verified, but
it should gain speed afterwards.
A few RPCs were added/updated as a result of this:
  • getblockchaininfo now returns the number of validated headers in addition to
the number of validated blocks.
  • getpeerinfo lists both the number of blocks and headers we know we have in
common with each peer. While synchronizing, the heights of the blocks that we
have requested from peers (but haven't received yet) are also listed as
'inflight'.
  • A new RPC getchaintips lists all known branches of the block chain,
including those we only have headers for.
Transaction fee changes
This release automatically estimates how high a transaction fee (or how
high a priority) transactions require to be confirmed quickly. The default
settings will create transactions that confirm quickly; see the new
'txconfirmtarget' setting to control the tradeoff between fees and
confirmation times. Fees are added by default unless the 'sendfreetransactions'
setting is enabled.
Prior releases used hard-coded fees (and priorities), and would
sometimes create transactions that took a very long time to confirm.
Statistics used to estimate fees and priorities are saved in the
data directory in the fee_estimates.dat file just before
program shutdown, and are read in at startup.
New command line options for transaction fee changes:
  • -txconfirmtarget=n : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting
is over-ridden by the -paytxfee option.
  • -sendfreetransactions : Send transactions as zero-fee transactions if possible
(default: 0)
New RPC commands for fee estimation:
  • estimatefee nblocks : Returns approximate fee-per-1,000-bytes needed for
a transaction to begin confirmation within nblocks. Returns -1 if not enough
transactions have been observed to compute a good estimate.
  • estimatepriority nblocks : Returns approximate priority needed for
a zero-fee transaction to begin confirmation within nblocks. Returns -1 if not
enough free transactions have been observed to compute a good
estimate.
RPC access control changes
Subnet matching for the purpose of access control is now done
by matching the binary network address, instead of with string wildcard matching.
For the user this means that -rpcallowip takes a subnet specification, which can be
  • a single IP address (e.g. 1.2.3.4 or fe80::0012:3456:789a:bcde)
  • a network/CIDR (e.g. 1.2.3.0/24 or fe80::0000/64)
  • a network/netmask (e.g. 1.2.3.4/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address
matches one of them.
For example:
| 0.9.x and before | 0.10.x |
|--------------------------------------------|---------------------------------------|
| -rpcallowip=192.168.1.1 | -rpcallowip=192.168.1.1 (unchanged) |
| -rpcallowip=192.168.1.* | -rpcallowip=192.168.1.0/24 |
| -rpcallowip=192.168.* | -rpcallowip=192.168.0.0/16 |
| -rpcallowip=* (dangerous!) | -rpcallowip=::/0 (still dangerous!) |
Using wildcards will result in the rule being rejected with the following error in debug.log:
 Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). 
REST interface
A new HTTP API is exposed when running with the -rest flag, which allows
unauthenticated access to public node data.
It is served on the same port as RPC, but does not need a password, and uses
plain HTTP instead of JSON-RPC.
Assuming a local RPC server running on port 8332, it is possible to request:
In every case, EXT can be bin (for raw binary data), hex (for hex-encoded
binary) or json.
For more details, see the doc/REST-interface.md document in the repository.
RPC Server "Warm-Up" Mode
The RPC server is started earlier now, before most of the expensive
intialisations like loading the block index. It is available now almost
immediately after starting the process. However, until all initialisations
are done, it always returns an immediate error with code -28 to all calls.
This new behaviour can be useful for clients to know that a server is already
started and will be available soon (for instance, so that they do not
have to start it themselves).
Improved signing security
For 0.10 the security of signing against unusual attacks has been
improved by making the signatures constant time and deterministic.
This change is a result of switching signing to use libsecp256k1
instead of OpenSSL. Libsecp256k1 is a cryptographic library
optimized for the curve Bitcoin uses which was created by Bitcoin
Core developer Pieter Wuille.
There exist attacks[1] against most ECC implementations where an
attacker on shared virtual machine hardware could extract a private
key if they could cause a target to sign using the same key hundreds
of times. While using shared hosts and reusing keys are inadvisable
for other reasons, it's a better practice to avoid the exposure.
OpenSSL has code in their source repository for derandomization
and reduction in timing leaks that we've eagerly wanted to use for a
long time, but this functionality has still not made its
way into a released version of OpenSSL. Libsecp256k1 achieves
significantly stronger protection: As far as we're aware this is
the only deployed implementation of constant time signing for
the curve Bitcoin uses and we have reason to believe that
libsecp256k1 is better tested and more thoroughly reviewed
than the implementation in OpenSSL.
[1] https://eprint.iacr.org/2014/161.pdf
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know
all addresses (or scripts), even without the private keys.
This can be used to track payments without needing the private keys online on a
possibly vulnerable system. In addition, it can help for (manual) construction
of multisig transactions where you are only one of the signers.
One new RPC, importaddress, is added which functions similarly to
importprivkey, but instead takes an address or script (in hexadecimal) as
argument. After using it, outputs credited to this address or script are
considered to be received, and transactions consuming these outputs will be
considered to be sent.
The following RPCs have optional support for watch-only:
getbalance, listreceivedbyaddress, listreceivedbyaccount,
listtransactions, listaccounts, listsinceblock, gettransaction. See the
RPC documentation for those methods for more information.
Compared to using getrawtransaction, this mechanism does not require
-txindex, scales better, integrates better with the wallet, and is compatible
with future block chain pruning functionality. It does mean that all relevant
addresses need to added to the wallet before the payment, though.
Consensus library
Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library.
The purpose of this library is to make the verification functionality that is
critical to Bitcoin's consensus available to other applications, e.g. to language
bindings such as [python-bitcoinlib](https://pypi.python.org/pypi/python-bitcoinlib) or
alternative node implementations.
This library is called libbitcoinconsensus.so (or, .dll for Windows).
Its interface is defined in the C header [bitcoinconsensus.h](https://github.com/bitcoin/bitcoin/blob/0.10/src/script/bitcoinconsensus.h).
In its initial version the API includes two functions:
  • bitcoinconsensus_verify_script verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
  • bitcoinconsensus_version returns the API version, currently at an experimental 0
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface
for existing methods should remain stable.
Standard script rules relaxed for P2SH addresses
The IsStandard() rules have been almost completely removed for P2SH
redemption scripts, allowing applications to make use of any valid
script type, such as "n-of-m OR y", hash-locked oracle addresses, etc.
While the Bitcoin protocol has always supported these types of script,
actually using them on mainnet has been previously inconvenient as
standard Bitcoin Core nodes wouldn't relay them to miners, nor would
most miners include them in blocks they mined.
bitcoin-tx
It has been observed that many of the RPC functions offered by bitcoind are
"pure functions", and operate independently of the bitcoind wallet. This
included many of the RPC "raw transaction" API functions, such as
createrawtransaction.
bitcoin-tx is a newly introduced command line utility designed to enable easy
manipulation of bitcoin transactions. A summary of its operation may be
obtained via "bitcoin-tx --help" Transactions may be created or signed in a
manner similar to the RPC raw tx API. Transactions may be updated, deleting
inputs or outputs, or appending new inputs and outputs. Custom scripts may be
easily composed using a simple text notation, borrowed from the bitcoin test
suite.
This tool may be used for experimenting with new transaction types, signing
multi-party transactions, and many other uses. Long term, the goal is to
deprecate and remove "pure function" RPC API calls, as those do not require a
server round-trip to execute.
Other utilities "bitcoin-key" and "bitcoin-script" have been proposed, making
key and script operations easily accessible via command line.
Mining and relay policy enhancements
Bitcoin Core's block templates are now for version 3 blocks only, and any mining
software relying on its getblocktemplate must be updated in parallel to use
libblkmaker either version 0.4.2 or any version from 0.5.1 onward.
If you are solo mining, this will affect you the moment you upgrade Bitcoin
Core, which must be done prior to BIP66 achieving its 951/1001 status.
If you are mining with the stratum mining protocol: this does not affect you.
If you are mining with the getblocktemplate protocol to a pool: this will affect
you at the pool operator's discretion, which must be no later than BIP66
achieving its 951/1001 status.
The prioritisetransaction RPC method has been added to enable miners to
manipulate the priority of transactions on an individual basis.
Bitcoin Core now supports BIP 22 long polling, so mining software can be
notified immediately of new templates rather than having to poll periodically.
Support for BIP 23 block proposals is now available in Bitcoin Core's
getblocktemplate method. This enables miners to check the basic validity of
their next block before expending work on it, reducing risks of accidental
hardforks or mining invalid blocks.
Two new options to control mining policy:
  • -datacarrier=0/1 : Relay and mine "data carrier" (OP_RETURN) transactions
if this is 1.
  • -datacarriersize=n : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs.
The relay policy has changed to more properly implement the desired behavior of not
relaying free (or very low fee) transactions unless they have a priority above the
AllowFreeThreshold(), in which case they are relayed subject to the rate limiter.
BIP 66: strict DER encoding for signatures
Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new
consensus rule, which prohibits non-DER signatures. Such transactions have been
non-standard since Bitcoin v0.8.0 (released in February 2013), but were
technically still permitted inside blocks.
This change breaks the dependency on OpenSSL's signature parsing, and is
required if implementations would want to remove all of OpenSSL from the
consensus code.
The same miner-voting mechanism as in BIP 34 is used: when 751 out of a
sequence of 1001 blocks have version number 3 or higher, the new consensus
rule becomes active for those blocks. When 951 out of a sequence of 1001
blocks have version number 3 or higher, it becomes mandatory for all blocks.
Backward compatibility with current mining software is NOT provided, thus miners
should read the first paragraph of "Mining and relay policy enhancements" above.
0.10.0 Change log

Detailed release notes follow. This overview includes changes that affect external
behavior, not code moves, refactors or string updates.
RPC:
  • f923c07 Support IPv6 lookup in bitcoin-cli even when IPv6 only bound on localhost
  • b641c9c Fix addnode "onetry": Connect with OpenNetworkConnection
  • 171ca77 estimatefee / estimatepriority RPC methods
  • b750cf1 Remove cli functionality from bitcoind
  • f6984e8 Add "chain" to getmininginfo, improve help in getblockchaininfo
  • 99ddc6c Add nLocalServices info to RPC getinfo
  • cf0c47b Remove getwork() RPC call
  • 2a72d45 prioritisetransaction
  • e44fea5 Add an option -datacarrier to allow users to disable relaying/mining data carrier transactions
  • 2ec5a3d Prevent easy RPC memory exhaustion attack
  • d4640d7 Added argument to getbalance to include watchonly addresses and fixed errors in balance calculation
  • 83f3543 Added argument to listaccounts to include watchonly addresses
  • 952877e Showing 'involvesWatchonly' property for transactions returned by 'listtransactions' and 'listsinceblock'. It is only appended when the transaction involves a watchonly address
  • d7d5d23 Added argument to listtransactions and listsinceblock to include watchonly addresses
  • f87ba3d added includeWatchonly argument to 'gettransaction' because it affects balance calculation
  • 0fa2f88 added includedWatchonly argument to listreceivedbyaddress/...account
  • 6c37f7f getrawchangeaddress: fail when keypool exhausted and wallet locked
  • ff6a7af getblocktemplate: longpolling support
  • c4a321f Add peerid to getpeerinfo to allow correlation with the logs
  • 1b4568c Add vout to ListTransactions output
  • b33bd7a Implement "getchaintips" RPC command to monitor blockchain forks
  • 733177e Remove size limit in RPC client, keep it in server
  • 6b5b7cb Categorize rpc help overview
  • 6f2c26a Closely track mempool byte total. Add "getmempoolinfo" RPC
  • aa82795 Add detailed network info to getnetworkinfo RPC
  • 01094bd Don't reveal whether password is <20 or >20 characters in RPC
  • 57153d4 rpc: Compute number of confirmations of a block from block height
  • ff36cbe getnetworkinfo: export local node's client sub-version string
  • d14d7de SanitizeString: allow '(' and ')'
  • 31d6390 Fixed setaccount accepting foreign address
  • b5ec5fe update getnetworkinfo help with subversion
  • ad6e601 RPC additions after headers-first
  • 33dfbf5 rpc: Fix leveldb iterator leak, and flush before gettxoutsetinfo
  • 2aa6329 Enable customising node policy for datacarrier data size with a -datacarriersize option
  • f877aaa submitblock: Use a temporary CValidationState to determine accurately the outcome of ProcessBlock
  • e69a587 submitblock: Support for returning specific rejection reasons
  • af82884 Add "warmup mode" for RPC server
  • e2655e0 Add unauthenticated HTTP REST interface to public blockchain data
  • 683dc40 Disable SSLv3 (in favor of TLS) for the RPC client and server
  • 44b4c0d signrawtransaction: validate private key
  • 9765a50 Implement BIP 23 Block Proposal
  • f9de17e Add warning comment to getinfo
Command-line options:
  • ee21912 Use netmasks instead of wildcards for IP address matching
  • deb3572 Add -rpcbind option to allow binding RPC port on a specific interface
  • 96b733e Add -version option to get just the version
  • 1569353 Add -stopafterblockimport option
  • 77cbd46 Let -zapwallettxes recover transaction meta data
  • 1c750db remove -tor compatibility code (only allow -onion)
  • 4aaa017 rework help messages for fee-related options
  • 4278b1d Clarify error message when invalid -rpcallowip
  • 6b407e4 -datadir is now allowed in config files
  • bdd5b58 Add option -sysperms to disable 077 umask (create new files with system default umask)
  • cbe39a3 Add "bitcoin-tx" command line utility and supporting modules
  • dbca89b Trigger -alertnotify if network is upgrading without you
  • ad96e7c Make -reindex cope with out-of-order blocks
  • 16d5194 Skip reindexed blocks individually
  • ec01243 --tracerpc option for regression tests
  • f654f00 Change -genproclimit default to 1
  • 3c77714 Make -proxy set all network types, avoiding a connect leak
  • 57be955 Remove -printblock, -printblocktree, and -printblockindex
  • ad3d208 remove -maxorphanblocks config parameter since it is no longer functional
Block and transaction handling:
  • 7a0e84d ProcessGetData(): abort if a block file is missing from disk
  • 8c93bf4 LoadBlockIndexDB(): Require block db reindex if any blk*.dat files are missing
  • 77339e5 Get rid of the static chainMostWork (optimization)
  • 4e0eed8 Allow ActivateBestChain to release its lock on cs_main
  • 18e7216 Push cs_mains down in ProcessBlock
  • fa126ef Avoid undefined behavior using CFlatData in CScript serialization
  • 7f3b4e9 Relax IsStandard rules for pay-to-script-hash transactions
  • c9a0918 Add a skiplist to the CBlockIndex structure
  • bc42503 Use unordered_map for CCoinsViewCache with salted hash (optimization)
  • d4d3fbd Do not flush the cache after every block outside of IBD (optimization)
  • ad08d0b Bugfix: make CCoinsViewMemPool support pruned entries in underlying cache
  • 5734d4d Only remove actualy failed blocks from setBlockIndexValid
  • d70bc52 Rework block processing benchmark code
  • 714a3e6 Only keep setBlockIndexValid entries that are possible improvements
  • ea100c7 Reduce maximum coinscache size during verification (reduce memory usage)
  • 4fad8e6 Reject transactions with excessive numbers of sigops
  • b0875eb Allow BatchWrite to destroy its input, reducing copying (optimization)
  • 92bb6f2 Bypass reloading blocks from disk (optimization)
  • 2e28031 Perform CVerifyDB on pcoinsdbview instead of pcoinsTip (reduce memory usage)
  • ab15b2e Avoid copying undo data (optimization)
  • 341735e Headers-first synchronization
  • afc32c5 Fix rebuild-chainstate feature and improve its performance
  • e11b2ce Fix large reorgs
  • ed6d1a2 Keep information about all block files in memory
  • a48f2d6 Abstract context-dependent block checking from acceptance
  • 7e615f5 Fixed mempool sync after sending a transaction
  • 51ce901 Improve chainstate/blockindex disk writing policy
  • a206950 Introduce separate flushing modes
  • 9ec75c5 Add a locking mechanism to IsInitialBlockDownload to ensure it never goes from false to true
  • 868d041 Remove coinbase-dependant transactions during reorg
  • 723d12c Remove txn which are invalidated by coinbase maturity during reorg
  • 0cb8763 Check against MANDATORY flags prior to accepting to mempool
  • 8446262 Reject headers that build on an invalid parent
  • 008138c Bugfix: only track UTXO modification after lookup
P2P protocol and network code:
  • f80cffa Do not trigger a DoS ban if SCRIPT_VERIFY_NULLDUMMY fails
  • c30329a Add testnet DNS seed of Alex Kotenko
  • 45a4baf Add testnet DNS seed of Andreas Schildbach
  • f1920e8 Ping automatically every 2 minutes (unconditionally)
  • 806fd19 Allocate receive buffers in on the fly
  • 6ecf3ed Display unknown commands received
  • aa81564 Track peers' available blocks
  • caf6150 Use async name resolving to improve net thread responsiveness
  • 9f4da19 Use pong receive time rather than processing time
  • 0127a9b remove SOCKS4 support from core and GUI, use SOCKS5
  • 40f5cb8 Send rejects and apply DoS scoring for errors in direct block validation
  • dc942e6 Introduce whitelisted peers
  • c994d2e prevent SOCKET leak in BindListenPort()
  • a60120e Add built-in seeds for .onion
  • 60dc8e4 Allow -onlynet=onion to be used
  • 3a56de7 addrman: Do not propagate obviously poor addresses onto the network
  • 6050ab6 netbase: Make SOCKS5 negotiation interruptible
  • 604ee2a Remove tx from AlreadyAskedFor list once we receive it, not when we process it
  • efad808 Avoid reject message feedback loops
  • 71697f9 Separate protocol versioning from clientversion
  • 20a5f61 Don't relay alerts to peers before version negotiation
  • b4ee0bd Introduce preferred download peers
  • 845c86d Do not use third party services for IP detection
  • 12a49ca Limit the number of new addressses to accumulate
  • 35e408f Regard connection failures as attempt for addrman
  • a3a7317 Introduce 10 minute block download timeout
  • 3022e7d Require sufficent priority for relay of free transactions
  • 58fda4d Update seed IPs, based on bitcoin.sipa.be crawler data
  • 18021d0 Remove bitnodes.io from dnsseeds.
Validation:
  • 6fd7ef2 Also switch the (unused) verification code to low-s instead of even-s
  • 584a358 Do merkle root and txid duplicates check simultaneously
  • 217a5c9 When transaction outputs exceed inputs, show the offending amounts so as to aid debugging
  • f74fc9b Print input index when signature validation fails, to aid debugging
  • 6fd59ee script.h: set_vch() should shift a >32 bit value
  • d752ba8 Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) (test only)
  • 698c6ab Add SCRIPT_VERIFY_MINIMALDATA (BIP62 rules 3 and 4) (test only)
  • ab9edbd script: create sane error return codes for script validation and remove logging
  • 219a147 script: check ScriptError values in script tests
  • 0391423 Discourage NOPs reserved for soft-fork upgrades
  • 98b135f Make STRICTENC invalid pubkeys fail the script rather than the opcode
  • 307f7d4 Report script evaluation failures in log and reject messages
  • ace39db consensus: guard against openssl's new strict DER checks
  • 12b7c44 Improve robustness of DER recoding code
  • 76ce5c8 fail immediately on an empty signature
Build system:
  • f25e3ad Fix build in OS X 10.9
  • 65e8ba4 build: Switch to non-recursive make
  • 460b32d build: fix broken boost chrono check on some platforms
  • 9ce0774 build: Fix windows configure when using --with-qt-libdir
  • ea96475 build: Add mention of --disable-wallet to bdb48 error messages
  • 1dec09b depends: add shared dependency builder
  • c101c76 build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix
  • e432a5f build: add option for reducing exports (v2)
  • 6134b43 Fixing condition 'sabotaging' MSVC build
  • af0bd5e osx: fix signing to make Gatekeeper happy (again)
  • a7d1f03 build: fix dynamic boost check when --with-boost= is used
  • d5fd094 build: fix qt test build when libprotobuf is in a non-standard path
  • 2cf5f16 Add libbitcoinconsensus library
  • 914868a build: add a deterministic dmg signer
  • 2d375fe depends: bump openssl to 1.0.1k
  • b7a4ecc Build: Only check for boost when building code that requires it
Wallet:
  • b33d1f5 Use fee/priority estimates in wallet CreateTransaction
  • 4b7b1bb Sanity checks for estimates
  • c898846 Add support for watch-only addresses
  • d5087d1 Use script matching rather than destination matching for watch-only
  • d88af56 Fee fixes
  • a35b55b Dont run full check every time we decrypt wallet
  • 3a7c348 Fix make_change to not create half-satoshis
  • f606bb9 fix a possible memory leak in CWalletDB::Recover
  • 870da77 fix possible memory leaks in CWallet::EncryptWallet
  • ccca27a Watch-only fixes
  • 9b1627d [Wallet] Reduce minTxFee for transaction creation to 1000 satoshis
  • a53fd41 Deterministic signing
  • 15ad0b5 Apply AreSane() checks to the fees from the network
  • 11855c1 Enforce minRelayTxFee on wallet created tx and add a maxtxfee option
GUI:
  • c21c74b osx: Fix missing dock menu with qt5
  • b90711c Fix Transaction details shows wrong To:
  • 516053c Make links in 'About Bitcoin Core' clickable
  • bdc83e8 Ensure payment request network matches client network
  • 65f78a1 Add GUI view of peer information
  • 06a91d9 VerifyDB progress reporting
  • fe6bff2 Add BerkeleyDB version info to RPCConsole
  • b917555 PeerTableModel: Fix potential deadlock. #4296
  • dff0e3b Improve rpc console history behavior
  • 95a9383 Remove CENT-fee-rule from coin control completely
  • 56b07d2 Allow setting listen via GUI
  • d95ba75 Log messages with type>QtDebugMsg as non-debug
  • 8969828 New status bar Unit Display Control and related changes
  • 674c070 seed OpenSSL PNRG with Windows event data
  • 509f926 Payment request parsing on startup now only changes network if a valid network name is specified
  • acd432b Prevent balloon-spam after rescan
  • 7007402 Implement SI-style (thin space) thoudands separator
  • 91cce17 Use fixed-point arithmetic in amount spinbox
  • bdba2dd Remove an obscure option no-one cares about
  • bd0aa10 Replace the temporary file hack currently used to change Bitcoin-Qt's dock icon (OS X) with a buffer-based solution
  • 94e1b9e Re-work overviewpage UI
  • 8bfdc9a Better looking trayicon
  • b197bf3 disable tray interactions when client model set to 0
  • 1c5f0af Add column Watch-only to transactions list
  • 21f139b Fix tablet crash. closes #4854
  • e84843c Broken addresses on command line no longer trigger testnet
  • a49f11d Change splash screen to normal window
  • 1f9be98 Disable App Nap on OSX 10.9+
  • 27c3e91 Add proxy to options overridden if necessary
  • 4bd1185 Allow "emergency" shutdown during startup
  • d52f072 Don't show wallet options in the preferences menu when running with -disablewallet
  • 6093aa1 Qt: QProgressBar CPU-Issue workaround
  • 0ed9675 [Wallet] Add global boolean whether to send free transactions (default=true)
  • ed3e5e4 [Wallet] Add global boolean whether to pay at least the custom fee (default=true)
  • e7876b2 [Wallet] Prevent user from paying a non-sense fee
  • c1c9d5b Add Smartfee to GUI
  • e0a25c5 Make askpassphrase dialog behave more sanely
  • 94b362d On close of splashscreen interrupt verifyDB
  • b790d13 English translation update
  • 8543b0d Correct tooltip on address book page
Tests:
  • b41e594 Fix script test handling of empty scripts
  • d3a33fc Test CHECKMULTISIG with m == 0 and n == 0
  • 29c1749 Let tx (in)valid tests use any SCRIPT_VERIFY flag
  • 6380180 Add rejection of non-null CHECKMULTISIG dummy values
  • 21bf3d2 Add tests for BoostAsioToCNetAddr
  • b5ad5e7 Add Python test for -rpcbind and -rpcallowip
  • 9ec0306 Add CODESEPARATOFindAndDelete() tests
  • 75ebced Added many rpc wallet tests
  • 0193fb8 Allow multiple regression tests to run at once
  • 92a6220 Hook up sanity checks
  • 3820e01 Extend and move all crypto tests to crypto_tests.cpp
  • 3f9a019 added list/get received by address/ account tests
  • a90689f Remove timing-based signature cache unit test
  • 236982c Add skiplist unit tests
  • f4b00be Add CChain::GetLocator() unit test
  • b45a6e8 Add test for getblocktemplate longpolling
  • cdf305e Set -discover=0 in regtest framework
  • ed02282 additional test for OP_SIZE in script_valid.json
  • 0072d98 script tests: BOOLAND, BOOLOR decode to integer
  • 833ff16 script tests: values that overflow to 0 are true
  • 4cac5db script tests: value with trailing 0x00 is true
  • 89101c6 script test: test case for 5-byte bools
  • d2d9dc0 script tests: add tests for CHECKMULTISIG limits
  • d789386 Add "it works" test for bitcoin-tx
  • df4d61e Add bitcoin-tx tests
  • aa41ac2 Test IsPushOnly() with invalid push
  • 6022b5d Make script_{valid,invalid}.json validation flags configurable
  • 8138cbe Add automatic script test generation, and actual checksig tests
  • ed27e53 Add coins_tests with a large randomized CCoinViewCache test
  • 9df9cf5 Make SCRIPT_VERIFY_STRICTENC compatible with BIP62
  • dcb9846 Extend getchaintips RPC test
  • 554147a Ensure MINIMALDATA invalid tests can only fail one way
  • dfeec18 Test every numeric-accepting opcode for correct handling of the numeric minimal encoding rule
  • 2b62e17 Clearly separate PUSHDATA and numeric argument MINIMALDATA tests
  • 16d78bd Add valid invert of invalid every numeric opcode tests
  • f635269 tests: enable alertnotify test for Windows
  • 7a41614 tests: allow rpc-tests to get filenames for bitcoind and bitcoin-cli from the environment
  • 5122ea7 tests: fix forknotify.py on windows
  • fa7f8cd tests: remove old pull-tester scripts
  • 7667850 tests: replace the old (unused since Travis) tests with new rpc test scripts
  • f4e0aef Do signature-s negation inside the tests
  • 1837987 Optimize -regtest setgenerate block generation
  • 2db4c8a Fix node ranges in the test framework
  • a8b2ce5 regression test only setmocktime RPC call
  • daf03e7 RPC tests: create initial chain with specific timestamps
  • 8656dbb Port/fix txnmall.sh regression test
  • ca81587 Test the exact order of CHECKMULTISIG sig/pubkey evaluation
  • 7357893 Prioritize and display -testsafemode status in UI
  • f321d6b Add key generation/verification to ECC sanity check
  • 132ea9b miner_tests: Disable checkpoints so they don't fail the subsidy-change test
  • bc6cb41 QA RPC tests: Add tests block block proposals
  • f67a9ce Use deterministically generated script tests
  • 11d7a7d [RPC] add rpc-test for http keep-alive (persistent connections)
  • 34318d7 RPC-test based on invalidateblock for mempool coinbase spends
  • 76ec867 Use actually valid transactions for script tests
  • c8589bf Add actual signature tests
  • e2677d7 Fix smartfees test for change to relay policy
  • 263b65e tests: run sanity checks in tests too
Miscellaneous:
  • 122549f Fix incorrect checkpoint data for testnet3
  • 5bd02cf Log used config file to debug.log on startup
  • 68ba85f Updated Debian example bitcoin.conf with config from wiki + removed some cruft and updated comments
  • e5ee8f0 Remove -beta suffix
  • 38405ac Add comment regarding experimental-use service bits
  • be873f6 Issue warning if collecting RandSeed data failed
  • 8ae973c Allocate more space if necessary in RandSeedAddPerfMon
  • 675bcd5 Correct comment for 15-of-15 p2sh script size
  • fda3fed libsecp256k1 integration
  • 2e36866 Show nodeid instead of addresses in log (for anonymity) unless otherwise requested
  • cd01a5e Enable paranoid corruption checks in LevelDB >= 1.16
  • 9365937 Add comment about never updating nTimeOffset past 199 samples
  • 403c1bf contrib: remove getwork-based pyminer (as getwork API call has been removed)
  • 0c3e101 contrib: Added systemd .service file in order to help distributions integrate bitcoind
  • 0a0878d doc: Add new DNSseed policy
  • 2887bff Update coding style and add .clang-format
  • 5cbda4f Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope
  • b4a72a7 contrib/linearize: split output files based on new-timestamp-year or max-file-size
  • e982b57 Use explicit fflush() instead of setvbuf()
  • 234bfbf contrib: Add init scripts and docs for Upstart and OpenRC
  • 01c2807 Add warning about the merkle-tree algorithm duplicate txid flaw
  • d6712db Also create pid file in non-daemon mode
  • 772ab0e contrib: use batched JSON-RPC in linarize-hashes (optimization)
  • 7ab4358 Update bash-completion for v0.10
  • 6e6a36c contrib: show pull # in prompt for github-merge script
  • 5b9f842 Upgrade leveldb to 1.18, make chainstate databases compatible between ARM and x86 (issue #2293)
  • 4e7c219 Catch UTXO set read errors and shutdown
  • 867c600 Catch LevelDB errors during flush
  • 06ca065 Fix CScriptID(const CScript& in) in empty script case
Credits

Thanks to everyone who contributed to this release:
  • 21E14
  • Adam Weiss
  • Aitor Pazos
  • Alexander Jeng
  • Alex Morcos
  • Alon Muroch
  • Andreas Schildbach
  • Andrew Poelstra
  • Andy Alness
  • Ashley Holman
  • Benedict Chan
  • Ben Holden-Crowther
  • Bryan Bishop
  • BtcDrak
  • Christian von Roques
  • Clinton Christian
  • Cory Fields
  • Cozz Lovan
  • daniel
  • Daniel Kraft
  • David Hill
  • Derek701
  • dexX7
  • dllud
  • Dominyk Tiller
  • Doug
  • elichai
  • elkingtowa
  • ENikS
  • Eric Shaw
  • Federico Bond
  • Francis GASCHET
  • Gavin Andresen
  • Giuseppe Mazzotta
  • Glenn Willen
  • Gregory Maxwell
  • gubatron
  • HarryWu
  • himynameismartin
  • Huang Le
  • Ian Carroll
  • imharrywu
  • Jameson Lopp
  • Janusz Lenar
  • JaSK
  • Jeff Garzik
  • JL2035
  • Johnathan Corgan
  • Jonas Schnelli
  • jtimon
  • Julian Haight
  • Kamil Domanski
  • kazcw
  • kevin
  • kiwigb
  • Kosta Zertsekel
  • LongShao007
  • Luke Dashjr
  • Mark Friedenbach
  • Mathy Vanvoorden
  • Matt Corallo
  • Matthew Bogosian
  • Micha
  • Michael Ford
  • Mike Hearn
  • mrbandrews
  • mruddy
  • ntrgn
  • Otto Allmendinger
  • paveljanik
  • Pavel Vasin
  • Peter Todd
  • phantomcircuit
  • Philip Kaufmann
  • Pieter Wuille
  • pryds
  • randy-waterhouse
  • R E Broadley
  • Rose Toomey
  • Ross Nicoll
  • Roy Badami
  • Ruben Dario Ponticelli
  • Rune K. Svendsen
  • Ryan X. Charles
  • Saivann
  • sandakersmann
  • SergioDemianLerner
  • shshshsh
  • sinetek
  • Stuart Cardall
  • Suhas Daftuar
  • Tawanda Kembo
  • Teran McKinney
  • tm314159
  • Tom Harding
  • Trevin Hofmann
  • Whit J
  • Wladimir J. van der Laan
  • Yoichi Hirai
  • Zak Wilcox
As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
Also lots of thanks to the bitcoin.org website team David A. Harding and Saivann Carignan.
Wladimir
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007480.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

Blockchain/Bitcoin for beginners 8: Bitcoin addresses, public key hash, P2PKH transactions Bitcoin JSON-RPC Tutorial 1 How to track your bitcoin Blockchain tutorial 27: Bitcoin raw transaction and transaction id How to Complete Unconfirmed BITCOIN Transaction  बिटकॉइन की पेंडिंग पेमेंट को कन्फर्म कैसे करें?

Bitcoin address format. Bitcoin address is an identifier (like account number), starting with 1, 3 or bc1 on the mainnet, containing 27-34 alphanumeric Latin characters and digits (except 0, O, I). Also set to Bitcoin Cash mainnet, bchtest for testnet and bchreg for bitcoin cash regtest. The most popular and trusted block explorer and crypto transaction search engine. The console window in the Bitcoin Core Wallet. If you have been given a TXID by your bitcoin wallet, it’s probably already in its “searchable” format (reverse byte order).. 2. Spending outputs. You use a TXID when you want to use an existing output as an input in a new transaction.. To refer to an existing output, you use the txid it was created in, along with the vout number for that ... Bitcoin transaction confirmation is needed to prevent double-spending of the same money. One of the main advantages of bitcoin is that it avoids the problem of double-spending, i.e. the risk that a digital currency token may be copied and spent more than once.In spite of having no central authority to verify that its tokens are not being duplicated, bitcoin successfully avoids double-spending ... Included in block is the ID of the block in which this transaction was confirmed. Remember – mining is a competitive sport. ... contains all the Bitcoin movement in this one transaction. When sending Bitcoins, it's possible to have several input addresses, and several output addresses. Many wallets automate this process and show the user only one amount, but this amount is actually saved on ...

[index] [46209] [17954] [12908] [23183] [10956] [18417] [39771] [39729] [26666] [32926]

Blockchain/Bitcoin for beginners 8: Bitcoin addresses, public key hash, P2PKH transactions

MORE ON: https://ethereum.ltda/ A cryptocurrency is a type of digital currency that has a decentralized payment system (there is no internal or external admi... For more tips like these visit http://bodymindsuccess.com/bitcoin or subscribe to our channel Blockchain - How to Verify A Bitcoin Transaction And Get Your Hash ID. Overview of Blockchain.info Bitcoin Transaction Tracking. How to Find the Transaction ID in Your Blockchain.info Bitcoin Wallet. This is part 27 of the Blockchain tutorial. This tutorial explains: - What Bitcoin raw transaction is. - Shows an example of a raw transaction using the very first transaction on the Genesis block. The Crypto Dad shows you how to trace a Bitcoin transaction. Important software used is: Electrum bitcoin wallet: https://electrum.org/#home The Blockchain e...

#