If someone tells me "donate to my kickstarter-style contract!" I want to examine the code of that contract to make sure it works as advertised, but it's not easy to understand the compiled bytecode. It would be very easy to scam people who trust your bytecode.
Has anyone proposed solutions to this problem?
If Serpent etc. has "repeatable builds" (e.g. the same input always produces same bytecode) that would make it possible, though not easy, to verify that someone's Serpent code was indeed compiled into a given contract.
Or should someone could start a site which analyzes contract bytecode and says "This matches github.com/foo/kickstarter-contract v. 12.04.32" or "This appears to be Bitcoin-Hedge 12.34"?