boscore / referendum

🗳Referendum platform for BOSCore

BOS Ecosystem Program (Referendum & WPS)

中文版本

• Proposal Structure Example
• Deployment Procedure
• Execution Procedure

1. Background

This proposal is a BOS development incentive program proposed by the founding core teams of BOS. The goal is to continue to support the development of core protocol and the expansion of the entire EOSIO ecosystem. BOSCore will set up an environmental fund of 100 million BOS for infrastructure construction, protocol standard setting, code optimization, and ecological partner incentives, etc. Other EOSIO eco-contributors can also apply for fund support, and multi-chain can achieve greater prosperity together. After this proposal is approved, BOSCore will deposit 100 million BOS into a designated account, which will be managed by BPs and used according to community referendum.

2. BOS Executive Team

Details: https://www.boscore.io/en/team.html

3. Program Goals

• Attracting and incentivizing developers or teams
• Letting more communities get involved
• Accelerating the evolution of EOSIO technology
• Prospering the EOSIO Ecosystem

More Details:

• English: BOS Ecosystem Program(Referendum & WPS).md
• Chinese: Referendum_WPS/BOS生态基金方案.md

referendum's Issues

Implement NuXT Server-side Rendering for frontend in V2

NuxT framework

https://nuxtjs.org/

Server Side Rendered (Universal)
The most popular mode for Nuxt. With SSR, also called "universal" or "isomorphic" mode, a Node.js server will be used to deliver HTML based on your Vue components to the client instead of the pure javascript. Using SSR will lead to a large SEO boost, better UX and more opportunities (compared to a traditional Vue SPA).

Because implementing SSR on your own can be really tedious, Nuxt.js gives you full support out of the box and will take care of common pitfalls.

Expired Action seems to have been renamed "Cancel", but Readme still lists "Expire".

Poll status card misleading data

Shouldn't status card show based in total votes instead of number of users voting?

Right now those % are related to number of accounts voting, but not taking in consideration voting power of each one.

Display request amount (parameter field) on the right section

boscore/referendum-ui#7

To avoid misalignment between proposers's request amount in parameter and text's announced amount.

Filters dont work

the created_at and expire time of referendum are not correct: 提案创建后日期显示貌似有误

after I created a referendum, seems like the time is wrongly displayed. please help to check. thanks a lot.@SheldonHH

I created it just yesterday evening, and set the expire time to end of june, yet the time displayed is one month earlier for both parameters.

Allow 3-12 character limit in UI for `proposal_name`

proposal_name can be anything from 3 to 12 characters.

https://github.com/boscore/referendum/blob/master/contracts/eosio.forum/src/forum.cpp#L19

can't submit proposal

When trying to submit a proposal with or without markdown content via https://www.boswps.io and with Scatter Desktop (login works), an error is given

Create ERROR[object Object]

Nothing else is logged on the browser console and Scatter is not called

Wrong Width cards on column

Width of cards on referendum page should be the same

remove proposal_name that require proposer to fill in as PK

Currently there are two parameters in propose page:
proposal name and title which is confusing for developers.

Basically proposal_name is the PK for proposal_row table

referendum/contracts/eosio.forum/include/forum.hpp

Lines 87 to 100 in 84e28b1

	struct [[eosio::table]] proposal_row {
	name proposal_name;
	name proposer;
	string title;
	string proposal_json;
	time_point_sec created_at;
	time_point_sec expires_at;
	auto primary_key()const { return proposal_name.value; }
	uint64_t by_proposer() const { return proposer.value; }
	bool is_expired() const { return current_time_point_sec() >= expires_at; }
	bool can_be_cleaned_up() const { return current_time_point_sec() > (expires_at + FREEZE_PERIOD_IN_SECONDS); }
	};

It's necessary to remove the burden for develop to key in this 12 character primary key and allow either auto-incremental PK or random identifier to be generated to identify a particular proposal.

https://boswps.io

Numbers with commas

We can put numbers with commas to make them more readable

Empty space on the right side

A lot of empty space on the screen

auditor.bos - enforce JSON input

Currently updatebio input allows any string

Should enforce JSON input

VALIDATE_JSON - code reference
https://github.com/boscore/referendum/blob/master/contracts/eosio.forum/src/forum.cpp#L212

"Incentives" and "Receipt account" do not recorded on the blockchain when create proposal use boswps.io

"Incentives" and "Receipt account" do not recorded on the blockchain when create proposal use boswps.io

In page of create proposal,there has "Incentives" and "Receipt account" field.

But in the contract, no usage of them .

Allow multiple init escrows & fund escrow using memo name

• Allow multiple escrows to be initialized by a single sender "creator of escrow".
• Funding escrow would require the sender to include a memo which would equal to the escrow name.

bosc transfer <SENDER> escrow.bos "100.0000 BOS" -m "<ESCROW NAME>"

This would allow multiple escrows to be initialized and funded at a later date.

Proposing batched MSIG escrows would be a more efficient & clear to understand when reviewing.

Trim / clean html on cards

We can remove html tags from cards to make them more readable.

eosio.forum pay for RAM

Instead of having the user pay for RAM, the contract would pay for all user actions