[MoveosStd] Refactor ObjectRef, allow ObjectRef as transaction argument

[jolestar]

Summary

1. [MoveosStd] Refactor ObjectRef, allow ObjectRef as transaction argument
2. [CLI] verify modules when publishing on the client side.
3. [Example] Refactor simple_blog example via new ObjectRef API.

Part of #1001

1. Anyone can obtain &ObjectRef<T> by ObjectID, and then get &T. This can be achieved through the entry function arguments or context::borrow_object(ctx, ObjectID).
2. Only the owner can obtain &mut ObjectRef<T> by ObjectID, and then get &mut T. This can be achieved through the entry function arguments or context::borrow_mut_object(ctx,signer,ObjectID).
3. If T has both key and store ability, anyone can transfer ownership by object_ref::transfer(&mut Object<T>, address).
4. The module where T is defined can use context::borrow_mut_object_extend to obtain any &mut ObjectRef<T>, and can transfer ownership by using object_ref::transfer_extend(&mut Object<T>, address).
5. Only the module where T is defined can call the object_ref::remove(ObjectRef<T>) method to remove the Object.
6. The object_ref::to_permanent method is provided to drop ObjectRef<T>, but once ObjectRef<T> is dropped, the Object cannot be removed from object storage.
7. Provide to_shared, to_frozen function.

TODO in next PR

1. Rename Object to ObjectEntity and object.move to object_entity.move.
2. Rename ObjectRef to Object and object_ref.move to object.move
3. Implement shared and frozen

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
rooch	⬜️ Ignored (Inspect)	Visit Preview		Oct 27, 2023 3:13pm

[baichuan3]

If an object is transferred to another address, the module where the object is defined can still get the write reference of the object through borrow_object_mut_extend?

[jolestar]

yes