sunshine
sunshine copied to clipboard
sunshine-protocol
Governance + Bounty Platform
so it would be much better if it could just collect the signatures off-chain, aggregate them, and then submit a proof to the chain I heard Celo is doing something...
"...indeed vote are not supposed to be stored but just used as intermediary arithmetic type for getting some result" ~guillaume The sunshine pallets `vote` and `vote-direct` store voter votes in...
```rust pub trait DrainableCurrency { fn drain_to_accounts( from: &AccountId, to_accounts: OrderedSet, ) -> DispatchResult; fn drain_to_accounts_weighted( from: &AccountId, to_weighted_accounts: OrderedSet, ) -> DispatchResult; } ``` We use this logic in...
```rust type EncodedIssue = Vec; ``` but we should prefer that this type has bounded length. What is the longest `repo_owner + repo_name + issue_number` for github's API?
> https://github.com/sunshine-protocol/sunshine-bounty/pull/110#issuecomment-653665806 The CLI input format for `BatchIssueShares`, `BatchBurnShares`, and `RegisterWeightedOrg` is not convenient. ```rust #[derive(Clone, Debug)] pub struct AccountShare(pub String, pub u64); impl FromStr for AccountShare { type Err...
So this requires some constant defined in the runtime like `1 SUN = 1_000_000_000_000`. Look at polkadot runtime for example
When I reviewed the CLI it doesn't appear to yet support functionality from the following pallets Bounty Utils, Grant, Treasury, Drip, or Court. What's the plan here?
