ORIGINAL MintEXP Actual Application Docs (Webapp & SDK) about craft HOT 5 OPEN

Can we just edit x/bank/client/cli/tx.go to deny sending EXP token in the message? no we can't

from craft.

Can we mint tokens with vesting times? or can this only be done via genesis?
I think we can't.

According to the Cosmos-sdk documentation:
The requirements for this vesting account is that it should be initialized during genesis with a starting balance X and a vesting end time ET.

vesting-sdk-doc

from craft.

Hi gents, on my call with reece, I basically encountered that this is a non-viable solution:

DAO funds really have to be kept in a module account so that their security is consensus enforced.

Our end solution is likely to look like applying some of /x/groups concepts to /x/gov

we can mint tokens that have the "forever vesting-- using cosmos sdk messages (gov v1beta2)

from craft.

Will post new issue tomorrow outlining this in a more consensus driven way

from craft.

update tom likes this better - says even if we value the EXP side of things at 0, CRAFT still has value.
EXP doesn't have to be on chain, the above proposal just has to add constant swap rates
ex: proposal 10eth -> 5000EXP

we need other assets non ibc native so proposals can fund other incentives
ex: DAO gets 10ETH to purchase NFT's, and then distributes these to random Land Plot owners.
This ETH wallet is held by DAO members and is multisig

The above solution IS webapp based and not state driven, but aligns with the DAOs goals
if we value EXP at 0, then CRAFT still has massive value

ROUGHLY:

{
    "proposal_id": "1",
    "content": {
      "@type": "/cosmos.craft.v1beta2.RequestExpProposal",
      "title": "Requesting EXP to contribute to the CRAFT DAO",
      "description": "ETH so the DAO can purchase NFT's for the community, BTC just to increase the DAO value",
      "walletToBeWhitelisted": "craft10r39fueph9fq7a6lgswu4zdsg8t3gxlqd6lnf0", 
      "depositPools": {
        "BTC": {
            "amount": 10,
            "expRequest": 5000,
            "closePoolDate": "2022-08-15T12:00:00Z"
        },
        "ETH": {
            "amount": 5,
            "expRequest": 250,
            "closePoolDate": "2022-08-15T12:00:00Z"
        },
      },                                 
      "vestingPeriodEnd": "2030-01-01T00:00:00Z"
    },
    "status": "PROPOSAL_STATUS_PASSED"
}

or

      "depositPools": {
        "BTC": {
            "depositAmount": 10,
            "expPerOneDeposit": 500, // so total is 5000exp here
            "closePoolDate": "2022-08-15T12:00:00Z"
        },

then the CraftMint module would only be allowed to mint the max amount above. Logic:
OnProposalPass, update CraftMintKeeper depositAmount*depositRate for each asset (ex: 1BTC @ 10,000EXP per)
Then the minter can now at max mint 10,000 since the proposal passed. Limiting downside of EXP to a rouge node

from craft.