🔥 Helios + GCScript + GCFS 🔥

loading...

GCScript:

GameChanger Wallet uses a dapp connection stardard than enforces code transparency, auditability and open-source colaboration. Differently from CIP-30 standard, dapps delegate the processing of code interfacing users wallets inside GameChanger Wallet. This very powerfull Domain Specific Language is called GCScript and is pure JSON packed on URLs, ready for web integration, requiring no further Cardano dependencies to work with it.

Multi-device support:

This powerfull design principle has many benefits, one of them is to provide desktop, mobile and offline support out of the box where no other current standard can do it properly without extra development effort, limited features or serious UX issues

Privacy Preserving:

This enhances privacy because dapps no longer need to request user specific data such as balances, utxos and addresses to construct transactions and interact with Web3 applications. This has never been possible before!. Also since 2021 we offered this model to avoid delegating UTXO coin selection and management to dapps as it is a terrible practice!.

Auditable:

This enhances auditability because Cardano low level code or data no longer need to be the only way to communicate, instead of binary/CBOR you can work with human readable GCScript, code ready to be interpreted, reviewed and cloned. Also GCScript is designed in such a way it can be presented to end users as coloured permissions on UIs meaning it can be also audited at certain level even by end users, something impossible until today with any other development language (Marlowe only solves smart contracts, this goes far beyond that limited scope). Check how you as a user can audit ALL INCOMMING AND OUTGOING COMMUNICATIONS to the wallet, everything is open by design. Even internal wallet functions are open sourced this way for you to audit and clone the code.

Now imagine if we start storing this GCScript code on-chain, and we import third party code to colaborate and build a greater ecosystem, making code perpetually available for everyone

Well imagine no more. This dapp uses GCFS, our On-Chain File Storage Protocol on Cardano to store GCScript code that is the actual interface to the protocol this dapp uses to work.

So the wallet loads third party code libraries stored on on-chain files and the dapp frontend only takes care of parameterizing their execution. You can view the imported code on any dapp connection on Advanced -> Full Code

Interoperability and Colaboration:

This enhances interoperability and open-source colaboration because the on-chain stored GCScript can be imported and combined freely, openly to create upon it, with easy to call interfaces using JSON parameters as "function arguments"

Enhanced Auditability:

To ilustrate the importance of this design principle, I've installed a backdoor on the smart contract. The code maintainer injects a key hash to became allowed to withdraw any locked deposit.

Open-source is not enough to keep us safe. Deployments and their parameters should be open as well to prevent all kind of attacks

Because the smart contract Helios code and the GCScript embedding it reside inmutable on-chain we can spot the exploit and nobody can hide it from us nor modify it to cover any tracks

If we were working as we currently work on Cardano, with low level compiled CBOR and frontends and backends centralizing the parameterized execution of open source code, it would be much harder to audit and only experts on advanced Plutus de-compiling could detect such a threat

• Frontent breaking changes?
• Dapp developer team gone?
• Censored dapp?
• Want to interoperate with any protocol?

When you get rid of processing transactions on opaque centralized backends and you work on client side storing protocol interfaces on GCFS your users can rest assured the minimal code required to recover their locked funds will be forever available on-chain, no matter what happens with dapp frontents, teams, censorships, you name it. You just need to pass the right parameters to the protocol interface and the same GCScript code the dapp calls will be runned. You can use our IDE for this, and for all the development process.



If you support our proposal, you will also be able to host frontends stored fully on-chain, along with their protocol interfaces, having 100% stored on-chain dapps on Cardano. We started with the hardest part, the interoperable protocol layer that took more than a year of development, frontent hosting is the last missing piece.