nikitavr/contrak

Contrak helps developer teams track and prove ownership of their smart contracts

contrak's Issues

Consolidate CONTRAK_URL and CONTRAK_API_URL in the CLI

The Foundry example currently requires two env vars as shown here:

But CONTRAK_API_URL is just composed of CONTRAK_URL. I think we can get rid of CONTRAK_API_URL and just derive it from CONTRAK_URL.

Add docs on deploying to Render

https://render.com/

Add language detection and display on deployment card

We had a mockup of the UI for this in this previous commit but it wasn't hooked up to real data

For the commit hash linked to a deployment on Contrak, how do we make sure that points to the actual source code that was deployed?

Currently, we don't guarantee that. It's similar to how tools like Sentry work in that we just read the data from Git when the command is run. I am interested in providing more useful guarantees around this though. Just not clear what the ideal implementation is.

Some suggestions from Telegram group:

1. Put bytecode hash in release tag and push tags to github

Hey one thing that I do is make a release tag on GitHub for the specific deployment commit. You can then point to that release tag as what's been deployed, and if you want to take it further you can hash the byte code and put that in the release tag. Ppl can then verify the bytecode deployed by hashing it and comparing themselves

2. Use commit hash to clone and compile source code and compare bytecode to what's on-chain for the linked contract address

maybe a tool which does "git checkout deployment commit hash" + compilation + a match of the bytecode against what is deployed on-chain could work

Add docs on deploying to Fly.io

https://fly.io/

Maybe look into Fly's sqlite offering that has automatic backups

Fix opengraph preview image

It's currently not using the dynamic data: