Kendall Cole

Not yet (that I’m aware of). cc @vgrichina

Check this PR for more context: https://github.com/near/near-api-js/pull/256

Linked Wallet issue: https://github.com/near/near-wallet/issues/1148

@vgrichina Thoughts on this? We currently recommend installing shell globally, which makes the folder specific behavior kinda confusing

If I'm understanding this correctly, this is when the user lands on `/sign` without any URL params? Ideally, we would redirect the user back to the app they came from...

> Source code of the contract is not stored on chain. Right, which is why contract verification will be pretty centralized, similar to [etherscan](https://etherscan.io/address/0x2af47a65da8cd66729b4209c22017d6a5c2d2400#code)

It's opt in, so the default will be "unverified". Depending on how much we want to encourage devs to reveal source code, we could make the warning pretty prominent. Etherscan...

This seems like a good one to bounty out (the UI, at least)

I think the best solution for the dashboard is too remove TXs entirely. Users should not expect to see there transaction on the dashboard, or even TX list page, as...

@vgrichina Does it make more sense to handle Borsh directly in Explorer, or to use a nearlib helper function? And do we still think hexdump is the way to go?...