Skip to content

Fix typo #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
petryshkaCODE wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix typo #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
381bf99
Fix typostreaming-payments-with-sablier.md
petryshkaCODE Jan 20, 2025
67583f7
Typo fix multisigs.md
petryshkaCODE Jan 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion education/governance-frameworks/multisigs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Multisig governance is typically paired with a signal voting mechanism to mainta

After considering a proposal in the community's discussion venue, a signal vote will be held to assess support. While this typically involves voting with Snapshot, in some cases communities may use onchain signal voting (eg. early Yearn [ygov.finance voting tool](https://ygov.finance/vote)) or off chain voting which is weighted by user accounts instead of token holdings (eg. polls in Discourse forums or Discord).

Regardless of voting system used (on or off chain, weighted by users or token holdings), the vote itself doesn't trigger execution of the proposal's effects. Instead, the vote serves as instructions for the multisig signers to execute the proposal using their admin priveledges.
Regardless of voting system used (on or off chain, weighted by users or token holdings), the vote itself doesn't trigger execution of the proposal's effects. Instead, the vote serves as instructions for the multisig signers to execute the proposal using their admin privileges.

### **Drawbacks**

Expand Down
2 changes: 1 addition & 1 deletion .../proposals/creating-proposals/custom-actions/streaming-payments-with-sablier.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ Let’s go over them one by one:
* **broker address:** the broker address. If you don’t know what this is, you don't need it. Simply set it to `0x0000000000000000000000000000000000000000` as laid out in the example.
* **broker fee:** the broker fee. Again, if you don’t know what this is, you don’t need it. Simply set it to `0`.

Regarding cancelation, all streams in Sablier V2 have a cancelation setting.
Regarding cancelation, all streams in Sablier V2 have a cancellation setting.

If it’s set to `true`, that means that the stream can be canceled at any time by the stream creator. The stream creator is the DAO. Canceling the stream will stop it and return the funds which haven’t yet been streamed over to the stream creator. If the DAO wants to cancel a cancellable stream, generally that will require another proposal.

Expand Down