Changelog Notes - V3.2.3-beta
Dec 22th, 2022
Binance Smart Chain
We have introduced the Binance Smart Chain for subscription payments. We have allowed four tokens - USDT, USDC, DAI, and WBNB on the Binance Smart Chain. All the user flow for upgrading to the PRO plan is the same, but you can connect your metamask wallet and select Binance Smart Chain to upgrade to pro and buy bonuses.ting a new instance from the template.
Introducing Reef RPC Node in the Marketplace
We have added Reef RPC node in the compute marketplace. You can now spin up a Reef RPC node with Spheron compute infrastructure at a cost-effective plan.
Reef chain is an EVM-compatible blockchain for DeFi. It is fast, scalable, has low transaction costs, and does no wasteful mining. It is built with a Substrate Framework and comes with on-chain governance. With Spheron compute, you can spin up your Reef RPC node in the decentralized cloud within minutes. We want you to experience the difference. This is the platform where you can finally say goodbye to centralized servers and the fear of losing everything within minutes. We offer you another option to spin your nodes and scale with minimal technical knowledge. We make it easy for you to monitor your nodes and notify you when they are down.
We dedicate a private instance and an IP to your Reef RPC node, improving its security and performance. You can access the best of both worlds, cloud and dedicated decentralized servers.
Ready to spin your next Reef RPC node? See how you can spin and manage your Reef RPC node on dCloud in seconds with Spheron powered by Akash Network.
Spheron IPFS Gateway
With this release, we have deployed our own IPFS gateway. Your Filecoin and Pinata deployment will be uploaded to IPFS via our gateway. They will also be pinned by us (On top of other providers you choose) for continued availability.
For serving the site, we have switched to a subdomain gateway with some notable advantages from the normal path-based gateway.
- The use of subdomain gateways avoids violating the same-origin policy - https://en.wikipedia.org/wiki/Same-origin_policy
- It also supports cross-origin resource sharing - https://web.archive.org/web/20200418003728/https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#The_HTTP_response_headers
- We now use V1 IPFS hashes which are more future-proof and safe for use in browser contexts. https://docs.ipfs.tech/concepts/content-addressing/#version-1-v1
From now on, you can attach your own custom domain or sub-domain to your cluster instances. Using your custom domains, you will get secure traffic with SSL protocol.
Frontend Performance Boost
We have boosted our overall lighthouse performance by 45% for most of our pages.
FCP (First Contentful Paint), SI (Speed Index), LCP (Largest Contentful Paint), TTI (Time to Interactive), and TBT were the metrics targeted in this release (Total Blocking Time).
Most of the work was accomplished by reducing the main thread work, script evaluation time, and the size of the main JS chunk
- Indexing : We have improved the performance across our API for around 35% by indexing our DB queries.
- Health Check Labels : We have fixed some issues with the health check labels. When your instance is unhealthy, the banner will be red; when it is healthy, it will be green. The labels were also changed from inactive to unhealthy and active to healthy.
Avatar Images larger than 1MB: We have fixed the issue with uploading images larger than 1MB for organization and user avatars. From now you can set an image up to 5MB for your avatar.
Pay overdue: We have fixed the issue that was causing the pay overdue for an organization to fail.
Repository branches not showing: We have fixed the issue because some repository branches were not shown in the dropdown list.
Cluster Docker Tag: We have fixed the issue because the image tag was not used when starting a new cluster instance.
Cluster Environment Variables, Command, and Args: We have removed the max length limit for the inputs.
Organization Creation: we have fixed some bugs that would cause the organization created to fail. Also, we have improved our validation messages so you can know why your organization’s creation failed.
- Upload deployment response: We have added
affectedDomainsproperty to the response of the upload deployment. The
affectedDomainsrepresents an array of the domain that are updated by the deployment.