Open-attestation on the Polygon network

[gsyndromes]

Hi! In light with the many blockchains popping off and their reliability ever-increasing with increasing user bases, it would be super helpful that open-attestation moves along with the innovations and allow its functions to operate on other blockchains as well. I hope to be able to see all functions of Open-attestation being supported on the polygon network due to the significantly lower gas fees available on polygon. It makes it easier for projects to onboard open-attestation as well if the functions are is blockchain-agnostic.

[Nebulis]

As I mentioned, it will be nice if you could give us more information about how open-attestation could support polygon.

You are not the first one to request to support a different blockchain. But definitely, if we have to explore every options, we won't go anywhere.

[gsyndromes]

thank you for the example! It helped solved my import problem. by the way, apparently, typescript does not play well with the top-level await as per the readme. It throws this error
test.ts:20:20 - error TS1378: Top-level 'await' expressions are only allowed when the 'module' option is set to 'esnext' or 'system', and the 'target' option is set to 'es2017' or higher.

20 const fragments = await verify(documentRopstenValidWithCertificateStore);

which can be hacked through by replacing with
const fragments = async () => { await verify(documentRopstenValidWithCertificateStore); };

EDIT: the typescript version I am on is
"typescript": "^4.3.4"

[gsyndromes]

however, upon running it, i am seeing this error instead, do you have any ideas why?
Object.defineProperty(exports, "__esModule", { value: true }); ^ ReferenceError: exports is not defined

[Nebulis]

@garysyndromes Ryan, who helped you, manage to answer my question: we are able to use oa-verify directly with polygon without any changes.

That means that oa supports natively polygon. However, OpenCerts and Tradetrust do not (we need special providers). It's a matter of configuration.
If we want Opencerts and Tradetrust to support both Eth / Polygon, we will need to work on OA to allow them to decide where to perform a verification.

We don't think that Polygon is mature enough. We don't plan to do modifications now. However, we will keep an eye on it and if the time comes we will do it.

There are things that can be done for now:

• Nothing prevents you to create your own platform that supports Polygon or Eth (Or both, considering Infura supports both)
• We can already start to think about how to integrate with different providers. Feel free to join the conversation

[gsyndromes]

Can i clarify what do you mean by opencerts and tradetrust needing special providers?

[ryanseee]

@garysyndromes what laurent meant was that, if you take a look at https://www.tradetrust.io/, https://dev.www.tradetrust.io/ and https://rinkeby.www.tradetrust.io/, they are all running on different Ethereum networks. so to include Polygon Mainnet or Mumbai Testnet necessary configurations would need to be done to support them on the different projects/platforms.