v2.0.4rc1

queue: fix failing queue test

v2.0.3

See CHANGELOG-V2 for release notes.

v2.0.2

See CHANGELOG-V2 for release notes

v2.0.1

See CHANGELOG-V2 for release notes.

v2.0.0 - Production Release

TODO: add detailed release notes

Beta Release #7 - The Final Hour

This is the last beta release before our production launch.

Release Highlights:

• Misc bug improvements
• Misc performance improvements
• Drastically improved test coverage
• MASSIVE improvements to TLS connection security
  • TLS 1.1 minimum version
  • Supported ciphers are
    • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
    • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
    • TLS_RSA_WITH_AES_256_GCM_SHA384

Beta Release #6

The bulk of this release is centred around a massive overhaul to our messaging system which leverages RabbitMQ. As of this release, we are now capable of processing 10x the amount of tasks that we were able to before. There have also been some slight optimizations to the internal API system, allowing for faster API response time when interacting with the messaging system which compromises about 75% of the API calls. During testing, API response time had an average of 2ms-3ms faster.

The IPFS keystore has now been migrated over to our krab keystore, allowing for storage of IPFS keys in encrypted volumes, along with cleanup to the actual API routes themselves, allowing for a more condensed, and readable API call paths.

Tasks which have had concurrent processing capabilities increased:

File upload
Pinning
Key Creation
IPNS Publishing

Due to the way we handle PubSub, and non queue based tasks, they weren't limited in the number of concurrent tasks we can process. The test coverage as well has been increased by 10%, with more improvements to test coverage on the way.

Beta Release #5

The biggest highlight of this release is private IPFS network management, which now finally allows proper use of private networks via the API calls that were already in place. The MVP of TNS is now available as well, with some light usability facilitated via the API. The rtfs package that we use to facilitate communication with the IPFS network, as well as key management has been extracted into a separate library. We also introduced the ability for users to export their IPFS keys as mnemonic phrases.

This is also a very big point in Temporal's life span, as the code base has reached over 2000 commits, and as of this release has 55 stars on github! This wouldn't be possible without the amazing team at RTrade, and all the open source projects that Temporal uses, and have been key in laying a solid foundation.

Special thanks to @bobheadxi for the wicked private network integration. And pseudonaut for the stellar web interface work.

Beta Release #4

This is the fourth release as part of our on-going beta test. The changes made between the third release and this one, are strictly optimizations, and bug fixes. Included, are upgraded IPFS dependencies to version 0.4.18, and upgraded IPFS Cluster dependencies to version 0.7.0.

Beta Release #3

This is the third release of the core Temporal code base as part of the on-going beta which is free to use, and ends December 31st 2018. The biggest feature of this release, is the ability to encrypt files you upload through Temporal to IPFS, before the data ever reaches the IPFS network. This is a huge step forward for privacy enhancement for both Temporal, and IPFS as a whole since it lacks native encryption capabilities. Now you may effortlessly encrypt your files through the web interface or the API using AES-256 bit encryption.

In order to reduce reliance on Temporal and RTrade, we have released our crypto utility in a seperate repository, allowing you to decrypt your files offline, and locally. This is very useful for sharing files across public gateways, since it means that you can share the files you uploaded to IPFS through temporal, without the recipient needing to create an account! They'll simply need to download the crypto tool and use an appropriate password!

This release also includes support for our "Credit" system, which allows users to purchase credit with a variety of different payment methods. For the beta, any time users sign up they are granted an incredibly high number of credits. Should you however wish to try the payment system, it is currently running on the Rinkeby testnet for ETH+RTC payments. However rest-assured the beta will still remain entirely free to use until it is over.

If you are interested trying out the web interface we have a few options:

• Clearnet Web Interface, Stable
• Clearnet Web Interface, Testing ← Recommended, Beta
• I2P Web Interface, No HTTPS ← Experimental, Early Alpha

Preview of things to come:

• Enhanced IPFS Private Network Support
• DASH,XMR,BTC, and LTC payments
• TNS Temporal Name Server