It's been a busy week for everyone at RTrade, we've been putting the finishing touches on our first large scale mining farm/datacenter, and have been hard at work on TEMPORAL. In a small time frame there has been quite a lot of work done both on the development, and business end of things, mostly related to marketing, web site, information, etc.. However, we will save that for another blog post as this one is just about those sweet, juicy technical details.

If you want to skip the distilled technical details, and get right down to the meat of it, check out our GitHub https://github.com/RTradeLtd/Temporal

Private IPFS Networks

---

Much of this week has been spent on building out the Private IPFS network support for TEMPORAL. After signing up with TEMPORAL, a user has the option to configure Private IPFS Network support by providing the list of Bootstrap peers, and a SWARM key allowing us to join your own private network. Or, should you not want to be responsible for the primary upkeep of the private we can be the Bootstrap peers, and primary nodes on your private network, allowing you to rest peacefully at night knowing that your network is up and running within our secure facilities. After configuration, using the exact same API calls as before, a user can decide whether or not to upload a file, or pin content to the public IPFS network, or to any one of their configured Private IPFS networks. All functionality available to the Public IPFS network (PubSub, IPNS, etc..) is available for all Private IPFS networks as well, however they have their own API calls. There is no set release date for this feature, however we will be rolling out an IPFS bridge, that will allow users to efficiently transfer content between their Private IPFS networks, and the Public IPFS network.

Currently Private IPFS Networks on TEMPORAL have no cluster support, but that will be coming very shortly, most likely within the next week. After that, the Private IPFS feature set is pretty much all fleshed out for our version 1 release, and all that will be left is optimizations, and bug fixes.

IPNS

---

There were some outstanding issues with our IPNS implementation, preventing IPNS records from being signed by non-default Private Keys, and non-default settings. This has been patched with a pending PR that Rtrade has submitted to the upstream go-ipfs-api repository, but in the meantime we are using our own fork. Finally, users can create IPNS records using any private key that they have generated through our system. Record publishing has been tested on Private, and Public IPFS networks with great results. The IPNS feature set isn't quite complete, and is about 50% of the way done. The main work that's left to do is integration record validation, and record republishing.

We've decided that for our version release, we will only be officially supporting DNSLINK record creation through AWS Route 53. Depending on user demand, we may roll out support for additional Name Service Providers (Cloudflare, etc...) so if there's one that you would like to use, please let us know in the comments below and we can look at integrating it for V1.

TEMPORAL License

---

Due to our current usage of the go-ethereum library, TEMPORAL is licensed under LGPL-3.0 however, this isn't super desirable, and we are aware of mixed opinions about this open-source license. We are currently reviewing the license with our lawyers to find the best fit for RTrade, Temporal, and everyone else!

What's Next For TEMPORAL?

---

After all the features of IPFS Public and Private networks have been completed, we will then begin work on a long awaited web interface for our first product that utilizes TEMPORAL, which will be a cloud storage service backed by Public and Private IPFS Networks through TEMPORAL! While the web interface is being designed, we will continue to build out the TEMPORAL software suite, and start building out integration of Ethereum SWARM networks primarily for use with the Ethereum main net, but other ice-cream based block chains will be targeted in some capacity.

Another big next step for us at RTrade is gearing up our social media presence, and community outreach. Community is absolutely key to a thriving project, so we will be making a detailed post on that in the coming weeks.

As always, if you want to see any of our other work, hobby projects, and such feel free to check out our main GitHub organization, or join us on Telegram!

• https://github.com/RTradeLtd
• https://t.me/RTradeTEMPORAL