Closed HashWarlock closed 2 years ago
Name | Link |
---|---|
Latest commit | db3963d08a4ed858300f421df54314416b4f6b2e |
Latest deploy log | https://app.netlify.com/sites/substrate-website/deploys/630d417c2945080009fdb503 |
Deploy Preview | https://deploy-preview-295--substrate-website.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
@SBalaguer Thank you for the feedback. I'll make appropriate changes. On the second point:
'Infrastructure' category is for teams that are building infrastructure across chains, think about Wallets, Indexers, etc. It would not apply to Phala, please leave it as 'Smart Contracts'.
One of our key distinctions for our Phat Contracts are that they are not Smart Contracts. This is due to them running in our secure enclave off-chain workers and with access to the Internet through HTTPS requests w/ near 0 latency via Queries. Some of the functionality we can provide include:
Another Dapp we provide is SubBridge which is an XCM Router + ChainBridge for token transfers from EVM chains like ETH to Khala parachain & route to parachains we have an HRMP channel open with. This is where we feel that our project lies under the Infrastructure services or requires a new category like "Cloud and Off-Chain Computation" as "Smart Contracts" tends to relate to On-Chain computation which is limited when it comes to scaling computation & latency. What are your thoughts?
Updates based on feedback. Let me know if any other items need to be addressed.
@HashWarlock do you happen to have the logo in better quality or SVG?
Added a better quality SVG.
Request to make changes to Phala Network information and logo to reflect current status of the project.