lint

docs/CODE_OF_CONDUCT.md

@@ -1,20 +1,23 @@
 # Code of Conduct
-Migaloo has an open, friendly, diverse, and welcoming community. We accept and respect everybody equally, but we 
+
+Migaloo has an open, friendly, diverse, and welcoming community. We accept and respect everybody equally, but we
 don't tolerate harassing, trolling, or spamming. We are here to build, not to engage in toxic behavior.
 
 ## Our Pledge
-We as members, contributors, and leaders pledge to make participation in the community a harassment-free experience for 
-everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity 
-and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, 
+
+We as members, contributors, and leaders pledge to make participation in the community a harassment-free experience for
+everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity
+and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion,
 or sexual identity and orientation.
 
-All Migaloo contributors are required to be respectful towards other members of the team and the community. We expect 
+All Migaloo contributors are required to be respectful towards other members of the team and the community. We expect
 everybody to act in the best interest of the community.
 
 ## Conflict resolution
-Contributors and community members should always try to solve conflicts communicatively. We encourage everybody to use 
-appropriate communication channels to express their concerns and feelings. These channels include on-chain governance and 
+
+Contributors and community members should always try to solve conflicts communicatively. We encourage everybody to use
+appropriate communication channels to express their concerns and feelings. These channels include on-chain governance and
 social media platforms like Twitter and Discord. Always remember to focus on what is best for the community.
 
 TLDR
-Be good.
+Be good.

docs/CONTRIBUTING.md

@@ -16,14 +16,15 @@ Before you can write any code, please take a look at the list of prerequisites b
 To download the necessary tools, clone the repository and so on, you need network access.
 
 The following are the tools you'll need:
+
 - [Git](https://git-scm.com/)
 - [Go](https://go.dev/doc/install)
 - [Docker](https://www.docker.com/)
 - An IDE. We recommend either [GoLand](https://www.jetbrains.com/go/download/), [Intellij Idea](https://www.jetbrains.com/idea/download/) or [VS Code](https://code.visualstudio.com/download),
   but feel free to use your preferred code editor.
 - [Go Plugin](https://plugins.jetbrains.com/plugin/9568-go) for Intellij Idea or the [Go extension](https://marketplace.visualstudio.com/items?itemName=golang.go) for VS Code.
 
---- 
+---
 Then fork the code and read it through. We encourage you to make your own contributions, though you might look at the
 [issue tracker](https://github.com/White-Whale-Defi-Platform/migaloo-chain/issues) if you want to solve something that has
 been pointed out already.
@@ -109,9 +110,10 @@ Are you a graphic designer and want to help out with some NFTs? Are you a copywr
 Whatever it is, we would love to hear from you and see how we can make White Whale better for everybody.
 
 ## Docs
+
 When in doubt, please take a look at our [litepaper]() or our [documentation]([]()).
 
-# Thank you!
+# Thank you
 
 All contributions to Migaloo are of great value and make this chain possible. Thanks for taking the time to make
-Migaloo better! We really appreciate it.
+Migaloo better! We really appreciate it.

docs/ROADMAP.md

@@ -1,5 +1,3 @@
 # Roadmap
 
 The Migaloo project roadmap is outlined in this document, which is subject to updates as the project advances.
-
-

docs/SECURITY.md

@@ -1,34 +1,40 @@
 # Security Policies and Procedures
+
 This document outlines security procedures and general policies for the `migaloo-chain` project.
+
 * [Reporting a Bug](#reporting-a-bug)
 * [Disclosure Policy](#disclosure-policy)
 * [Suggestions on this Policy](#comments-on-this-policy)
 
 ## Reporting a Bug
-Security is something we take seriously at Migaloo. Thanks for taking the time to improve the security of `migaloo-chain`. 
+
+Security is something we take seriously at Migaloo. Thanks for taking the time to improve the security of `migaloo-chain`.
 We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.
 
 Please report security bugs by emailing White Whale at [email protected] or [email protected]. Do not report
-it publicly on the GitHub issues tracker. Your report should detail the necessary steps to reproduce the security issue. 
-We will acknowledge your email within 48 hours and send a detailed response indicating the next steps. After the initial 
-reply to your report, we will keep you informed of the progress towards a fix and full announcement and may ask for 
+it publicly on the GitHub issues tracker. Your report should detail the necessary steps to reproduce the security issue.
+We will acknowledge your email within 48 hours and send a detailed response indicating the next steps. After the initial
+reply to your report, we will keep you informed of the progress towards a fix and full announcement and may ask for
 additional information or guidance.
 
 Report security bugs in third-party modules to the person or team maintaining the module.
 
 ## Disclosure Policy
-If we receive a security bug report, we assign it to a primary handler. This person will coordinate the fix and release 
+
+If we receive a security bug report, we assign it to a primary handler. This person will coordinate the fix and release
 process, involving the following steps:
+
 * Confirm the problem and determine the affected versions.
 * Audit code to find any potentially similar problems.
 * Patches are prepared for eligible releases in private repositories.
-* We inform the community of an upcoming security release to provide ample time for users to update their systems. 
+* We inform the community of an upcoming security release to provide ample time for users to update their systems.
 Notifications are sent through various channels such as Discord, Twitter, and email to partners and validators.
 * 24 hours after the notification, the security fixes are publicly implemented and new releases are made available.
 * Once the releases are available for Migaloo, the community is notified again through Discord, Twitter, and email to partners and validators.
 * Upon notification to the community, relevant bug bounties will be rewarded to submitters.
 * A week after the release, a post with details on the vulnerability and our response will be published.
 
 ## Suggestions on this Policy
+
 If you have suggestions on how to improve this process, please submit a
-pull request or reach out on [Discord](https://discord.com/invite/tSxyyCWgYX).
+pull request or reach out on [Discord](https://discord.com/invite/tSxyyCWgYX).

networks/mainnet/README.md

@@ -34,7 +34,9 @@ migalood version --long | grep commit
 ```bash
 migalood init MONIKER --chain-id=migaloo-1
 ```
+
 Set minimum gas price to 0.
+
 ```bash
 sed -i 's/minimum-gas-prices = ".*"/minimum-gas-prices = "0uwhale"/' $HOME/.migalood/config/app.toml
 ```

scripts/README.md

@@ -1,7 +1,7 @@
 # Scripts
 
-These scripts are copied from the [Cosmos-SDK](https://github.com/cosmos/cosmos-sdk/tree/v0.42.1/scripts) respository 
+These scripts are copied from the [Cosmos-SDK](https://github.com/cosmos/cosmos-sdk/tree/v0.42.1/scripts) respository
 with minor modifications. All credits and big thanks go to the original authors.
 
 Please note that a custom [fork](github.com/regen-network/protobuf) by the Regen network team is used.
-See [`go.mod`](../go.mod) for version.
+See [`go.mod`](../go.mod) for version.