Binance Python API – A Step-by-Step Guide - AlgoTrading101 ...
Binance Python API – A Step-by-Step Guide - AlgoTrading101 ...
Bitcoin Exchange Cryptocurrency Exchange Binance
Galileo Dokumentation zum Bitcoin Millionär Niklas ...
Binance API — python-binance 0.2.0 documentation
Binance.US Buy & Sell Crypto
FAQ - Binance Chain Docs
Websockets — python-binance 0.2.0 documentation
binance-official-api-docs/rest-api.md at master · binance ...
Binance API Documentation
La plateforme d'échange de Bitcoin La ... - Binance
Ultimate glossary of crypto currency terms, acronyms and abbreviations
How To End The Cryptocurrency Exchange "Wild West" Without Crippling Innovation
In case you haven't noticed the consultation paper, staff notice, and report on Quadriga, regulators are now clamping down on Canadian cryptocurrency exchanges. The OSC and other regulatory bodies are still interested in industry feedback. They have not put forward any official regulation yet. Below are some ideas/insights and a proposed framework.
Typical securities frameworks will cost Canadians millions of dollars (ie Sarbanes-Oxley estimated at $5m USD/yr per firm). Implementation costs of this proposal are significantly cheaper.
Canadians can maintain a diverse set of exchanges, multiple viable business models are still fully supported, and innovation is encouraged while keeping Canadians safe.
Many of you have limited time to read the full proposal, so here are the highlights:
Effective standards to prevent both internal and external theft. Exchange operators are trained and certified, and have a legal responsibility to users.
Regular Transparent Audits
Provides visibility to Canadians that their funds are fully backed on the exchange, while protecting privacy and sensitive platform information.
Establishment of basic insurance standards/strategy, to expand over time. Removing risk to exchange users of any hot wallet theft.
Background and Justifications
Cold Storage Custody/Management After reviewing close to 100 cases, all thefts tend to break down into more or less the same set of problems: • Funds stored online or in a smart contract, • Access controlled by one person or one system, • 51% attacks (rare), • Funds sent to the wrong address (also rare), or • Some combination of the above. For the first two cases, practical solutions exist and are widely implemented on exchanges already. Offline multi-signature solutions are already industry standard. No cases studied found an external theft or exit scam involving an offline multi-signature wallet implementation. Security can be further improved through minimum numbers of signatories, background checks, providing autonomy and legal protections to each signatory, establishing best practices, and a training/certification program. The last two transaction risks occur more rarely, and have never resulted in a loss affecting the actual users of the exchange. In all cases to date where operators made the mistake, they've been fully covered by the exchange platforms. • 51% attacks generally only occur on blockchains with less security. The most prominent cases have been Bitcoin Gold and Ethereum Classic. The simple solution is to enforce deposit limits and block delays such that a 51% attack is not cost-effective. • The risk of transactions to incorrect addresses can be eliminated by a simple test transaction policy on large transactions. By sending a small amount of funds prior to any large withdrawals/transfers as a standard practice, the accuracy of the wallet address can be validated. The proposal covers all loss cases and goes beyond, while avoiding significant additional costs, risks, and limitations which may be associated with other frameworks like SOC II. On The Subject of Third Party Custodians Many Canadian platforms are currently experimenting with third party custody. From the standpoint of the exchange operator, they can liberate themselves from some responsibility of custody, passing that off to someone else. For regulators, it puts crypto in similar categorization to oil, gold, and other commodities, with some common standards. Platform users would likely feel greater confidence if the custodian was a brand they recognized. If the custodian was knowledgeable and had a decent team that employed multi-sig, they could keep assets safe from internal theft. With the right protections in place, this could be a great solution for many exchanges, particularly those that lack the relevant experience or human resources for their own custody systems. However, this system is vulnerable to anyone able to impersonate the exchange operators. You may have a situation where different employees who don't know each other that well are interacting between different companies (both the custodian and all their customers which presumably isn't just one exchange). A case study of what can go wrong in this type of environment might be Bitpay, where the CEO was tricked out of 5000 bitcoins over 3 separate payments by a series of emails sent legitimately from a breached computer of another company CEO. It's also still vulnerable to the platform being compromised, as in the really large $70M Bitfinex hack, where the third party Bitgo held one key in a multi-sig wallet. The hacker simply authorized the withdrawal using the same credentials as Bitfinex (requesting Bitgo to sign multiple withdrawal transactions). This succeeded even with the use of multi-sig and two heavily security-focused companies, due to the lack of human oversight (basically, hot wallet). Of course, you can learn from these cases and improve the security, but so can hackers improve their deception and at the end of the day, both of these would have been stopped by the much simpler solution of a qualified team who knew each other and employed multi-sig with properly protected keys. It's pretty hard to beat a human being who knows the business and the typical customer behaviour (or even knows their customers personally) at spotting fraud, and the proposed multi-sig means any hacker has to get through the scrutiny of 3 (or more) separate people, all of whom would have proper training including historical case studies. There are strong arguments both for and against using use of third party custodians. The proposal sets mandatory minimum custody standards would apply regardless if the cold wallet signatories are exchange operators, independent custodians, or a mix of both. On The Subject Of Insurance ShakePay has taken the first steps into this new realm (congratulations). There is no question that crypto users could be better protected by the right insurance policies, and it certainly feels better to transact with insured platforms. The steps required to obtain insurance generally place attention in valuable security areas, and in this case included a review from CipherTrace. One of the key solutions in traditional finance comes from insurance from entities such as the CDIC. However, historically, there wasn't found any actual insurance payout to any cryptocurrency exchange, and there are notable cases where insurance has not paid. With Bitpay, for example, the insurance agent refused because the issue happened to the third party CEO's computer instead of anything to do with Bitpay itself. With the Youbit exchange in South Korea, their insurance claim was denied, and the exchange ultimately ended up instead going bankrupt with all user's funds lost. To quote Matt Johnson in the original Lloyd's article: “You can create an insurance policy that protects no one – you know there are so many caveats to the policy that it’s not super protective.” ShakePay's insurance was only reported to cover their cold storage, and “physical theft of the media where the private keys are held”. Physical theft has never, in the history of cryptocurrency exchange cases reviewed, been reported as the cause of loss. From the limited information of the article, ShakePay made it clear their funds are in the hands of a single US custodian, and at least part of their security strategy is to "decline to confirm the custodian’s name on the record". While this prevents scrutiny of the custodian, it's pretty silly to speculate that a reasonably competent hacking group couldn't determine who the custodian is. A far more common infiltration strategy historically would be social engineering, which has succeeded repeatedly. A hacker could trick their way into ShakePay's systems and request a fraudulent withdrawal, impersonate ShakePay and request the custodian to move funds, or socially engineer their way into the custodian to initiate the withdrawal of multiple accounts (a payout much larger than ShakePay) exploiting the standard procedures (for example, fraudulently initiating or override the wallet addresses of a real transfer). In each case, nothing was physically stolen and the loss is therefore not covered by insurance. In order for any insurance to be effective, clear policies have to be established about what needs to be covered. Anything short of that gives Canadians false confidence that they are protected when they aren't in any meaningful way. At this time, the third party insurance market does not appear to provide adequate options or coverage, and effort is necessary to standardize custody standards, which is a likely first step in ultimately setting up an insurance framework. A better solution compared to third party insurance providers might be for Canadian exchange operators to create their own collective insurance fund, or a specific federal organization similar to the CDIC. Such an organization would have a greater interest or obligation in paying out actual cases, and that would be it's purpose rather than maximizing it's own profit. This would be similar to the SAFU which Binance has launched, except it would cover multiple exchanges. There is little question whether the SAFU would pay out given a breach of Binance, and a similar argument could be made for a insurance fund managed by a collective of exchange operators or a government organization. While a third party insurance provider has the strong market incentive to provide the absolute minimum coverage and no market incentive to payout, an entity managed by exchange operators would have incentive to protect the reputation of exchange operators/the industry, and the government should have the interest of protecting Canadians. On The Subject of Fractional Reserve There is a long history of fractional reserve failures, from the first banks in ancient times, through the great depression (where hundreds of fractional reserve banks failed), right through to the 2008 banking collapse referenced in the first bitcoin block. The fractional reserve system allows banks to multiply the money supply far beyond the actual cash (or other assets) in existence, backed only by a system of debt obligations of others. Safely supporting a fractional reserve system is a topic of far greater complexity than can be addressed by a simple policy, and when it comes to cryptocurrency, there is presently no entity reasonably able to bail anyone out in the event of failure. Therefore, this framework is addressed around entities that aim to maintain 100% backing of funds. There may be some firms that desire but have failed to maintain 100% backing. In this case, there are multiple solutions, including outside investment, merging with other exchanges, or enforcing a gradual restoration plan. All of these solutions are typically far better than shutting down the exchange, and there are multiple cases where they've been used successfully in the past. Proof of Reserves/Transparency/Accountability Canadians need to have visibility into the backing on an ongoing basis. The best solution for crypto-assets is a Proof of Reserve. Such ideas go back all the way to 2013, before even Mt. Gox. However, no Canadian exchange has yet implemented such a system, and only a few international exchanges (CoinFloor in the UK being an example) have. Many firms like Kraken, BitBuy, and now ShakePay use the Proof of Reserve term to refer to lesser proofs which do not actually cryptographically prove the full backing of all user assets on the blockchain. In order for a Proof of Reserve to be effective, it must actually be a complete proof, and it needs to be understood by the public that is expected to use it. Many firms have expressed reservations about the level of transparency required in a complete Proof of Reserve (for example Kraken here). While a complete Proof of Reserves should be encouraged, and there are some solutions in the works (ie TxQuick), this is unlikely to be suitable universally for all exchange operators and users. Given the limitations, and that firms also manage fiat assets, a more traditional audit process makes more sense. Some Canadian exchanges (CoinSquare, CoinBerry) have already subjected themselves to annual audits. However, these results are not presently shared publicly, and there is no guarantee over the process including all user assets or the integrity and independence of the auditor. The auditor has been typically not known, and in some cases, the identity of the auditor is protected by a NDA. Only in one case (BitBuy) was an actual report generated and publicly shared. There has been no attempt made to validate that user accounts provided during these audits have been complete or accurate. A fraudulent fractional exchange, or one which had suffered a breach they were unwilling to publicly accept (see CoinBene), could easily maintain a second set of books for auditors or simply exclude key accounts to pass an individual audit. The proposed solution would see a reporting standard which includes at a minimum - percentage of backing for each asset relative to account balances and the nature of how those assets are stored, with ownership proven by the auditor. The auditor would also publicly provide a "hash list", which they independently generate from the accounts provided by the exchange. Every exchange user can then check their information against this public "hash list". A hash is a one-way form of encryption, which fully protects the private information, yet allows anyone who knows that information already to validate that it was included. Less experienced users can take advantage of public tools to calculate the hash from their information (provided by the exchange), and thus have certainty that the auditor received their full balance information. Easy instructions can be provided. Auditors should be impartial, their identities and process public, and they should be rotated so that the same auditor is never used twice in a row. Balancing the cost of auditing against the needs for regular updates, a 6 month cycle likely makes the most sense. Hot Wallet Management The best solution for hot wallets is not to use them. CoinBerry reportedly uses multi-sig on all withdrawals, and Bitmex is an international example known for their structure devoid of hot wallets. However, many platforms and customers desire fast withdrawal processes, and human validation has a cost of time and delay in this process. A model of self-insurance or separate funds for hot wallets may be used in these cases. Under this model, a platform still has 100% of their client balance in cold storage and holds additional funds in hot wallets for quick withdrawal. Thus, the risk of those hot wallets is 100% on exchange operators and not affecting the exchange users. Since most platforms typically only have 1%-5% in hot wallets at any given time, it shouldn't be unreasonable to build/maintain these additional reserves over time using exchange fees or additional investment. Larger withdrawals would still be handled at regular intervals from the cold storage. Hot wallet risks have historically posed a large risk and there is no established standard to guarantee secure hot wallets. When the government of South Korea dispatched security inspections to multiple exchanges, the results were still that 3 of them got hacked after the inspections. If standards develop such that an organization in the market is willing to insure the hot wallets, this could provide an acceptable alternative. Another option may be for multiple exchange operators to pool funds aside for a hot wallet insurance fund. Comprehensive coverage standards must be established and maintained for all hot wallet balances to make sure Canadians are adequately protected.
Current Draft Proposal
(1) Proper multi-signature cold wallet storage. (a) Each private key is the personal and legal responsibility of one person - the “signatory”. Signatories have special rights and responsibilities to protect user assets. Signatories are trained and certified through a course covering (1) past hacking and fraud cases, (2) proper and secure key generation, and (3) proper safekeeping of private keys. All private keys must be generated and stored 100% offline by the signatory. If even one private keys is ever breached or suspected to be breached, the wallet must be regenerated and all funds relocated to a new wallet. (b) All signatories must be separate background-checked individuals free of past criminal conviction. Canadians should have a right to know who holds their funds. All signing of transactions must take place with all signatories on Canadian soil or on the soil of a country with a solid legal system which agrees to uphold and support these rules (from an established white-list of countries which expands over time). (c) 3-5 independent signatures are required for any withdrawal. There must be 1-3 spare signatories, and a maximum of 7 total signatories. The following are all valid combinations: 3of4, 3of5, 3of6, 4of5, 4of6, 4of7, 5of6, or 5of7. (d) A security audit should be conducted to validate the cold wallet is set up correctly and provide any additional pertinent information. The primary purpose is to ensure that all signatories are acting independently and using best practices for private key storage. A report summarizing all steps taken and who did the audit will be made public. Canadians must be able to validate the right measures are in place to protect their funds. (e) There is a simple approval process if signatories wish to visit any country outside Canada, with a potential whitelist of exempt countries. At most 2 signatories can be outside of aligned jurisdiction at any given time. All exchanges would be required to keep a compliant cold wallet for Canadian funds and have a Canadian office if they wish to serve Canadian customers. (2) Regular and transparent solvency audits. (a) An audit must be conducted at founding, after 3 months of operation, and at least once every 6 months to compare customer balances against all stored cryptocurrency and fiat balances. The auditor must be known, independent, and never the same twice in a row. (b) An audit report will be published featuring the steps conducted in a readable format. This should be made available to all Canadians on the exchange website and on a government website. The report must include what percentage of each customer asset is backed on the exchange, and how those funds are stored. (c) The auditor will independently produce a hash of each customer's identifying information and balance as they perform the audit. This will be made publicly available on the exchange and government website, along with simplified instructions that each customer can use to verify that their balance was included in the audit process. (d) The audit needs to include a proof of ownership for any cryptocurrency wallets included. A satoshi test (spending a small amount) or partially signed transaction both qualify. (e) Any platform without 100% reserves should be assessed on a regular basis by a government or industry watchdog. This entity should work to prevent any further drop, support any private investor to come in, or facilitate a merger so that 100% backing can be obtained as soon as possible. (3) Protections for hot wallets and transactions. (a) A standardized list of approved coins and procedures will be established to constitute valid cold storage wallets. Where a multi-sig process is not natively available, efforts will be undertaken to establish a suitable and stable smart contract standard. This list will be expanded and improved over time. Coins and procedures not on the list are considered hot wallets. (b) Hot wallets can be backed by additional funds in cold storage or an acceptable third-party insurance provider with a comprehensive coverage policy. (c) Exchanges are required to cover the full balance of all user funds as denominated in the same currency, or double the balance as denominated in bitcoin or CAD using an established trading rate. If the balance is ever insufficient due to market movements, the firm must rectify this within 24 hours by moving assets to cold storage or increasing insurance coverage. (d) Any large transactions (above a set threshold) from cold storage to any new wallet addresses (not previously transacted with) must be tested with a smaller transaction first. Deposits of cryptocurrency must be limited to prevent economic 51% attacks. Any issues are to be covered by the exchange. (e) Exchange platforms must provide suitable authentication for users, including making available approved forms of two-factor authentication. SMS-based authentication is not to be supported. Withdrawals must be blocked for 48 hours in the event of any account password change. Disputes on the negligence of exchanges should be governed by case law.
Continued review of existing OSC feedback is still underway. More feedback and opinions on the framework and ideas as presented here are extremely valuable. The above is a draft and not finalized. The process of further developing and bringing a suitable framework to protect Canadians will require the support of exchange operators, legal experts, and many others in the community. The costs of not doing such are tremendous. A large and convoluted framework, one based on flawed ideas or implementation, or one which fails to properly safeguard Canadians is not just extremely expensive and risky for all Canadians, severely limiting to the credibility and reputation of the industry, but an existential risk to many exchanges. The responsibility falls to all of us to provide our insight and make our opinions heard on this critical matter. Please take the time to give your thoughts.
Buy, Sell, and Trade Crypto on WazirX: How to trade Bitcoin and other Cryptocurrencies on WazirX?
Source: WazirX Hello Friends! Welcome to my one-stop article where you can do earning while learning about “Cryptocurrencies”. So, in this article, you’ll learn about: How to buy, sell, and trade Bitcoin as well as other cryptocurrencies onWazirX? WazirX is an “International Cryptocurrency Exchange” and do allow individuals from most countries to sign up on their exchange.
Step 1: Signing up for a WazirX account.
Click here or simply copy-paste the below link in your browser’s search-bar and press Enter to go over to the WazirX’s Sign-Up page: WazirX Referral Link: https://wazirx.com/invite/j9ykd Once you’re on the sign-up page, click on the SIGN UP or SIGN UP NOW button to proceed further.
Step 2: Submit your registration details.
Email — Enter your complete email address. This is the email address you will use to login and also receive any communication from WazirX. You cannot change your login email address later.
Password — Enter a strong password that you will remember. Passwords must be atleast 6 characters long and a maximum of 64 characters. We recommend using passwords longer than 10 characters. Do not use passwords that you’ve already used on another website. Try and mix special characters like @#$%^&-* along with capitals and numerics in your password.
Step 3: Email verification.
Once you’ve entered your email, password and clicked on sign up, you will receive a verification email at your email address. Click on the Verify Email button in the email. You will be taken back to the WazirX website where your verification will be confirmed!
Note that the verification email is only valid for 15 minutes. If you do not verify in 15 minutes, login to your WazirX account again and click on the Resend verification email button.
Step 4: Mobile verification.
After verifying your email, the next step is to verify your mobile number.
Mobile number — Enter your complete mobile number. Do not include country code or ‘0’ at the start. This will also be the number at which you will receive an OTP when logging into your WazirX account.
Verification OTP — You will receive an OTP via an SMS. Enter the OTP in the verification box and click verify.
Step 5: Submit your KYC details.
You can complete your KYC by selecting your country from the dropdown & click on Complete KYC. You’ll then be taken to the next step to enter your details and upload KYC documents for verification.
Name — Enter your name as it appears on your KYC document. For eg — If the name is John Smith on your document, please enter John Smith in the form too.
Date of Birth — Enter your DOB in DD/MM/YYYY format. For eg — If your DOB is 1st April 1989, enter 01/04/1989. You must be 18 Years and above to apply for a WazirX account.
Address — Enter your full address as it appears on your KYC document. Do not enter the City, State & PIN Code in this box as there are separate boxes for that
Documents — Depending on the country you’ve chosen, you’ll need to upload a set of KYC documents. Carefully fill in the details in the respective fields & upload a scanned copy or a photo of your KYC document & your selfie as illustrated in the Sign Up form.
Before you click submit, please cross check all your details to make sure you’ve not made any typing errors. This will speed up your verification process. The verification process could take anywhere between 24–48 hours depending on the volume of signups.
Step 6: Start trading Crypto on your WazirX.
EXCHANGE — Click on the “Exchange” tab and select the crypto pair in which you want to trade from the: USDT, BTC, or INR pairing list.
BUY or SELL — Click on the Buy or Sell tab. Then select either a LIMIT or STOP LIMIT order type. Note that in case of STOP LIMIT, you need to enter a STOP PRICE at which you want that trade to take place. So if you’re a beginner, then it’s recommended to select a LIMIT order type.
AT PRICE —Enter your own price at which you want to Buy or Sell your selected crypto.
AMOUNT — Enter the amount of crypto which you want to Buy or Sell.
PLACE ORDER — Once you’ve entered all the required details related to your Buy or Sell order, you just need to click on the PLACE [BUY/SELL] ORDER to submit your order which will be and can be seen in WazirX’s Open Order Book.
That’s it! As soon as your open order gets completed, you’ve executed your first cryptocurrency trade successfully. So, what are you waiting for? Sign-up, trade, and earn exciting referral bonuses on the WazirX exchange from the above given link now. If you want to support me in my efforts for the growth of the Crypto Community then please feel free to donate as per your wish: Bitcoin $BTC Address: 17hRk6kuhwEnAJN6KTkSjFvfihX4PFbei Ethereum $ETH Address: 0x63d5692ee8b7bd9bcf1706d2fa73ca0e4e2cef96 XRP $XRP Address: rNxCw7HUbd51dvUMUyC7ju5XivXmCM1Bvr XRP $XRP Destination Tag: 544806860 Binance Coin $BNB Address: bnb14kktnh6n20efy4kfh0u5xy38rw53j8q5gkzuzv Binance Coin $BNB Memo: 7515036536
❤️ Like, Share, Leave your comment
If you like my article, don’t forget to like, share with your friends or colleagues and leave your comment below. And do Follow me…
Trading and investing in cryptocurrencies (also called digital or virtual currencies, crypto assets, altcoins and so on) is subject to market risks. The information provided on this blog is purely for guidance, informational and educational purposes. It does not constitute investment advice, financial advice, trading advice, or any other sort of advice. Do conduct your own due diligence and consult your financial advisor before making any investment decisions.
Bitcoin (BTC) is a peer-to-peer cryptocurrency that aims to function as a means of exchange that is independent of any central authority. BTC can be transferred electronically in a secure, verifiable, and immutable way.
Launched in 2009, BTC is the first virtual currency to solve the double-spending issue by timestamping transactions before broadcasting them to all of the nodes in the Bitcoin network. The Bitcoin Protocol offered a solution to the Byzantine Generals’ Problem with ablockchainnetwork structure, a notion first created byStuart Haber and W. Scott Stornetta in 1991.
Bitcoin’s whitepaper was published pseudonymously in 2008 by an individual, or a group, with the pseudonym “Satoshi Nakamoto”, whose underlying identity has still not been verified.
The Bitcoin protocol uses an SHA-256d-based Proof-of-Work (PoW) algorithm to reach network consensus. Its network has a target block time of 10 minutes and a maximum supply of 21 million tokens, with a decaying token emission rate. To prevent fluctuation of the block time, the network’s block difficulty is re-adjusted through an algorithm based on the past 2016 block times.
With a block size limit capped at 1 megabyte, the Bitcoin Protocol has supported both the Lightning Network, a second-layer infrastructure for payment channels, and Segregated Witness, a soft-fork to increase the number of transactions on a block, as solutions to network scalability.
Bitcoin is a peer-to-peer cryptocurrency that aims to function as a means of exchange and is independent of any central authority. Bitcoins are transferred electronically in a secure, verifiable, and immutable way.
Network validators, whom are often referred to as miners, participate in the SHA-256d-based Proof-of-Work consensus mechanism to determine the next global state of the blockchain.
The Bitcoin protocol has a target block time of 10 minutes, and a maximum supply of 21 million tokens. The only way new bitcoins can be produced is when a block producer generates a new valid block.
The protocol has a token emission rate that halves every 210,000 blocks, or approximately every 4 years.
Unlike public blockchain infrastructures supporting the development of decentralized applications (Ethereum), the Bitcoin protocol is primarily used only for payments, and has only very limited support for smart contract-like functionalities (Bitcoin “Script” is mostly used to create certain conditions before bitcoins are used to be spent).
In the Bitcoin network, anyone can join the network and become a bookkeeping service provider i.e., a validator. All validators are allowed in the race to become the block producer for the next block, yet only the first to complete a computationally heavy task will win. This feature is called Proof of Work (PoW). The probability of any single validator to finish the task first is equal to the percentage of the total network computation power, or hash power, the validator has. For instance, a validator with 5% of the total network computation power will have a 5% chance of completing the task first, and therefore becoming the next block producer. Since anyone can join the race, competition is prone to increase. In the early days, Bitcoin mining was mostly done by personal computer CPUs. As of today, Bitcoin validators, or miners, have opted for dedicated and more powerful devices such as machines based on Application-Specific Integrated Circuit (“ASIC”). Proof of Work secures the network as block producers must have spent resources external to the network (i.e., money to pay electricity), and can provide proof to other participants that they did so. With various miners competing for block rewards, it becomes difficult for one single malicious party to gain network majority (defined as more than 51% of the network’s hash power in the Nakamoto consensus mechanism). The ability to rearrange transactions via 51% attacks indicates another feature of the Nakamoto consensus: the finality of transactions is only probabilistic. Once a block is produced, it is then propagated by the block producer to all other validators to check on the validity of all transactions in that block. The block producer will receive rewards in the network’s native currency (i.e., bitcoin) as all validators approve the block and update their ledgers.
The Bitcoin protocol utilizes the Merkle tree data structure in order to organize hashes of numerous individual transactions into each block. This concept is named after Ralph Merkle, who patented it in 1979. With the use of a Merkle tree, though each block might contain thousands of transactions, it will have the ability to combine all of their hashes and condense them into one, allowing efficient and secure verification of this group of transactions. This single hash called is a Merkle root, which is stored in the Block Header of a block. The Block Header also stores other meta information of a block, such as a hash of the previous Block Header, which enables blocks to be associated in a chain-like structure (hence the name “blockchain”). An illustration of block production in the Bitcoin Protocol is demonstrated below. https://preview.redd.it/m6texxicf3151.png?width=1591&format=png&auto=webp&s=f4253304912ed8370948b9c524e08fef28f1c78d
Block time and mining difficulty
Block time is the period required to create the next block in a network. As mentioned above, the node who solves the computationally intensive task will be allowed to produce the next block. Therefore, block time is directly correlated to the amount of time it takes for a node to find a solution to the task. The Bitcoin protocol sets a target block time of 10 minutes, and attempts to achieve this by introducing a variable named mining difficulty. Mining difficulty refers to how difficult it is for the node to solve the computationally intensive task. If the network sets a high difficulty for the task, while miners have low computational power, which is often referred to as “hashrate”, it would statistically take longer for the nodes to get an answer for the task. If the difficulty is low, but miners have rather strong computational power, statistically, some nodes will be able to solve the task quickly. Therefore, the 10 minute target block time is achieved by constantly and automatically adjusting the mining difficulty according to how much computational power there is amongst the nodes. The average block time of the network is evaluated after a certain number of blocks, and if it is greater than the expected block time, the difficulty level will decrease; if it is less than the expected block time, the difficulty level will increase.
What are orphan blocks?
In a PoW blockchain network, if the block time is too low, it would increase the likelihood of nodes producingorphan blocks, for which they would receive no reward. Orphan blocks are produced by nodes who solved the task but did not broadcast their results to the whole network the quickest due to network latency. It takes time for a message to travel through a network, and it is entirely possible for 2 nodes to complete the task and start to broadcast their results to the network at roughly the same time, while one’s messages are received by all other nodes earlier as the node has low latency. Imagine there is a network latency of 1 minute and a target block time of 2 minutes. A node could solve the task in around 1 minute but his message would take 1 minute to reach the rest of the nodes that are still working on the solution. While his message travels through the network, all the work done by all other nodes during that 1 minute, even if these nodes also complete the task, would go to waste. In this case, 50% of the computational power contributed to the network is wasted. The percentage of wasted computational power would proportionally decrease if the mining difficulty were higher, as it would statistically take longer for miners to complete the task. In other words, if the mining difficulty, and therefore targeted block time is low, miners with powerful and often centralized mining facilities would get a higher chance of becoming the block producer, while the participation of weaker miners would become in vain. This introduces possible centralization and weakens the overall security of the network. However, given a limited amount of transactions that can be stored in a block, making the block time too longwould decrease the number of transactions the network can process per second, negatively affecting network scalability.
3. Bitcoin’s additional features
Segregated Witness (SegWit)
Segregated Witness, often abbreviated as SegWit, is a protocol upgrade proposal that went live in August 2017. SegWit separates witness signatures from transaction-related data. Witness signatures in legacy Bitcoin blocks often take more than 50% of the block size. By removing witness signatures from the transaction block, this protocol upgrade effectively increases the number of transactions that can be stored in a single block, enabling the network to handle more transactions per second. As a result, SegWit increases the scalability of Nakamoto consensus-based blockchain networks like Bitcoin and Litecoin. SegWit also makes transactions cheaper. Since transaction fees are derived from how much data is being processed by the block producer, the more transactions that can be stored in a 1MB block, the cheaper individual transactions become. https://preview.redd.it/depya70mf3151.png?width=1601&format=png&auto=webp&s=a6499aa2131fbf347f8ffd812930b2f7d66be48e The legacy Bitcoin block has a block size limit of 1 megabyte, and any change on the block size would require a network hard-fork. On August 1st 2017, the first hard-fork occurred, leading to the creation of Bitcoin Cash (“BCH”), which introduced an 8 megabyte block size limit. Conversely, Segregated Witness was a soft-fork: it never changed the transaction block size limit of the network. Instead, it added an extended block with an upper limit of 3 megabytes, which contains solely witness signatures, to the 1 megabyte block that contains only transaction data. This new block type can be processed even by nodes that have not completed the SegWit protocol upgrade. Furthermore, the separation of witness signatures from transaction data solves the malleability issue with the original Bitcoin protocol. Without Segregated Witness, these signatures could be altered before the block is validated by miners. Indeed, alterations can be done in such a way that if the system does a mathematical check, the signature would still be valid. However, since the values in the signature are changed, the two signatures would create vastly different hash values. For instance, if a witness signature states “6,” it has a mathematical value of 6, and would create a hash value of 12345. However, if the witness signature were changed to “06”, it would maintain a mathematical value of 6 while creating a (faulty) hash value of 67890. Since the mathematical values are the same, the altered signature remains a valid signature. This would create a bookkeeping issue, as transactions in Nakamoto consensus-based blockchain networks are documented with these hash values, or transaction IDs. Effectively, one can alter a transaction ID to a new one, and the new ID can still be valid. This can create many issues, as illustrated in the below example:
Alice sends Bob 1 BTC, and Bob sends Merchant Carol this 1 BTC for some goods.
Bob sends Carols this 1 BTC, while the transaction from Alice to Bob is not yet validated. Carol sees this incoming transaction of 1 BTC to him, and immediately ships goods to B.
At the moment, the transaction from Alice to Bob is still not confirmed by the network, and Bob can change the witness signature, therefore changing this transaction ID from 12345 to 67890.
Now Carol will not receive his 1 BTC, as the network looks for transaction 12345 to ensure that Bob’s wallet balance is valid.
As this particular transaction ID changed from 12345 to 67890, the transaction from Bob to Carol will fail, and Bob will get his goods while still holding his BTC.
With the Segregated Witness upgrade, such instances can not happen again. This is because the witness signatures are moved outside of the transaction block into an extended block, and altering the witness signature won’t affect the transaction ID. Since the transaction malleability issue is fixed, Segregated Witness also enables the proper functioning of second-layer scalability solutions on the Bitcoin protocol, such as the Lightning Network.
Lightning Network is a second-layer micropayment solution for scalability. Specifically, Lightning Network aims to enable near-instant and low-cost payments between merchants and customers that wish to use bitcoins. Lightning Network was conceptualized in a whitepaper by Joseph Poon and Thaddeus Dryja in 2015. Since then, it has been implemented by multiple companies. The most prominent of them include Blockstream, Lightning Labs, and ACINQ. A list of curated resources relevant to Lightning Network can be found here. In the Lightning Network, if a customer wishes to transact with a merchant, both of them need to open a payment channel, which operates off the Bitcoin blockchain (i.e., off-chain vs. on-chain). None of the transaction details from this payment channel are recorded on the blockchain, and only when the channel is closed will the end result of both party’s wallet balances be updated to the blockchain. The blockchain only serves as a settlement layer for Lightning transactions. Since all transactions done via the payment channel are conducted independently of the Nakamoto consensus, both parties involved in transactions do not need to wait for network confirmation on transactions. Instead, transacting parties would pay transaction fees to Bitcoin miners only when they decide to close the channel. https://preview.redd.it/cy56icarf3151.png?width=1601&format=png&auto=webp&s=b239a63c6a87ec6cc1b18ce2cbd0355f8831c3a8 One limitation to the Lightning Network is that it requires a person to be online to receive transactions attributing towards him. Another limitation in user experience could be that one needs to lock up some funds every time he wishes to open a payment channel, and is only able to use that fund within the channel. However, this does not mean he needs to create new channels every time he wishes to transact with a different person on the Lightning Network. If Alice wants to send money to Carol, but they do not have a payment channel open, they can ask Bob, who has payment channels open to both Alice and Carol, to help make that transaction. Alice will be able to send funds to Bob, and Bob to Carol. Hence, the number of “payment hubs” (i.e., Bob in the previous example) correlates with both the convenience and the usability of the Lightning Network for real-world applications.
Schnorr Signature upgrade proposal
Elliptic Curve Digital Signature Algorithm (“ECDSA”) signatures are used to sign transactions on the Bitcoin blockchain. https://preview.redd.it/hjeqe4l7g3151.png?width=1601&format=png&auto=webp&s=8014fb08fe62ac4d91645499bc0c7e1c04c5d7c4 However, many developers now advocate for replacing ECDSA with Schnorr Signature. Once Schnorr Signatures are implemented, multiple parties can collaborate in producing a signature that is valid for the sum of their public keys. This would primarily be beneficial for network scalability. When multiple addresses were to conduct transactions to a single address, each transaction would require their own signature. With Schnorr Signature, all these signatures would be combined into one. As a result, the network would be able to store more transactions in a single block. https://preview.redd.it/axg3wayag3151.png?width=1601&format=png&auto=webp&s=93d958fa6b0e623caa82ca71fe457b4daa88c71e The reduced size in signatures implies a reduced cost on transaction fees. The group of senders can split the transaction fees for that one group signature, instead of paying for one personal signature individually. Schnorr Signature also improves network privacy and token fungibility. A third-party observer will not be able to detect if a user is sending a multi-signature transaction, since the signature will be in the same format as a single-signature transaction.
4. Economics and supply distribution
The Bitcoin protocol utilizes the Nakamoto consensus, and nodes validate blocks via Proof-of-Work mining. The bitcoin token was not pre-mined, and has a maximum supply of 21 million. The initial reward for a block was 50 BTC per block. Block mining rewards halve every 210,000 blocks. Since the average time for block production on the blockchain is 10 minutes, it implies that the block reward halving events will approximately take place every 4 years. As of May 12th 2020, the block mining rewards are 6.25 BTC per block. Transaction fees also represent a minor revenue stream for miners.
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.
Dev meeting? Would say so, yes The people are still exhausted from the payment ID meeting :) Guess we could ping some people vtnerd, moneromooo, hyc, gingeropolous, TheCharlatan, sarang, suraeNoether, jtgrassie Anyone up for a meeting? Yep I'm here Here o/ Perhaps we should just start and people will eventually hop in? oof sorry guys, I'm working on the new FFS and I forgot all about this. Got a couple of new volunteers. This literally might be able to launch tomorrow. I know that. It's called "flow" :) I could run if you're out of time? go for it dEBRUYNE you guys are going to like this new FFS. We're like 99% done. Hi rehrar: someone else do the milestone thing already? All right, jtgrassie, perhaps you'd to start w/ briefly describing your most recent PR? https://github.com/monero-project/monero/pull/5091 oneiric, xiphon did everything like....everything As far as I can see, it allows the user to push his transaction over I2P, thereby masking the origin IP of the sendeuser great And it hooks into vtnerd's PR right? Sure. It basically just builds on vtnerds Tor stuff. sorry dEBRUYNE Really not much added. I have it running and tested. From the perspective of the user, what needs to be configured exactly? Nice Assuming the PR is included in the release binaries I'm using knacccs i2p-zero duirng testing but will of course work with any i2p setup sorry dEBRUYNE <= Np Looks a little like dams breaking, now that we have some dark clouds over Kovri and people take matters into their own hands ... User needs to run i2p, expose a socks service and and inbound tunnel. Basically same as Tor Okay, so should be reasonable as long as we write proper documentation for it (e.g. an elaborate guide) rbrunner, yes, knaccc credit for jumping on i2p-zero really dEBRUYNE: documentation monero side is kindof done. i2p side is very much implementation specific. I suppose we could write some guides for the most popular implementations? e.g. i2p-zero aims to be zero conf, but i2pd or Kovri would be differnet. I see, great vtnerd___: Do you want to add anything? could amend the current kovri guide for monero use from --exclusive-peer to the new proxy support Now I have i2p-zero running and tested with the #5091, I plan to jump back over to helping knaccc on getting that polished. I added support for socks proxy in the basic wallets ^ excellent Yes vtnerd___ I havent tested it yet but looks sweet. So connections to `monerod` over Toi2p are possible within wallet cli and wallet rpc Awesome This also implies auth+encryption even if ssl is not in use (when using an onion or i2p address) All right moneromooo: are you here? If so, could you perhaps share what you've been working on? I am. I revived the SSL PR, more stuff on multi sender txes, an implementation of ArticMine's new block size algorithm. I presume a multi sender tx works similar to multisig insofar as the senders have to exchange data before the transaction can be performed right? Yes. There are 2 SSL PRs. What's the diff? Theoretically this would also allow the sender to provide an output right? Which would be kind of similar to Bitcoin's P2EP The second one adds some things like selecting a cert by fingerprint. Yes. (for the first sentence) All right, awesome For anyone reading, this breaks the assumption of the inputs belonging to a single sender, which makes analysis more difficult Nice side-effect. Much work coming for the various wallets to support that rbrunner: Anything you'd like to share in the meeting btw? Yes, just a little info I have started to seriously investigate what it would mean to integrate Monero into OpenBazaar I have already talked with 2 of their devs, was very interesting In maybe 2 or 3 weeks I intend to write a report Too early to tell much more :) Soon^tm I guess :) Yep Currently wrestling with Go debugging whole new world moneromooo: Has pony recently shared any insights regarding the upcoming 0.14 release btw? No. All right I would love to see the tor & i2p PR's merged sooner rather than later so we can get more testing done. ^ +1 Isn't that famous early code freeze already on the horizon? fluffypony, luigi1111 ^ I suppose I could provide a little update regarding the GUI btw As always, lots of bug fixes and improvements :-P selsta has recently added a feature to support multi accounts dsc_ has revamped the wizard and will now start working on implementing the different modes and a white theme dsc_ is working fulltime on the GUI already? yes :) dsc_ is bae In light of the recent payment ID discussion, we've also, by default, disabled the option to add a payment ID unless the user explicitely activates the option on the settings page rehrar ^ nice I spoke about this yesterday at the coffee chat, this is not a good decision. How does it handle integrated addresses? The same way? rehrar ? For the next many months, we are still stuck with PAyment IDs in the ecosystem. Making it harder for people to access them will make Monero suck so hard to use for the average person for many months. i agree with rehrar Remove the option of Payment IDs when we remove Payment IDs rehrar: The new GUI release won't be live until probably mid march though Which is a few weeks in advance of the scheduled protocol upgrade Payment ID removal comes in October right, but Payment IDs are not removed in March Did we not have loose consensus on removing the old, unencrypted payment IDs in march? they are removed in October We had discussed a deprecation in March and a ban in October ok, then if we are going to do that, we have to commit to it and contact the exchanges like Binance that use them and get rid of them in the next few months (of unencrypted) Binance is huge, and if they still use them, then people will be very upset that they can't deposit or use Payment IDs easily I'm just speaking from a UX perspective. I thought it was unencrypted in April and possibly encrypted in October Yes I do agree Timeline and notes: https://github.com/monero-project/meta/issues/299 impossible to remove them for march, many exchanges still use them We can defer it to the 0.15 release if needed Well, that wasn't the impression for them log that I just read today This was all discussed in the earlier meeting linked above We have to force the ecosystem off of Payment IDs before we remove them from the UI, is all I'm saying Remove != make difficult to use ... or make them more difficult there, right? ping sgp_ sarang, I understand, and I agreed with you during that meeting. But then I started thinking of it as a UX person, which I am. And that huge massive problem leapt out at me i think making them difficult to generate is a good idea but making them difficult to consume and use is a bad idea well, maybe not a good idea, but a better idea ^ If we defer the decision to depriciate long payment IDs to october, won't we have the same issue then? The UI can gave an expandable payment ID field like MyMonero and we can still call it deprecated It is foolhardy to remove an option that the ecosystem uses. So I suggest we keep the Payment ID in the UI until October when they are completely banned. no dEBRYUNE, because they will be banned via consensus sgp_ imo it may be a misdirection of dev resources to add that since things are proceeding in the short term rather than long term but this is a relatively minor point Nothing matters til exchanges change All right The issue is that consensus will still have them in April, and exchanges won't upgrade because they are still allowed. Thus they must still be in the UI. endogenic these changes are already merged in the GUI to hide it like you do ok But when they are banned, exchanges are forced to upgrade or stop using Monero, so we can remove them safely because they won't be in use rehrar: that's a strong assumption sarang that they will upgrade? yes if they don't, then they can't use Monero If exchanges require pid, users need a way to set a pid. Making it hard for the user in the interim is just going to be a nightmare. we have decided to take our "stand" in October A way that is not too hard, then To be clear, we still intend to deprecate long encrypted payment IDs in April right? But no enforcement until October the term "deprecated" doesn't mean much if it's still allowed, and used in popular places yes, as far as I understand it jtgrassie, exactly True I suppose dEBRUYNE: we need to be more specific when talking about deprecation the person who suffers is the user There are two proposals for GUI deprecation: 1. Hide it in the send screen with a simple option to expand (currently merged iirc) 2. Hide it completely in the send screen unless users enable the field in advanced settings (PR'd but not merged yet iirc) What are the arguments for 2? Both are poor options, but 1 is better than 2 by a long shot Well the people who need to be made to "suffer" are the exchanges. And I don't see a way to make exchanges "suffer" other than by having their suffering customers complain to them constantly that they need to update. ^ CLI has something similar where users need to set a manual payment ID transfer mode. Not sure if it's merged yet the way to make the exchanges suffer is when we ban PIDs. They either upgrade or don't use Monero. exact;y Agree with rerahr here have exchanges been provided with clear, practical, sufficient technical upgrade plans for supporting what they're doing with PIDs but with subaddrs? Both are poor options, but 1 is better than 2 by a long shot <= I wouldn't call 1. a poor option. Have you actually checked how it looks? Because it states "Payment ID" and a user has to click on the + to expand the field endogenic: yes the email when out. Blog post coming soon, but contains the same info as the email also the exhcnages' users are often using wallets that don't support subaddresses ok great as well, it should be noted that the timeline for exchanges to upgrade is September, not October when the fork is. Which wallets are that? Rehrar: I don't see option 1. causing any issues/confusion i guess it doesnt matter too much if withdrawing as a personal user the main address should suffice Because September is when the new versions will be coming out without PIDs in the UI If there's opposition to 2, 1 is fine. We can still call it deprecated which is the optics we need anyway exchange users are often just using other exchanges lol. No wallets involved. dsc_ dEBRUYNE, ok, I trust you guys here then rbrunner: i was thinking mymonero last i heard Ok pigeons: rbrunner yes receiving on subaddresses won't be supported yet sending to them has been possible though and yes as learnandlurkin says often they withdraw to other systems like exhcnages that also dont yet support subaddresses I really can't come up with any good argument for 2. right now endogenic: seems not much of an issue then. Exchanges will typically support withdrawals to both subaddresses and plain addresses (especially if we are going to force them to use subaddresses) For deposits, MyMonero works properly if the user sends to a subaddress Actually the second solution was already merged: https://github.com/monero-project/monero-gui/pull/1866 Maybe not enough eyes watching :) The important thing is to have done something to justify having a big "DEPRECATED IN APRIL" stamp on PIDs to spook exchanges in the interim This was for solution 1: https://github.com/monero-project/monero-gui/pull/1855 The Monero Community Workgroup will start making noise everywhere we can to exchanges, and everywhere else that will listen. Try to get on those garbage news sites also. So everyone knows that deprecated in April, and banned in September Hey, for solution 1, write "Payment ID (optional, deprecated)" or similar there rbrunner: noted rehrar: probably wait until the blog post, but it should only be a few days Maybe a Reddit sticky post would be useful? With the blog post If people are over freaking out about the hashrate or terabyte blockchain :) sigh Any questions for the MRL side? Is someone checking ArticMine's block size changes for weird behaviour in some cases etc ? How would such testing work? Private blockchain?