Closed simonweniger closed 4 years ago
@simonweniger I see that you are going step-by-step (e.g. not showing proposals yet). This is fine 👍But I suggest we won't merge intermediate steps into master
branch, but rather in some kind of feature branch. E.g. create a branch feature/token-governance
and create all your intermediate pull request against it. This way we merge small changes gradually one by one into feature/token-governance
and once it is done we do the final merge into master
. How does it sound?
the idea of feature/token-governance
is greate. I am going to do that
contract call fails for me when I try to register a proposal. I have 20000 LEAP on my account, so it is enough for stake and the proposal name and description are pretty unique, so there is no hash collision
contract call fails for me when I try to register a proposal. I have 20000 LEAP on my account, so it is enough for stake and the proposal name and description are pretty unique, so there is no hash collision
Did you approved the withdraw of Leap at etherscan ? This feauter where the user can approve the contract to take his Leap isn't build in yet...
Did you approved the withdraw of Leap at etherscan ? This feauter where the user can approve the contract to take his Leap isn't build in yet...
great point! totally overlooked that. Approved the allowance and now it works 🎉
Also used "write" functionality on Etherscan for the first time, cool
@cyan-one I've changed the base branch for this PR from master
to feature/token-governance
@cyan-one proposed some changes here: https://github.com/leapdao/bridge-ui/pull/276 (based on top of governance-screen branch, so will be merged here in this PR) Suggesting to merge #276 before merging #269
solves #272
0x3cc955f91d645b4250f6070a8b7d71365662776f