Daniel Olano

Payments API will be defined as a wink! program that abstracts Kreivo's payments infrastructure. Let's define what the scope of v1 would be based on payment-pallet current functionality.

Consider using primitives from [`futures_concurrency`](https://docs.rs/futures-concurrency/latest/futures_concurrency)(e.g. `join`, `race`, etc) instead of spawn to keep async code runtime agnostic.

As the Kabocha parachain is quite outdated and requires major changes to its code base, we would advice to re-genesis Kabocha with a brand new code base using a "satellite...

This also seems to relate to the [prize discovery topic](https://forum.polkadot.network/t/a-price-discovering-treasury-proposal/9083?u=olanod) Shawn Tabrizi started in the forum. I'd be interested to integrate something like that with pallet-referenda and allow special kinds...

Related to this, we are exploring adding the feature to pallet referenda to be able to edit a preimage during the prepare period and allow proposers to use that time...

Wouldn't it be enough for a community to configure their approval/support curves with very "optimistic" parameters? e.g. a community with a track with very low required approval and support and...

I think we can make it work with the existing system ;) assuming the proposer votes yes when submitting the initiative and minimum support stays flat at zero or near...

We will evaluate whether we should implement this as a pallet in Kreivo or propose it as an extension to the asset conversion pallet in Kusama AssetHub which seems the...

For *reasons* I need to use this in an embedded context with no std. I see you're hesitant to make changes to this library but I don't see this one...

# API (draft) ## Commands (endpoints) - **`register`** ### Params - `username` - `credentials` ### Input (extra data) ### Output - **`connect`** ### Params ### Input ### Output - **`verify`**...