hyperledgendary / fabric-contract-api-rust Goto Github PK

When implementing DataType for a particular type, none of the methods support returning a Result. This means that any type (asset) implementing DataType won't necessarily work with generic fields if the methods implemented in those fields require a Result.

For example:

pub struct MyAsset<T: SomeTrait> {
    uid: String,
    value: T,
}

impl<T: SomeTrait> DataType for MyAsset<T> {
    fn to_state(&self) -> State {
      State::from((self.uid.clone(), self.value.do_something()?))
    }
}

In this example, do_something() returns a result which isn't supported by the method on the DataType trait.

This may be by design to require anything that implements DataType to match State as closely as possible. Otherwise, it's unclear what kind of flexibility one has here.

fabric-contract-api-rust cannot be build by cargo build --target wasm32-unknown-unknown, there are 160 problem
I build the project by https://hyperledgendary.github.io/fabric-contract-api-rust/guides/getting-started.html
is the project still be maintenanced ?

Incorrect number of arguments should fail properly if supplied.

When a innvocation comes in from the peer, waPC is called with the 'invokeTransaction' command; the payload is a protobuf that is decoded. It's then passed directly onto the ContractAPI for final routing and processing.

To make it easier to interact with different implementations it's worth looking into how to separate out this into it's own crate.

If a namespace is not supplied with the name of the transaction function we need a default.
(eg myTransaction rather than myContract:myTransaction

This should be the first one in the list of registered contracts.

I am following the instructions on
https://hyperledgendary.github.io/fabric-contract-api-rust/guides/getting-started.html

I get to the part
docker exec humboldt.cli mknet.sh

2023-01-04 12:51:27.253 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
Error: got unexpected status: BAD_REQUEST -- error applying config update to existing channel 'smallchannel': error authorizing update: error validating ReadSet: proposed update requires that key [Group] /Channel/Application be at version 0, but it is currently at version 1

This issue is for noting queries/questions regarding the shape and details of the Rust API
Please add your views.

• ClientIdentity: what fns does this really need? X509 certificate for example
• String or &String or str or &str in the fns?
• Iterators: confirm that these are idiomatic
• Timestamp: best rust type for a point in time
• Ensure visibility of fns is correct, don't expose internals.

Support retrieve state from the collection.

@mbwhite Is this project still being maintained? Is there an issue in starting new projects with this?

• Need to be able to enable and configure logging inside the Rust library

• Logging for both the Rust code and also the user's own contract code

• All logging to be routed via waPC log command

• Consider an entry point in https://github.com/hyperledgendary/fabric-ledger-protos/tree/master/protos

Current chaincodes can enable this by APIs available in contract functions, hence could be controlled by access control.. i.e. can't attempt denial-of-service attack by random person enabling trace.

I recently starting getting a number of errors when attempting to execute wasm chaincode built with Rust v1.46.0. Not sure what is causing these import errors.

12 link errors: (1 of 12) Import not found, namespace: __wbindgen_placeholder__, name: __wbindgen_describe (2 of 12) Import not found, namespace: __wbindgen_placeholder__, name: __wbg_self_1b7a39e3a92c949c (3 of 12) Import not found, namespace: __wbindgen_placeholder__, name: __wbg_crypto_968f1772287e2df0 (4 of 12) Import not found, namespace: __wbindgen_placeholder__, name: __wbg_getRandomValues_a3d34b4fee3c2869 (5 of 12) Import not found, namespace: __wbindgen_placeholder__, name: __wbg_getRandomValues_f5e14ab7ac8e995d (6 of 12) Import not found, namespace: __wbindgen_placeholder__, name: __wbg_require_604837428532a733 (7 of 12) Import not found, namespace: __wbindgen_placeholder__, name: __wbg_randomFillSync_d5bd2d655fdf256a (8 of 12) Import not found, namespace: __wbindgen_placeholder__, name: __wbindgen_is_undefined (9 of 12) Import not found, namespace: __wbindgen_placeholder__, name: __wbindgen_object_drop_ref (10 of 12) Import not found, namespace: __wbindgen_externref_xform__, name: __wbindgen_externref_table_grow (11 of 12) Import not found, namespace: __wbindgen_externref_xform__, name: __wbindgen_externref_table_set_null (12 of 12) Import not found, namespace: __wbindgen_placeholder__, name: __wbindgen_throw

Support the create state option in the Collection

When attempting to call Collection::update_state(key, data) against the World state, I get the following error:

Error: endorsement failure during query. response: status:500 message:"error invoking guest: Failed to call the `__guest_call` exported function."

Not sure if the implementation for this function is incomplete or if this is a legitimate bug. Looks to be generated from the wapc-guest crate.