Stella Cannefax

Here's what you currently see if a module didn't match when publishing. I think we could make this clearer / friendlier, but i'm not sure the best way of doing...

@todd-mystenlabs i don't think _flaky_ is a useful description here. Actually, it works great. Yes, it needs to add version information for the Move compiler. However, we currently don't seem...

> Maybe I missed this in the comments but what's wrong with hashing the generated bytecode? It really doesn't change much between versions. And if its changing often, this is...

OK, all code issue should be updated. had to do some updating to account for recent changes in build APIs as well. Tested the whole flow of publishing the test...

> Also, it's good that this PR has a test plan, but can we check in a test of some kind? > > **EDIT** just to clarify -- I see...

> ⚠️ 🦋 **Changesets Warning:** This PR has changes to public npm packages, but does not contain a changeset. You can create a changeset easily by running `pnpm changeset`, and...

Wikipedia-style disambiguation page sounds fine - show links to the results with a type label beside them for consideration, another way we could allow the search box to be used...

@tnowacki does this mean the entire idea of source verification as you would have on Solana or Ethereum is moot, in your view ?

@tnowacki all that happens on solana / eth side is: There is some way to verify that a given source code folder produces the exact bytecode that is on-chain for...

seems fixed ? i see Console on first reveal, but we do still need to make the hidden ones discoverable