Stratis Masternode Registration Protocol

Stratis masternodes solve the problem of providing useful services to a blockchain network while keeping the list of services decentralised and tamper-proof. In the initial masternode implementation the service being provided is the Breeze Privacy Protocol, but it is anticipated that many more services can be added in future.
In order for this goal to be accomplished, each masternode must register (advertise) its existence via the Stratis blockchain. This is what is referred to as the Masternode Registration Protocol. A masternode registration simply consists of a specially formatted Stratis transaction. This transaction contains all the pertinent information needed by a client to connect to and validate the masternode.
A registration transaction, once submitted to the network, remains valid indefinitely until invalidated by one of the consensus rules governing such registrations. These are:

  • The masternode server’s funding address is not funded within the initial window period.
  • The collateral funds are insufficient at the conclusion of the window period (see section Collateral Verification for additional information regarding the collateral and the balance tracking).
  • The collateral funds get moved, wholly or in part, to another address, thereby decreasing the balance below the required threshold.
  • A subsequent registration is made at a greater block height than the original (e.g. to update the masternode’s public parameters).
  • (Currently not enforced) A registration expires every N blocks, requiring the operator to periodically refresh it.

It is the responsibility of the Breeze client software to scan the Stratis blockchain for the most current masternode registrations prior to initiating contact with any server. They do this by observing each incoming block, looking for transactions that match the bitstream format. When a registration is found, it is stored in the node’s local store.
The block height that the registration is received at determines the window period for the masternode funding transaction. The masternode operator has to move the required collateral into the funding address before this window elapses. If this is not done the registration will be regarded as expired and purged from the local storage of all nodes on the network.
Once a sufficient number of valid masternode registrations have been downloaded, the client can select one at random and try to connect to it to utilise its services (e.g. the Breeze Privacy Protocol). Optionally the masternode selection can be performed once the entire blockchain is downloaded, as this is more fair to masternodes that register later in the chain.
The process described above has already been implemented into the Stratis software offering.
Bitstream format for masternode registration transaction
The registration transaction consists of a single transaction broadcast on the Stratis network (either testnet for testing or mainnet for ‘live’ masternodes). This transaction can have any number of funding inputs, as normal.
It has precisely one nulldata (data storage) output marking the entire transaction as a masternode registration. There can be an optional change return output, which if present must be at the end of the entire output list. The remainder of the transaction outputs are of near-dust value. Each output encodes 64 bytes of data into a public key script. The contents and format of the encoded data is described below.
The presumption is that the transaction outputs are not reordered by the broadcasting masternode, as this would result in potential data corruption.

OP_RETURN transaction output
Field Size Description


Encoded public key transaction outputs
Field Size Description
1 1 byte Protocol version byte (if >200, it is a test registration to be ignored by mainnet wallets)
2 2 bytes Length of registration header
3 34 bytes Server ID of masternode (base58 representation of the collateral address, right padded with spaces if it is less than 34 characters long)
4 4 bytes IPv4 address of masternode, one byte per octet. Use 00000000 for an empty address. This field is not used for the Breeze Privacy Protocol; it is a placeholder for future functionality
5 16 bytes IPv6 address of masternode, one byte per octet. Use 00000000 00000000 00000000 00000000 for an empty address. This field is not used for the Breeze Privacy Protocol; it is a placeholder for future functionality
6 16 bytes Masternode server URI, currently this is an ASCII onion address hostname without any prefix or suffix. An empty address is signified by 00000000 00000000 00000000 00000000, but leaving this empty is not valid for the current Breeze Privacy Protocol implementation
7 2 bytes TCP port of masternode, may be ignored by client implementation
8 2 bytes RSA signature length in bytes
9 n bytes RSA signature proving ownership of the Breeze Privacy Protocol server’s private key
10 2 bytes ECDSA signature length in bytes
11 n bytes ECDSA signature made with the private key of the address used as the server ID. This same address is where the collateral will need to be located
12 40 bytes Hash of the Breeze Privacy Protocol server’s configuration file. This may be moved into the header in the next version of the protocol
The protocol format can be extended in future to accommodate new functionality. New fields should attempt as far as possible to retain backward compatibility with the existing fields

On connection with the Breeze Privacy Protocol server by a client, the public key of the server will be verified by the client to ensure that the server is authentic and in possession of the registered keys. The Privacy Protocol is then followed as normal.
Collateral Verification
For the Breeze Privacy Protocol to function well, the creation of numerous or insufficiently powerful masternode servers must be disincentivised. Therefore, consensus rules that govern the validity of a masternode need to be established and enforced by participating client nodes.
A Stratis masternode requires 250 000 Stratis coins (STRAT) to be regarded as compliant. These coins should be kept in a single address, and should not be moved once the funding transaction is performed.
On receipt of each new block, the non-masternodes will check each transaction for those that affect a currently tracked masternode server. If funds have been moved out of the address, the calculated balance is decreased. If funds come in, the calculated balance increases. Once the balance has been computed for a masternode, its registration is automatically deleted if it falls below the 250 000 STRAT threshold. It is therefore not recommended that significant transactional activity be performed with the collateral funds, to avoid inadvertently invalidating registrations.

The above diagram illustrates 4 basic scenarios for a masternode’s registration sequence.

  • Node 1 has made a sufficient funding transaction within the window period, and as such its collateral is regarded as compliant.
  • Node 2 was initially compliant after the window period, but later removed some funds from the address, and therefore no longer has sufficient collateral.
  • Node 3 made two transfers that when aggregated form sufficient collateral in the target address. This is a valid, but non-standard method of performing the funding.
  • Node 4 took too long for the funding transaction to be performed (it was outside the window period), and is therefore regarded as non-compliant in terms of its collateral obligation.

The collateral verification functionality has also already been implemented into the Stratis software offering.
Future improvements
Inter-node discovery protocol
A drawback of the approach outlined in this paper is that every node has to download the entire blockchain from the genesis block onwards in order to accurately determine collateral balances. It is more efficient for registrations to be accumulated by full nodes, and circulated to their peers (full or light nodes) with sufficient proof of their accuracy.
The inter-node discovery protocol has already been implemented in the Stratis node software, but is not currently used in order to keep the initial version as simple as possible. It also has an indirect requirement for the peer policing described in the Peer policing model section.
Improvement proposal – peer policing model
There are some differences between existing masternode implementations and the envisioned Stratis masternode approach. Briefly:

  • Dash masternodes are remunerated ‘passively’. This requires that they be actively pinged in a verifiable way by the remainder of the network to avoid paying a masternode that performs no work.
  • Conversely, a Stratis masternode can currently only earn remuneration via active participation in the Breeze Privacy Protocol with connected clients. This removes the need to directly police the masternode in this sense.
  • Due to the high cost of a top tier Stratis masternode, it is presumed that the operator will be economically incentivised to positively participate in the network. This is similar to the core tenets of the Proof Of Stake consensus mechanism.

There are also some aspects of the Dash approach that are desirable to emulate, particularly the ability to have the collateral in ‘cold’ storage.
The requirements for the Stratis top tier masternode may be summarised as follows:

  • The node operator must be in possession of at least 250 000 Stratis (i.e. they possess the private key to move or spend them).
  • These collateral Stratis must be present in a single address.
  • Moving the Stratis collateral to a different address invalidates any proof of possession generated prior to the move.

These requirements need to be actively enforced to prevent dilution of the Privacy Protocol security model. It is proposed that the entities most suited to perform the enforcement are the masternode’s peers on the Stratis network. These peers may be one of the following:

  • Another masternode (essentially a full node with additional features).
  • A ‘full’ node with a complete copy of the Stratis blockchain.
  • A ‘light’ node that does not retain a copy of the entire chain, but does at least retain block headers.
  • Other types of nodes are outside of the scope of this document.

The onus is on a particular masternode to advertise its services to the network. This means that every node can elect whether or not to regard a masternode registration as valid, depending on the information it has available to it. From a game-theoretic perspective, it is advantageous for the operators of ‘rival’ masternodes to immediately present proofs of non-compliance of a particular masternode to the rest of the network. It is additionally presumed that there is no advantage to be gained for an honest node to propagate registrations known to be invalid.
An example of the ‘lifetime’ of a registration & implementation of the ‘proof of non-compliance’ concept is as follows:

  1. Operator configures masternode, which generates masternode registration Y on startup.
  2. Node operator moves sufficient collateral into address X (the ‘funding transaction’). This needs to be done within a finite window period after the registration transaction is made.
  3. Registration Y is broadcast as a transaction to peer nodes for inclusion into the Stratis blockchain in block Z.
  4. The registration is cached on each peer node. Nodes that join the network after block Z need not download the entire chain to receive registration Y – they can receive lists of verified historical registrations by communicating with their peers (inter-node discovery protocol). Light nodes can validate registrations for themselves by evaluating the Merkle proof of the registration against their locally downloaded block header storage.
  5. All full nodes on the network can directly evaluate the balance available in address X at any time. Therefore, if it transpires that a spurious masternode registration has been broadcast (which may happen) the full nodes will not forward that registration on to new peers. Peers that attempt to send known-invalid registrations will receive a proof of non-compliance in response.
  6. The status quo persists for a period of time without any changes that affect masternode registration validity.
  7. The masternode operator moves a portion of the funds from address X elsewhere, i.e. they are now below the collateral requirement.
  8. All nodes that download blocks will immediately be able to tell that the balance of X has changed, although a light node may not know what the actual balance is. Full nodes do know (or can calculate) what the balance is, and can construct a proof thereof showing that the masternode is no longer compliant.
  9. The non-compliance proof will be broadcast between nodes. This could be done pre-emptively (i.e. broadcast proof to all known peers immediately), or it could be done passively in response to receiving an invalid registration from a peer.

At a high level, the proof of insufficient funds will consist of the following elements:

  • A copy of the ‘funding transaction’ for the masternode. This is defined in more detail in the Funding Transaction
  • The registration record itself (in its entirety, as the peer may not have downloaded it yet).
  • At least one complete transaction with the funding transaction included as one or more of its inputs i.e. showing that collateral funds have been moved/spent.
  • The net result of the movement transactions must be that the balance of the collateral address is < 250 000 STRAT.
  • Merkle proof(s) for the movement transaction(s) showing that they are included in a block at the same or higher height than the funding transaction.

A light node should be able to interrogate a peer node about the perceived status of one or more masternodes. If the peer being interrogated is also a light node, it will only be able to pass along proofs it already received and stored from the full nodes.
Funding transaction
The funding transaction for a masternode is the transaction that assigns the 250 000 Stratis collateral to a given address. It is recommended that only a single transaction output be used for this, to keep the size of the proofs communicated between peers to a minimum.
There is also naturally a possible gap between the block height of the funding transaction and the block height of the registration transaction, during which some fund movement may have occurred. This should not be a problem, as full nodes will evaluate the solvency of the masternode and determine whether to propagate its registration to other peers via the inter-node protocol.
Some possible attack/DoS vectors
The most vulnerable portion of the network are the light nodes. The proof mechanism therefore needs to be robust enough to allow the light nodes to participate in policing the masternode registrations without having the entire blockchain available.
The masternode operators also need to be protected from rogue full nodes attempting to stifle traffic to particular masternodes by censoring their registrations. This is mitigated by the decentralised nature of the Stratis blockchain. It is only required that a sufficient number of honest nodes participate to minimise or negate the impact of rogue nodes, as the registrations will percolate through the network via the blocks & inter-node protocol. A rogue full node cannot generate a fake proof of non-compliance, as the Merkle proofs will fail to be validated.
Masternode operators may generate copious registration transactions (i.e. spam) in an attempt to sway client nodes to use their server. This is mitigated by a rule that a client node will only keep the most recent valid registration for each known masternode, so spamming the network does not result in an increased likelihood that a client will select a particular masternode server.
It is important that a masternode operator avoid moving their collateral funds in such a way that they inadvertently provide an avenue for full nodes to construct a non-compliance proof. If funds need to be moved it is recommended that an entirely new address be used & a new registration performed. This will naturally cause the previous registration to be invalidated and removed from the caches of nodes on the network. The new registration will, conversely, be cached and used going forwards.

Stratis Masternodes Alpha Release

Today we have reached another significant milestone in our roadmap as we release our Stratis Masternodes product.

This major release includes the following:

  • A live running Masternode running on Microsoft Azure.
  • The Masternodes fully support our new Service Discovery Protocol and are currently configured to run our Breeze Privacy Protocol service.
  • A new version of the Breeze Wallet with Breeze Privacy Protocol (powered by TumbleBit) that features the Masternode Client Discovery Protocol.
  • The Masternode technology implements a collateral verification feature that requires the node operator provide 250,000 Strat to be held in a watched address on the blockchain. This requirement helps to incentivize the supply of appropriate resources required to operate the network.

These technologies work together to solve the problem of providing useful services on the network where Masternodes host and advertise their services on the blockchain while client applications use the blockchain to discover and connect to those services.

This delivers a robust, trustless, decentralized advertisement and discovery mechanism that is resistant to manipulation or censorship.

Our first such service, the Breeze Privacy Protocol, is available as a Masternode service today with more exciting Masternode services coming soon.


Download a version of our Breeze Wallet with Breeze Privacy Protocol (powered by TumbleBit):

Masternode Source Code on BreezeHub:

Look out for more information today including a detailed post and a technical paper with full details of how the technology works.

Breeze Beta Release

The beta release of the Breeze wallet is now available and represents a significant milestone in our development roadmap schedule.
There has been extensive work undertaken since the alpha release in order to move the Breeze wallet to the beta status. A key development since the alpha release is the Breeze wallet now supports two currencies running side by side: Stratis and Bitcoin respectively.
The release encompasses user interface enhancements and provides updates with regards to stability.
Existing Breeze Wallet Holders
There have been a number of updates, therefore, any users which have an existing Breeze wallet will need to perform the following steps before starting the app:

  1. Make sure you have your mnemonics and your passwords for these wallets

2. Delete all the files in the following folders:
%AppData%\StratisNode on Windows or ~/.stratisnode on MacOS and Linux

  1. Choose wallet recovery on start-up and use your mnemonic and password

Breeze Wallet Download
The Breeze wallet is available to be downloaded from the below link:

Stratis Blockchain Upcoming Expos

Stratis is set to take the stage at a number of upcoming conferences as we showcase our blockchain offering and latest product developments.
Over the next six months, Stratis will be attending and speak at a host of bitcoin and blockchain conferences. Starting with the Blockchain Expo at Santa Clara in Silicon Valley on the 28th November to 30th November, we will be attending and be exhibiting our technology.
As strategic partners of the Expo, we will be on hand throughout the three days, offering the opportunity for investors to discuss product developments, as well as one-on-one conversations with Stratis employees.
In the new year, we will continue to showcase our blockchain offering, attending the Bitcoin Super Conference in Dallas, Texas which is from the 16th to 18th February 2018. We will be discussing our turnkey solutions and how we utilize C# and .Net development frameworks to provide quick and easy blockchain-based applications.
On the 18th April to 19th April 2018, Stratis will be in attending the Blockchain Expo in London, Olympia. More detailed information will be provided about the Expos closer to the time.
Finally, we are excited in ramping up for a very busy period with major technology releases and attendance at key Blockchain Expos.

Stratis Roadmap 2017-2018

Today we would like to share with you our Stratis Roadmap 2017-2018.
We are excited to highlight our achievements during the current year and wish to provide an insight into our future product roadmap. Among those completed milestones in our product development cycle are as follows:

  • Stratis Full Node
  • Breeze Wallet with Breeze Privacy Protocol (Bitcoin Alpha testnet)
  • Breeze Wallet with Tumblebit (Bitcoin alpha Testnet)
  • Stratis Identity App

We will continue to communicate updates of the roadmap deliverables via a series of blogposts. The roadmap provides a good insight into the bright future of Stratis as we move into Q4 and we look forward to a successful 2018.
Thanks for your support.

Breeze Wallet with Breeze Privacy Protocol (Dev. Update)

Breeze Wallet with Breeze Privacy Protocol Released

(Powered by TumbleBit and Stratis Blockchain Technology)

Breeze Wallet with TumbleBit has a new name: Breeze Wallet with Breeze Privacy Protocol. Breeze Wallet will be the first wallet of its kind that will not only provide a fully featured crypto wallet, it will also include a unique coin shuffling and swapping technology. The protocol takes small denominations of bitcoins from a source wallet in Breeze, shuffles and swaps the coins with others, and then transfers those coins to a destination wallet.
The process is powered internally by TumbleBit to add privacy to your coins. It is likely to be used by discerning individuals and businesses that accept cryptocurrencies and do not want to leave traces that may reveal their customer and supplier lists.

Alpha Available Now

Stratis Internal and select community testing of Breeze Wallet with Breeze Privacy Protocol is complete and we’d like to offer you, our community, the opportunity to take a look, download and try the Alpha. The new wallet is available now for Windows, Mac and Ubuntu. Download details are available here: ( ). This release runs only on testnet and is an alpha/experimental release.
The work has focused on developing a smooth user experience as well as deep integration into the Stratis Blockchain Technology. There is no longer a need to run BitCoin Core alongside Breeze Wallet when using the protocol to shuffle and swap coins. That functionality is now completely provided by Stratis Blockchain technologies. This work moves us closer to our vision where MasterNodes provide discoverable services – such as the privacy protocol – to the Stratis network in a decentralized, scalable, trustless way.
We’d like to point out that the Breeze Privacy Protocol is a CPU intensive service and although we will be providing a test server, places on the server are limited and part of the goal of the community alpha is to stress the server. Please do not be disappointed if you cannot get on this server – we are working with our community to add more server power. If you are interested in running a server please get in touch.
We’d like to also extend a warm thank you to our dedicated community testing team who have done an excellent job helping to get Breeze and the core NTumbleBit technology to a solid alpha release state. A special mention to badass, zomertje, sigma, demon and kabbie. And lastly to all our capable development team across all functions. Last but not least thanks to Nicolas Dorier and the TumbleBit dev team from MIT. This was a team effort and you guys are awesome.

Stratis Identity Proof of Concept Public Beta Release

Today we are proud to release the first Stratis Platform Proof of Concept – The Stratis Identity App. In a joined effort between Stratis and the Escalate Group, we have assembled the first building blocks of many possible applications on the Stratis blockchain.
Built on top of the Stratis Platform infrastructure this proof of concept showcases personal and corporate identity management capabilities on the Stratis blockchain to deliver a real use case for users to attest their identity on an immutable ledger and share that data with others via social networks.
With the Stratis Identity app, you can validate an identity, or other documents, once. After that, you just share the attestation, not the document itself. This feature can help shorten business processes and avoid exposing customer data.
Proof of the information you confirmed with a social login provider, like Microsoft, will be written to The Stratis Blockchain. No actual personal information will be exposed without your explicit permission.

Leveraging Microsoft’s Enterprise Solutions

On this initial beta-release, the Stratis Identity app tightly integrates into Microsoft’s Identity and Cloud Management solutions (Azure B2C Active Directory) and the Xamarin framework to provide an additional blockchain layer of trust to identity certification. For the first time, a blockchain project showcases this deeply integration with key enterprise tools such as Microsoft’s Azure Active Directory B2C which provides unparalleled customer identity and access management in the cloud.

By integrating in Azure Active Directory we open the doors for the Stratis Platform to be the blockchain of choice when implementing blockchain based identity solutions for large companies and enterprises. Among the benefits from such integration, we can mention:
• Use social accounts, emails, custom IdPs
• Support all platforms and open standards
• Customize your customers’ identity experience
• Integrate with CRM and marketing databases
• Use a white label solution, promote your brand
• Meet your security, scalability, and compliance needs
The development with the Xamarin platform, provides a great opportunity to demonstrate versatility for multi-platform deployment when developing blockchain apps in the Microsoft environment.
Additionally we have combined Graph API, Application Insights, Microsoft Teams and Visual Studio Team Services to dramatically improve the development and deployment cycle towards a fully functional application.
In summary the Stratis Identity App will be a great first experience for developers to learn about integrating existing enterprise tools with the different Stratis modules that could help them bring enhanced trust to social interactions with the help of blockchain technology.

How it Works

For this Beta release, the App is Android only, with an iOS version to be released shortly. After you download the App, sign up to Stratis Identity Alpha using your existing social logins. Currently, supported providers include Microsoft, LinkedIn, and Google. More sign-up options are already in development. You can find a full How to Guide here:
For developers, we are providing documentation and access to our Github page (eventually the project will be fully open-sourced).

About Stratis Proofs of Concept (PoC)

A key element of our strategy is the development and release of proof-of-concept apps that can be customized into full blown products and used as building blocks for developers in the C#/Net environment. The idea is to show and tell how simple it is to build blockchain apps using the Stratis Platform, while providing basic elements to get projects started fast.
One key element in this vision, is to also establish alliances with technology oriented business entities in different verticals, that can provide their market expertise and help refine our solutions for different business activities, co-develop licensable technologies and provide customer support.
On this line of thought, we think the Stratis Identity PoC could become a key element in developing opportunities through Microsoft channels, partners and customers that are currently exploring the different blockchain options available in the market. Also, this will become an invaluable tool to show and tell to potential clients how actual decentralized blockchain apps work and how they can improve existing business processes.
We expect to continue delivering several proof of concept apps, like the one announced above in partnership with Earth Twine and other organizations that are finalizing the onboarding process.

Calling Up Developers

We want to extend a particular invitation to C#/.Net developers to get access to the tools and share their experiences with us. If you are interested in furthering your learning in blockchain, we want to invite you to join the Stratis Academy.
You can contribute to the Stratis identity project on GitHub and also you are more than welcome to propose new ideas or concepts you would like to test.
We look forward to help you solve any issues and provide you with tips to get you started developing your own blockchain based apps on the Stratis Blockchain.
Acknowledgement: Thanks to Cesar castro and the escalate Group, our developers and all the testers that helped during the process. Also thanks to a stratis community member for this great walk through video:

World’s first seafood dedicated blockchain

Earth Twine partners with Stratis!
The first implementation of blockchain technology for the seafood industry, the second largest traded commodity on Earth! “The global fish & seafood market had total revenues of $158.1bn in 2015 …” – Wise Guy Reports
This partnership creates the first dedicated blockchain system for origin data and tracking for the international seafood industry –The Earth Twine-Stratis Platform. This platform combines collaborative technologies (Earth Twine, SPARKL, Stratis), and will provide the means for tracking mandatory data for IUU compliance. (Info below)
As seafood industry professionals, the EARTH TWINE team has created a solution born of the industry itself. In collaboration with The Association of International Seafood Professionals (AISP), Earth Twine has established the means for inclusive representation of all sectors of seafood professionals. Earth Twine’s comprehensive understanding of the unique seafood supply chain, and the Code of Federal Regulations (CFR’s) has led to the development of its solution that provides a product for all stakeholders of the supply chain, small and large.
SPARKL enables our multiple tracking applications and systems to work collaboratively within legacy environments. This fuels the platform to orchestrate multiple structures and will reduce complexities in the seafood supply chain.
Stratis will establish distinct, dedicated blockchains, tokens and applications to integrate Earth Twine’s global seafood tracking solution onto the blockchain. This rapid innovation and development will transform the seafood industry by introducing unprecedented levels of trust, collaboration and settlement, in turn, increasing productivity and sustainability.
Starting January 2018, the Seafood Import Monitoring Program requires specific data related to seafood imports to be provided electronically to U.S. Customs and Border Protection. For many years, illegal, unreported and unregulated (IUU) fishing and/or misrepresented seafood have affected global seafood markets. The Earth Twine-Stratis Platform will significantly help solve the NOAA Compliance Standards (who, what, when, where) that will confirm and validate the information as proof positive.
A fundamental partnership for Earth Twine is Greenberg Traurig Law, the largest law firm in the USA. The Earth Twine team benefits from Greenberg Traurig Law’s international presence, industry specific knowledge of blockchain innovation, and its evolution and emerging regulations around cryptocurrencies by the US Securities and Exchange Commission (SEC).
“Our goal is confirmation and compliance of product”
-Earth Twine
“We Make BlockChain Easy For You”
– Stratis Platform
For enquiries contact:
Earth Twine, Inc.
[email protected]
Stratis Group Ltd.
[email protected]


Bitcoin Privacy is a Breeze: TumbleBit Successfully Integrated Into Breeze

Development Update

This week the Breeze development team reached the final major milestone in their development of the Breeze Privacy Protocol, which is the Breeze implementation of TumbleBit.
This development has allowed us to start seeing considerable volume of transactions protected by Breeze’s Privacy Protocol, the architecture developed by Stratis, which provides a safe way to anonymize cryptocurrencies.

The Breeze Wallet is now fully capable of providing enhanced privacy to bitcoin transactions through a secure connection. Utilising Breeze Servers that are pre registered on the network using a secure, trustless registration mechanism that is resistant to manipulation and censorship.
Breeze Tumbler is expected to be utilized in commercial scenarios including businesses that do not wish to reveal their customer or sensitive data for competitive reasons.
Finally, we want to share with you the latest progress on the Breeze wallet UI, so that you can start getting a feeling of the great things to come from our team.

Follow and contribute to the Breeze Wallet project: BreezeHub and look out for an alpha release of this exciting product coming soon.

BreezeHub is Here

This note is a contribution from our new team member Carlton Pringle (@carlton on Slack). One of the key missions in Carlton’s new role as Breeze / Tumblebit development Project Lead, is to coordinate the communications about progress in this exciting technology to internal teams, developers and the public at large.
As he gets more familiarized with the vision and accomplishments of our development team. He will be responsible for providing all the relevant updates and streamlining communications from the Breeze / Tumblebit team to our developers and general community.
Welcome Carlton and we wish you success in your key role, and without further ado… here is his first Breeze Update.

Facilitating Breeze Development Access

We want to simplify access and visibility for the Breeze Project, as we expect many peer reviews and collaborators to this exciting project now and in the future. To this aim we are launching the GitHub open source projects for Breeze / Tumblebit development under the auspices of Stratis.
BreezeHub hosts our TumbleBit Server Experimental build and showcases the Stratis secure node advertisement protocol, which will be utilized by the Breeze wallet to locate Breeze Tumblebit servers without the need for a centralized list. This is therefore a registration mechanism resistant to manipulation or censorship as it does not require trust in third parties.
Check out BreezeHub where you’ll find all our work on the TumbleBit Protocol in one place including code, documentation and all the latest info on the TumbleBit Server Experimental Build.
BreezeHub includes full instructions to walk you through the TumbleBit server installation. Give it a try and please reach out to our team of developers on Slack with your bug reports, suggestions, and comments.
Expect to see lots of activity on BreezeHub – including more incremental releases – as our vision of this exciting technology takes form.
BreezeHub on GitHub

BreezeHub is hosted on GitHub and can be found at
Acknowledgements: Thanks to @zeptin and @dan.gould for their hard work on this and thanks @jeremy for your support.
TCP Server
This week also, Nicolas Dorier wrote a custom core server to replace the default Kestrel implementation that runs in core on Windows, Linux and OS X. This lightweight tcp server will be used within the TumbleBit Server in place of the previous http+json ptotocol to improve anonymity for TumbleBit users. It can be found here.

1 2 12 13 14 15
Privacy Settings
We use cookies to enhance your experience while using our website. If you are using our Services via a browser you can restrict, block or remove cookies through your web browser settings. We also use content and scripts from third parties that may use tracking technologies. You can selectively provide your consent below to allow such third party embeds. For complete information about the cookies we use, data we collect and how we process them, please check our Privacy Policy
Consent to display content from - Youtube
Consent to display content from - Vimeo
Google Maps
Consent to display content from - Google
Consent to display content from - Spotify
Sound Cloud
Consent to display content from - Sound