Compound [deprecated]

Members URI

In this implementation of membersURI, we define a member of the DAO as any address with a voting share OR non-voting shares greater than or equal to zero. votingShares represent the amount of token each address has and is not delegated into another address. nonVotingShares represent the number of tokens one delegated to another address. Also, delegatedShares indicates the total number of tokens delegated to the member’s address.

We add a checkpoint property because the Compound governance contract keeps track of the voting weights based on the block time by using checkpoints. Compound governance token contract has a structure named Checkpoint which has two elements; fromBlock and votes. Each time a member transfers tokens to another party delegates the tokens to another party or cancels the delegation this structure for the member will be updated. fromBlock will be changed into the block number in which the change happen and votes will be changed in a proper way based on the transfer of voting right.
Also, it should be mentioned that Compound governance calculates the voting weight of each member, by calculating the voting power each member had at the starting time of each proposal. So, when a member decides to vote on a specific proposal, the smart contract is using checkpoints of the member to find the amount of voting power the member had in the start time of the proposal (the block time in which that specific proposal is submitted).

So, to have the members and their voting power on each proposal we need to keep track of the checkpoints and votingShares, nonVotingShares and delegatedShares related to each of the checkpoints of the members.

(For optimization we can just calculate the start time of the oldest ongoing proposal and remove the objects with checkpoints lesser than that from the membersURI JSON)

We add "delegatee-ethereum-address" field to specify to which address the member delegated their voting right. 

{
	"@context": {
		"members": "https://daostar.org/members",
		"member": "https://daostar.org/member",
		"checkpoint" : "https://daostar.org/member",
		"memberId": "https://daostar.org/memberId",
		"votingShares": "https://daostar.org/moloch/votingShares",
		"nonVotingShares": "https://daostar.org/moloch/nonvotingShares",
		"ethereum-address": "https://daostar.org/EthereumAddress",
		"delegatee-ethereum-address": "https://daostar.org/DelegateeEthereumAddress",
	},
	"members": [{

			"memberId": {
				"@value": "0xabc123",
				"@type": "EthereumAddress"
				"checkpoint" : "12000000"
			},

Proposals URI

Each proposal has a specific Id, a title, a string describing the proposal. Also, the block number from which the proposal is started and the block number in which the proposal will be ended and the address of the proposer.

The status of the proposals in Compound can be Pending, Active, Canceled, Defeated, Succeeded, Queued, Expired, or Executed. 

{
	"@context": {
      "@vocab": "http://daostar.org/"

	},
	"proposals": [
		{
			"metadata": {
				"proposalId": "PROPOSAL_COUNTER",
				"title": "<Proposal Title>",
				"contentURI": "description",
				"startBlock":"blockNumber1",
				"endBlock":"blockNumber2",
				"proposer": "0x1aqw10"
			},
			"status": {
				"@type": "daostar:compound",
				"@value": "executed"
			},
	"executionData": {
		"calls": [
		{	
			"@type": "callDataEVM",
			"from": "<address_1>",
			"to": "<address_1>",
			"data": "<call_data_1>",
			"call_type": "<call or delegate call>",
			"value": "<call_value_1>"
		},
		{
			"@type": "callDataEVM",
			"from": "<address_2>",
			"to": "<address_2>",
			"data": "<call_data_2>",
			"call_type": "<call or delegate call>",
			"value": "<call_value_2>"
		}]

}

Activity Log

{
	"@context": {
		"@vocab": "http://daostar.org/"
	},
	"activity": [
		{
			"interactionType": "vote",
			"voter": {
				"@value": "0xabc123",
				"@type": "ethereum-address"
			},
			"proposal": "PROPOSAL_COUNTER",
			"result": {
				"choice": "For",
				"weight": {
					"@type": "shares",
					"@value": 150
				}
			},
			"timestamp": "2021-01-01"
		}
	]
}

Compound

In Compound governance, we have generic action proposals so all we need to add is a URI state variable and a setter. This can then be updated through standard governance flows.

interface IEIP_TBD {
    function daoURI() external view returns (string memory); 
}

function setDaoUri(string memory _newUri) external baalOnly;

Compound [deprecated]

Members URI

In this implementation of membersURI, we define a member of the DAO as any address with a voting share OR non-voting shares greater than or equal to zero. votingShares represent the amount of token each address has and is not delegated into another address. nonVotingShares represent the number of tokens one delegated to another address. Also, delegatedShares indicates the total number of tokens delegated to the member’s address.

We add a checkpoint property because the Compound governance contract keeps track of the voting weights based on the block time by using checkpoints. Compound governance token contract has a structure named Checkpoint which has two elements; fromBlock and votes. Each time a member transfers tokens to another party delegates the tokens to another party or cancels the delegation this structure for the member will be updated. fromBlock will be changed into the block number in which the change happen and votes will be changed in a proper way based on the transfer of voting right.
Also, it should be mentioned that Compound governance calculates the voting weight of each member, by calculating the voting power each member had at the starting time of each proposal. So, when a member decides to vote on a specific proposal, the smart contract is using checkpoints of the member to find the amount of voting power the member had in the start time of the proposal (the block time in which that specific proposal is submitted).

So, to have the members and their voting power on each proposal we need to keep track of the checkpoints and votingShares, nonVotingShares and delegatedShares related to each of the checkpoints of the members.

(For optimization we can just calculate the start time of the oldest ongoing proposal and remove the objects with checkpoints lesser than that from the membersURI JSON)

We add "delegatee-ethereum-address" field to specify to which address the member delegated their voting right. 

{
	"@context": {
		"members": "https://daostar.org/members",
		"member": "https://daostar.org/member",
		"checkpoint" : "https://daostar.org/member",
		"memberId": "https://daostar.org/memberId",
		"votingShares": "https://daostar.org/moloch/votingShares",
		"nonVotingShares": "https://daostar.org/moloch/nonvotingShares",
		"ethereum-address": "https://daostar.org/EthereumAddress",
		"delegatee-ethereum-address": "https://daostar.org/DelegateeEthereumAddress",
	},
	"members": [{

			"memberId": {
				"@value": "0xabc123",
				"@type": "EthereumAddress"
				"checkpoint" : "12000000"
			},

Proposals URI

Each proposal has a specific Id, a title, a string describing the proposal. Also, the block number from which the proposal is started and the block number in which the proposal will be ended and the address of the proposer.

The status of the proposals in Compound can be Pending, Active, Canceled, Defeated, Succeeded, Queued, Expired, or Executed. 

{
	"@context": {
      "@vocab": "http://daostar.org/"

	},
	"proposals": [
		{
			"metadata": {
				"proposalId": "PROPOSAL_COUNTER",
				"title": "<Proposal Title>",
				"contentURI": "description",
				"startBlock":"blockNumber1",
				"endBlock":"blockNumber2",
				"proposer": "0x1aqw10"
			},
			"status": {
				"@type": "daostar:compound",
				"@value": "executed"
			},
	"executionData": {
		"calls": [
		{	
			"@type": "callDataEVM",
			"from": "<address_1>",
			"to": "<address_1>",
			"data": "<call_data_1>",
			"call_type": "<call or delegate call>",
			"value": "<call_value_1>"
		},
		{
			"@type": "callDataEVM",
			"from": "<address_2>",
			"to": "<address_2>",
			"data": "<call_data_2>",
			"call_type": "<call or delegate call>",
			"value": "<call_value_2>"
		}]

}

Activity Log

{
	"@context": {
		"@vocab": "http://daostar.org/"
	},
	"activity": [
		{
			"interactionType": "vote",
			"voter": {
				"@value": "0xabc123",
				"@type": "ethereum-address"
			},
			"proposal": "PROPOSAL_COUNTER",
			"result": {
				"choice": "For",
				"weight": {
					"@type": "shares",
					"@value": 150
				}
			},
			"timestamp": "2021-01-01"
		}
	]
}

Compound

In Compound governance, we have generic action proposals so all we need to add is a URI state variable and a setter. This can then be updated through standard governance flows.

interface IEIP_TBD {
    function daoURI() external view returns (string memory); 
}

function setDaoUri(string memory _newUri) external baalOnly;