@Canageek Probably the best you could do would be to have the server periodically hand you a certificate authenticating your character's state (including timestamp, code version, etc.), which you could then hand to another server -- and that other server may or may not decide to accept it based on whether the operators trusted each other.
This would work even if you *later* had a falling-out with the server operator.
@varx That is what I was thinking of, yeah.
I was also thinking that if you used a modular format, sort of like how D&D modules work at conventions, it would be easy to track and verify things.
so if they have a certificate from the Dungeon of Bob, the dungeon of Bob would have a publicly known signature and list of things and amounts it can give out, so you could verify that the cryptographic signature of the version of Dungeon of Bob they played matches the known list