GRAFT “Anti-ASIC” Major Network Update 1.5 on October 31, 2018

GRAFT developers just released a new version of GRAFT software for the upcoming major network update that will introduce a new variation of the PoW hash algorithm which prevents ASIC mining. Network hashrate is important, but it is not the only factor in blockchain security. The way this hash power is distributed between the miners is also important. ASICs break the balance and facilitate centralization (concentration of hash power) which can be dangerous for the network.

The major network update will apply a new variation of CryptoNight hash algorithm (CryptoNight V8 / CN variant 2) which is currently ASIC-resistant. The source code of the new version 1.5 can be downloaded from master. The binaries for Linux and Windows will be available shortly (please follow GRAFT Twitter account for the notification).

The major network update (aka hard fork) in GRAFT mainnet is scheduled for Wednesday, October 31st at block 207,700 (block 194,130 in GRAFT testnet tomorrow, October 24, 2018).

The major network update means that if you are running the GRAFT network node (graftnoded) you must upgrade to the latest software before October 31st. If you do not upgrade your node before October 31st, it will be disconnected from the mainnet. Note that users of GRAFT mobile and desktop wallets are not affected by the hard fork and should not do anything – as long as they are still connected to the default proxy supernodes (if you are connected to your own supernode, do not forget to upgrade the underlying network node).

GRAFT Weekly Development Status Update October 22nd, 2018

Hi everyone, this is our weekly update on GRAFT development activities. Last week we were focused on RTA alpha debugging and new release, exchange broker development, and payment gateway UI, while dealing with an “anti-ASIC” major network update. Let’s review the status of all these activities.

The new RTA alpha release with stabilized communication is ready, the only reason we did not release it to the alpha testers last week was the work on the hard fork patch, so the release will happen later this week. This RTA release is a close version of the upcoming beta release to the mainnet, with a few things still in development.

Before RTA beta, however, we are going to open the RTA alpha to the public, so everyone will be able to “touch” and try to break it while still in test mode (right now it is only available to the 50 alpha testers.) Once we get a “confirmation” from the RTA Public Alpha testers, we will release the beta to the mainnet. This way we can test the supernode network scalability in environment pretty close to the real world operations before it goes to full production.

While the core dev team was focused on RTA and the upcoming major network update, another team continued working on payment terminal apps, exchange broker, and payment gateway. More specifically, last week there were working on an enhanced GUI for exchange broker and payment gateway (as shown on the screenshot below). Since the payment gateway is aimed towards the less technical, more business operations oriented audience, the quality and functionality of the user interface is very important.

Also, the core team is working on a patch for the upcoming major network update that will introduce a new variation of the hash algorithm that prevents ASIC mining. Network hashrate is important, but it is not the only factor in blockchain security. The way this hash power is distributed between the miners is also important. ASICs break the balance and facilitate centralization (concentration of hash power) which can be dangerous for the network.

The patch will apply a new variation of CryptoNight hash algorithm (CryptoNight V8 / CN variant 2) which is currently ASIC-resistant. The patch is still being tested – thanks to the group of GRAFT miners’ who help with the testing. We will announce the hard fork block number and date once the testing is finished (probably tomorrow). As usual, we remind that the major network update (aka “hard fork”) is only relevant to the miners and other full node operators; if you use one of the GRAFT mobile or desktop wallet apps you don’t need to do anything.

Finally, please check out the questions and answers from our first official AMA (“Ask Me Anything”) session which took place last week. We tried to answer all the questions from the community, but if you don’t find an answer to your question in the list – don’t worry, we plan to conduct periodic (shooting for monthly) AMA sessions!

Happy GRAFTing!

October AMA with the Devs

AMA Feature Image



Community Manager: Welcome everybody for the first GRAFT developer AMA! We’ve been collecting questions across our various social media channels, which lead developers, Slava and Dan will be responding to. This channel will be reserved strictly for questions and answers. We will give the community a few moments to respond in the Discord #graft-lounge and Telegram, and determine if there are any follow-up questions we have time to address. I will be working to keep things moving so that we can get through as many questions as we can in the short amount of time that we have. Please note that if your question doesn’t get answered, it will remain in the pool for follow-on AMAs.

With that, let’s begin with our first question…


Question: Could you talk a little about the software development process that Graft uses? What development methodology does Graft use? Is it an industry-standard model (such as agile, incremental, or waterfall) or something custom designed? Perhaps you could walk us through how the process works, for example how a concept goes from initial idea to implementation to testing to competition?

Dan: We use an agile methodology with two-week sprints.  The system is quite complex with many components that we have to time together into planned releases.  We started with formal testing but are quickly migrating towards community supported rollouts.  You can see how various pieces stitch together looking at our development roadmap.


Question: I currently scan various blockchain projects. I’ve noticed several unresponded pull requests that seem to be ignored. In understanding C++ for a number of years. They seem to be solutions for a drastic fix. I cannot involve myself in a blockchain that the dev doesn’t fix issues in a timely manner. How can i invest with any courage the dev and the project is community oriented if they do not listen to pull requests!

Is there any particular reason why PR are being ignored and is the super node RTA going to launch without any review from all pull requests?

Slava: We pay attention to all pull requests. Pull requests however are not “just push an approve” button activity – they have to be vetted, tested, incorporated into the release schedule, and timed for the appropriate network update (fork) – all these things take time and are gated by the development and release schedule.


Question: It is appreciated that the Graft Team have said many times that people who buy GRFT aren’t investors. But if GRFT is truly a ‘community’ coin then it would help if someone is available to give one consistent message from the Graft team to the people that form the community. There is often misinformation and confusion in the telegram and elsewhere because there isn’t someone from the core team that is managing communication with the community. Will you be hiring an individual or team to manage communication with the community?

Dan: We are sometimes constrained as to what we can share due to incomplete conceptual framework (we start out with broad brush strokes and then fill in the details as we move closer to implementation), private info from 3rd parties that we’re not at liberty to share (such is often the case with exchanges or other partners), or simply are working on something that may or may not pan out and we try to avoid situations where we overpromise and underdeliver.  As engineers, we tend to communicate once something is done and no uncertainties remain – we’re learning however to communicate more, bear with us.


Question: In the current alpha implementation, the RTA SuperNode requires a hot wallet with full spend keys on the VPS running the SuperNode.  This seems dangerous: if we imagine graft at $1, that means a T4 is holding a hot wallet worth a quarter of a million USD, which makes it a tempting target for hacks—someone who gains access to the VPS could steal the entire stake plus any transaction fees.  Why did Graft decide to go with a hot wallet approach as opposed to the cold-stake approach (of submitting stakes as time-locked transactions on the blockchain) commonly used by other Masternode systems?

Slava: First, it’s important to take into account the specifics of the Cryptonote protocol – proof of balance in a CryptoNote wallet is not as easy as doing the same in “”regular”” non-private blockchains. Second, we are aware of this issue and already have it in the backlog, so it will be resolved in the future RTA release.


Question: The recently announced stimulus plan for supernodes was unveiled without any details at all as to how it will work.  This has led the community taking wild guesses as to how it might work (e.g. with the unofficial calculator floating around) and what the payoffs might be.  Proper planning for potential supernode operators requires the actual details.

When do you plan to formalize the stimulus payoff details so that people can start deciding whether or not they want to run supernodes?

Dan: The stimulus plan will take a bit of flushing out.  We have defined the general direction and the targets for the incentives and will be filling in the details as we get to the roll out stage.  The goal is to make the network perform at roughly 100k tx monthly volume.


Question: There has been quite some discussion recently on the GRAFT blockchain telegram channel about the upcoming Monero CNv2 fork and the impact it may have on the GRAFT blockchain. Some are convinced that the fork will lead to a substantial migration of ASIC/FPGA hashrate to GRAFT (being the most profitable CNv1) from XMR. This in turn could lead to centralization of the network, a potential drop in value (as the farms are less like to hold their GRAFT) and even outright attacks. It would be great to get more information from you on this topic, if you plan to fork to CNv2 or any of the CNv1 derivates in the coming months?

Slava: The GRAFT dev team is working on the patch. We will announce the date of the hard fork shortly.


Question: Where are we with Verifone and Ingenico exactly? What will be procedure for merchant to turn on GRAFT as currency on their POS machines, and will it require manual update?

Dan: Regarding Verifone software – it is done and ready for the rest of the network – of course there are iterations and updates happening on that as we go as all these things are interconnected. Using GRAFT on Verifone terminals only requires Engage-compatibility. Engage is their app platform – they are rolling it out to various models starting with the newest / most capable ones.  To enable GRAFT, the merchant has to go to Verifone marketplace, add the app to their merchant account, configure the wallet and few other payment gateway options. As simple as that. Regarding Ingenico – we are waiting for the platform upgrade from their side and opening API’s – tentatively Q1 2019, so for now our primary goal is to get the Verifone terminal to work flawlessly.


Question: Could you briefly share the Graft Team marketing plan and road marks that you are following to implement the plan?

Dan: Here’s an example of what we’re thinking and driving towards. https://www.graft.network/merchant-service-provider/ . Please keep in mind however, that this is a decentralized, community project, so core team’s involvement in marketing and distribution is focused on working on core software and integrations.


Question: Many people have attempted to send coins from the mobile wallet to Cryptopia. The transaction fails because the mobile wallet does not support non-integrated payment ID’s. The users then contact Cryptopia about the lost coins and then Cryptopia asks for a payment ID. There are a few problems with this all too common scenario, but the biggest problem in my opinion is that the mobile wallet does not provide access to transaction ID’s. Will the mobile wallet soon be able to display transaction ID’s?

Slava: 1) Cryptopia is the only exchange that does not support integrated addresses. We’ve contacted their devs several times and asked to implement this support. They promised to do it but never provided any ETA. By the way, they do not support integrated address for Monero or other CryptoNote coins, not just GRAFT. Here is the latest response from Cryptopia devs: “We’ve escalated this issue and hope to have an ETA for you in the near future. We haven’t forgotten about it.” 2) In the next releases of the wallets we plan to add both detached payment id & full transaction history (including Tx ID).


Question: When will the results of the RTA alpha testing (bug reports/fixes/etc.) be made public? Or if they won’t be, when will you start accepting public bug reports for RTA supernodes?

Slava: As you may have noticed, we have started communicating the development status on a weekly basis providing lots of details to the community.  The results of the testing feed back into the development with the end result of a public alpha and then beta state of the product.


Question: Do you plan to conduct any external security audit of the platform (RTA/Exchange brokers/etc.) before the final production release?

Slava: One-time security audits are largely ineffective (subpar, expensive, and short lived) as the code changes literally every day.  The code is open to the community to examine and find bugs.  We’re also looking into implementing a bug bounty program.  (Note that both GRAFT co-founders are CISSP certification holders and have serious infosec background.)


Question: What is the long-term plan for continuing Graft’s management?  Some other coins have defined organization structures that are designed to continue without the present Dev teams.  Has the Graft team thought about how Graft will be managed on an ongoing basis once the project reaches maturity?

Dan: Good question.  We recognize that there is a natural evolution in a decentralized project governance as the project matures.  We are considering a DAO path potentially, taking notes from other leading projects, and looking to incorporate some of the innovative models (like quadratic voting) that provide equalized participation.


Question: Multiple sites out there already support payments with cryptocurrency.  How’s GRAFT different?

Dan: The primary purpose of the GRAFT project is to build a DECENTRALIZED payment network – the fact that it can process crypto payments is one of the important by-products, not the be all and end all. The devil is in the details – centralized payment brokers go against the principles of decentralization and they don’t scale. GRAFT’s goal is a decentralized payment network with no borders, no single party controls, no (or marginalized) banks, agnostic to the currency you pay with.


Question: I’ve heard that early supernode holders will be incentivized to participate in the graft network and I applaud that. Doesn’t it make sense to incentivize merchants to encourage graft usage by offering a transaction fee holiday for some time period up front?  You could still pay the network supernode participants out of the coins set aside for incentives (or not).  I think that incentivizing the vendor will go MUCH further towards promoting crypto adoption.

Dan: Yes, we’re thinking about incentivizing other eco-system participants and have thought about waving the transaction fees for the merchants for period of time.  It’s not clear whether it’s strong enough of an incentive for them to adopt a new payment network if they didn’t have an interest in it before.  We are thinking that the focus with merchants should be on creating awareness in the industries that are notoriously hard to get merchant services in, as well as making it super easy for them to integrate GRAFT into their existing systems and processes.


Question: Service Brokers are going to be One of the most critical part of the Graft Ecosystem. Considering an example where Bitcoin payment is made by a buyer and Merchant’s payout choice is in Fiat USD. This is the most obvious use case I could think of. And the kind of liquidity needed for converting BTC to USD is going to be huge (to make settlement seemless). I fear individuals (SN owners) could provide this liquidity. Unless a major exchange could be a service broker I personally feel this will be difficult. Hard fact being we are facing difficulties in listing Graft on a bigger exchange, so what’s the plan on getting a high liquidity exchange?

Dan: You’re right – payout brokers are one of the keys to the functional network. We anticipate the liquidity to come from both smaller and larger brokers. The plan is that once the project gains recognition and adoption in the marketplace, the exchanges will open up as it’s a very lucrative market for them.  At this time we have a number of smaller payout brokers who have registered their intent to provide these services to the network.


Question: One problem with almost every cryptocurrency is the boundless growth of the blockchain data. One of the numbers that got pulled from the reward post was 100k transactions per day.  Graft transactions average about 12kB, so put those together and you get the blockchain growing by 1.2GB/day.  It’ll hit nearly 100 gigs after 2 months, nearly 500 gigs after a year.Does Graft have any long-term plan to reduce that storage requirement at the node and/or supernode level?

Slava: This is common problem for all blockchains, not just a specific problem to GRAFT. The current short-term solution is merging recent Monero code which introduced a new method of proofs for confidential transactions – Bulletproof – which is supposed to reduce the blockchain size by 80%.

https://web.stanford.edu/~buenz/pubs/bulletproofs.pdf
https://monero.stackexchange.com/questions/6781/what-are-bulletproofs


Question: We appreciate your efforts to involve the community in the project, how would you like to improve this relationship over the next few months?

Dan: Thanks for this question. As a decentralized project, we have to really pull back on implementing roll-out and adoption plans for the network and rely on the community to take over and form their own geographic and industry clusters with their own promotion and business plans for the network.   We will know that the network is thriving if there are initiatives, ideas, local governance, and business models that go well beyond what was envisioned by the founding team.


Question: How does GRAFT handle void transaction? Is that similar to void transaction of Credit cards?

Slava: Void transactions are typically handled by the point of sale, before it even comes to the settlement. If payment is processed, some payment processors allow voiding such transaction. On blockchain it is impossible to reverse (void) a transaction after it is added to the transaction pool (even before it’s added to the block), so RTA “void” should be replaced by refund (return) transaction.


Community Manager: Excellent. Well that concludes today’s AMA. I want to thank Dan and Slava for taking the time out to answer questions. We are happy to get through so many, and look forward to future sessions. Thank you all!


GRAFT Weekly Development Status Update October 15th, 2018

It’s been another hard working week for GRAFT devs, and here is our brief weekly update.

We are continuing work on debugging and improvement of the RTA communication protocol. During the last week we merged “blocking doubled RTA notifications” PR, fixed connection and white peer lists management, and did some internal debugging, merging, and testing. Also, we just finished creating a couple of diagnostics tools – an automated communication test framework and GraftnetExplorer (see the screenshots below).

The supernodes communicate to each other through “tunnels” which they build using the existing network of underlying cryptonodes. They use a special mechanism that allows creating a set of shortest and fastest tunnels. Currently, the protocol works but not in the most efficient way, so we are looking for weak spots and bugs. These diagnostic tools have already allowed us to find and fix a couple of bugs in communication between the supernodes. At some point we may release them to the alpha group (and then to the public as well).

As you can see on the GraftnetExplorer screenshot above, several supernodes in this dev network are interconnected, which means they can send each other instant notifications or broadcast messages to a larger group or even the entire network – all without knowing the IP addresses of other nodes, just by using their logical IDs. This is one of the major features (but not the only one) that differentiates the GRAFT supernodes from similar protocols such as Dash masternodes as it significantly enhances both the privacy and security of the GRAFT network.

The automated testing framework is another utility, recently developed by the team, that allows us to simulate various scenarios of communication between the supernodes and print the resulting diagnostics and statistics.

On the screenshot above you can see one of the results of the test run. There is a detailed backtrace located before the red line, while the next test is the same but without the details. 3 out of 4 the communication tests were successful, while one was failed (‘broadcast’, marked by letter ‘F’).

Another part of the team continues working on terminal apps, payment gateway, and exchange broker – optimizing the API, preparing for the production environment deployment, and developing reports. They are in the middle of the sprint, and the results will be reported next week.

Also, please check out a new version of the GRAFT white paper which now can be downloaded from the website. In this version, we have added recent proposals created since the previous white paper release, and summarized the changes in the original functionality. As the ideas initially set forth in the original GRAFT white paper gradually materialize, we need to make adjustments as we get deeper into the project. There are three areas of new or updated content in this version of the white paper:

And finally, the GRAFT Team will be hosting an AMA (“Ask Me Anything”) live on Telegram and Discord on October 18th, at 12pm EDT, so if you have not submitted your questions yet please do so!

Happy GRAFTing!

AMA With the Devs – October 18th

GRAFT AMA with the Devs
Have a burning question about the GRAFT Network? Marketing plan? Adoption? Community involvement? Technical questions? Submit your question(s) and get an answer! In a continued effort to increase engagement with our community and educate the market, the GRAFT Team will be hosting an AMA live on Telegram and Discord on October 18th, at 12pm EDT.

Questions will be categorized and collected through a Google form to make the best use of time and format.

* PLEASE SUBMIT ONE QUESTION AT A TIME. You will have the opportunity to post another question after submission. This allows us to keep the questions concise, organized and minimize duplication.

SUBMIT QUESTIONS HERE: https://goo.gl/forms/10VVUaqcWqp9Kg2y1

FORMAT:
  • Questions will be moderated by our Discord Community Manager, and answered by GRAFT devs.
  • Q&A will be delivered simultaneously on Telegram and Discord via the GRAFT Bridge Bot.
  • We have an hour for the AMA. Will try to get through as many questions as we can, with target of 20. The remaining questions will be held over for the future monthly AMA rounds.
  • Afterword, a summary will be posted to the GRAFT blog, and then pushed to all social media channels.
Happy GRAFTing!

GRAFT Development Status Update October 8, 2018

It’s been a week since the previous dev status update, and, as we promised last time, we would like to keep our community posted weekly, so here is another update on GRAFT development status.

Last week we continued working on RTA implementation in several directions including fixing bugs discovered during alpha testing, implementing the full automated test suite, preparing a new supernode release, and continuing working on stability of the communication protocol. The fixes include the bugs in initial seed connection, p2p logging, and storing of p2p state data. The automated test suite is built on python-based test framework and will allow to automate the regression and other QA tests.

The new supernode release for alpha testers will be available later this week. In addition, we are finalizing the supernode plugin framework which will be used for plugging extra apps such as exchange brokers into the supernode.

Speaking of exchange brokers and other components of GRAFT network ecosystem, we almost finished developing a live demo that showcases the payment flow on a hardware payment terminal. One of the main goals of GRAFT project is bringing crypto payments into the physical world of brick-and-mortar stores. Unlike most other projects in the area of crypto payments, we realize that the shortest way to adoption by brick-and-mortar retailers and service providers is using their existing hardware payment terminals (aka “pinpads”), because these terminals are already integrated with various point of sale systems. While there are only a few major payment terminal brands, there are hundreds if not thousands of types of point of sale applications they are connected to.

Hardware payment terminals can be loaded with additional software such as GRAFT payment app, without requiring retailers to purchase, test, certify, and maintain a new hardware in their stores. But how to showcase such an app online if it’s designed to run on particular hardware? Our payment application emulator is the first version of such a showcase application that will allow the demonstration of altcoin acceptance on a Verifone terminal using GRAFT network. The initial version of the emulator (see the screenshot below) will be released later this week and available for anyone to try a Bitcoin/GRAFT payment.

From the last week’s events, it’s also important to mention the following two things. First, the incentives for RTA supernodes. Although this is not directly related to development process, the additional rewards will help boost the RTA network once it’s released to public beta on the mainnet. Second, the patch fixing the code execution vulnerability which was “silently” released last Monday. The fix for this denial of service vulnerability is merged into master under 1.4.5 and can be downloaded and built by anyone running GRAFT network nodes (please do not confuse it with the previous “burning bug” patch 1.4.4 for exchanges that was released a few days before the last one).

See you next week! Happy GRAFTing!

Incentives for Full Supernodes

Any network needs to be stimulated to get off the ground. A simple marketplace network might require bringing in sellers when there are not enough buyers, or bringing in buyers when there are not enough sellers. All the prominent networks of today – Uber, AirBnB, eBay, Amazon – faced this issue and were able to overcome it by tapping into existing users or providers of similar services, and by creating extra startup incentives for people joining their platforms.

GRAFT is no exception. It is a complex network with many participants – users, miners, full supernode operators, service brokers, proxy supernode operators, merchants, application developers. Having so many players is both a blessing and a challenge.

Miners represent the first layer of the network (settlement), and they are already incentivized through both network transaction fees and block mining rewards, which do not depend on the number of settled transactions and provide a steady income for miners. Beyond the miners, the next group without which the network will not function are the full supernodes which are critical for real-time authorizations (RTA) and the pay-in/pay-out facilitation.

Full supernodes get paid for performing validations for the network and preventing double-spending while processing authorizations in real time. Their income depends exclusively on the number of transactions that they get to work on as well as the total number of full supernodes in the network. Full supernodes are chosen randomly in each block, with two selected from each of the four tiers for a total eight supernodes, which equally split the 0.5% fee of the transaction they authorize. The problem, however, is that a small transaction volume of the brand new payment network would result in low initial full supernode income, and thus little incentive to run full supernodes before the network volume ramps up.

The good news is that there is a fairly easy way to incentivize the full supernode hosts without resorting to simple airdrop-type incentives or block reward sharing. What we will do instead is send enough RTA transactions across the network to provide a healthy transaction volume until the network is fully ramped up. This way we reward full supernodes for the real work they are supposed to do – validating transactions – unlike most other second layer reward models where masternodes receive passive income for just “being there” (which does little to promote network robustness or self-optimization).

The incentive program is designed to maintain a robust daily transaction volume until merchant-generated RTA transactions reach that level on their own. The number and size of stimulus transactions will depend on overall transaction volume and will be reduced gradually as the network gains momentum. We estimate the cost of this program to range between 50 and 100 million GRFT.

As with any new network, especially one with lots of participant types, the GRAFT Network needs to be stimulated to maintain a level of involvement ensuring stability of the network and availability of network services. We believe that the most critical part needing extra stimulation at this early stage is the full supernode layer. To stimulate the network as a whole, however, we are also considering additional groups of participants that may require stimulus going forward. For example, buyers may need to receive cashback incentives (similar to some credit cards) in order to choose GRFT over other methods of payment available at the checkout.

As always, we’re open to other suggestions from the community.

Fundraising Initiative (clarification)

Earlier this week we published a form for project contributions in form of donations on the home page. We would like to take a moment to explain the rationale behind it and address the concerns raised by some members of the community.

We collected modest funds during the ICO, further affected by the falling market. While sufficient to carry out the main development track we’ve committed to, there are ancillary initiatives the community has expressed interest in or that have potential to increase awareness or improve adoption, that do not fit into our current budget.

Tier 1-2 exchange listings are expensive, and while they add to the liquidity of the token, they do not represent the “critical path” for the project and therefore are not allocated for in our current budget. We do however recognize there are different groups within the community for which liquidity is important. We also recognize that in order to speed adoption of the GRAFT ecosystem, it’s important to have as many gateways to the GRFT token as possible for increased visibility and to present opportunities for participants to engage where they feel most comfortable, i.e. their favorite exchange.

In addition to exchange listings, we have additional projects we can get involved in, like the ColdPay card. These projects require significant capital investment upfront.

To enable these new initiatives, we are opening up the project to voting and donations as a way for the community to indicate their appetite for us delivering on these initiatives and help fund these projects.

We have heard a few concerns so far from the community and would like to address those:

  • No specifics on the exchanges
    Most exchanges we enter into negotiations with ask for a non-disclosure agreement. They do it so that the negotiated amounts are not widely known and to avoid getting inundated with inquiries from the community. We will disclose what we can, when we can. (This is of course not applicable to community vote listings)
  • No transparency on the donation wallet
    The criteria for the payment system was that we could collect the shipping address data alongside the donation, and the promotion claim would be inextricably linked to the donation to prevent abuse. We can and will create a separate swipe wallet for the balance to be seen by the community.
  • Community doesn’t have enough visibility into the projects and use of funds
    We heard you – we’re adding a way to vote for these initiatives. Vote here


GRAFT Development Status Update October 1st, 2018

We listened to our community and decided to publish development status updates more often (bi-weekly or even weekly). However, since one week cannot accommodate the same amount of news as one month, don’t expect to receive long updates anymore!

Here is a quick round up of the news since the previous dev update.

First Working Prototype of Bitcoin Pay-In Broker

We have completed the first working prototype of a Bitcoin Pay-In Broker, which allows merchants to accept Bitcoin at checkout (both in brick-and-mortar stores and online) using GRAFT mobile point of sale or hardware payment terminal apps. The buyer can pay with any wallet supporting Bitcoin, as designed in the original GRAFT white paper. This is a big milestone for the GRAFT project, along with the ongoing RTA alpha, as the main concept of GRAFT is supporting multiple cryptocurrencies as a method of payment for merchants and buyers.



Some time next week we will place a button on the web site that will allow anyone to try out this workflow on the live network with live brokers and payment gateway!

RTA Alpha

The Dev team is continuing working on RTA alpha issues. Currently, we are focused on communication stability and optimization of RTA communication. We still have several issues with tunnel construction (the base mechanism for RTA communication based on P2P network), and optimizing the amount of messages traveling between the nodes – to provide more lightweight and stable communication.

As a reminder, RTA alpha is closed release to a group of 50 alpha testers selected from the large community of volunteers. Not surprisingly, these people are going to be the first full supernode owners and operators, although we have a much larger group of future supernode owners waiting for the beta release. The plan is to release beta to the mainnet as soon as the alpha is stable and fully featured with the functionality required for RTA transaction processing.

By the way, we have some exciting news for supernode owners coming out this week – we’re formulating an incentive program to stimulate the supernode network as part of ramping up the GRAFT network as a whole. We believe we’ve come up with a very elegant solution for it. More details will be released soon.

“Burning bug” Patch

There was a bug found in CryptoNote wallet code, the full description of the issue can be found here. The short story is that the bug affected only exchanges and only the wallet – no implications for regular users, and no need (even for exchanges) to update the network node daemon. Since GRAFT is not a direct clone of Monero (unlike some other CryptoNote blockchains), it took some time to adjust the Monero patch to current GRAFT wallet code, which was eventually done successfully last week, and the patch was “silently” released to the exchanges. TradeOgre and STEX updated their wallets immediately and as usual, Cryptopia is behind schedule but communicated to us that they are working on the update and it will be ready “asap” (no ETA provided).

As a side note – such bugs and patches mean that some part of engineering resources had to be diverted, but the impact on RTA timelines should be minimal.

Stay tuned, happy GRAFTing!

Engineering Update: Pay-in Broker and Payment Gateway Demo

While we’ve been focusing on stabilizing the Full Supernode based RTA (real-time authorizations), part of the team has been diligently working on the other components that are necessary to make the main GRAFT Network use case (paying with any digital currency with your favorite wallet) a reality – namely Payment Gateway and an Pay-in (aka Accept) Broker, and it’s time to show some progress!

Pay-in broker is a type of an exchange broker that provides alt-currency acceptance for the network. It’s a critical piece required to enable any digital currency acceptance at the POS with the wallets of user preference.

Payment Gateway provides a layer between the payment terminal and a network that’s meant to handle business logic and part of the remote wallet functionality.