17d109a15e
* replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com> |
||
|---|---|---|
| .github | ||
| .idea | ||
| apitest | ||
| assets/src | ||
| cli/src | ||
| common/src | ||
| core | ||
| daemon/src | ||
| desktop | ||
| docs | ||
| gpg_keys | ||
| gradle | ||
| inventory/src/main | ||
| media | ||
| monitor | ||
| p2p/src | ||
| pricenode | ||
| proto/src/main/proto | ||
| relay | ||
| scripts | ||
| seednode | ||
| statsnode/src/main | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| build.gradle | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| settings.gradle | ||
What is Haveno?
Haveno (pronounced ha‧ve‧no) is a platform for people who want to exchange Monero for fiat currencies like EUR, GBP and USD or other cryptocurrencies, like BTC, ETH, BCH .
Main features:
-
All communications are routed through Tor, to preserve your privacy
-
Trades are peer-to-peer: trades on Haveno will happen between people, the platform doesn't provide any liquidity.
-
Trades are non-custodial: Haveno provides arbitration in case something goes wrong during the trade, but we will never have access to your funds.
-
There is No token, because we don't need it. Transactions between traders are secured by non-custodial multisignature transactions on the Monero network.
See the FAQ on our website for more information.
Haveno is still work in progress. There are no binaries available at this stage. If you want to test Haveno you have to compile it first (see docs/installing.md).
Status of the project
At the moment Haveno is only a Proof of Concept. It's already possible to initiate crypto <-> XMR and fiat <-> XMR trades, but the platform still needs a lot of work before being available for public use.
The project is divided between multiple repositories:
- haveno - This repository. The heart of Haveno.
- haveno-ui-poc - The PoC of the future user interface. Uses gRPC APIs to serve the UI in React.
- haveno-meta - For project-wide discussions and proposals.
- haveno-site - The repository of the website.
If you wish to help, take a look at the issue tracker. We run a bounty program to incentivize development. See Bounties
The project is lead by a core Team formed of 2 people: ErCiccione and Woodser. The PGP keys of the core team members are in gpg_keys/.
Keep in touch and help out!
Haveno is a community-driven project. For it to be successful it's fundamental to have the support and help of the Monero community. We have our own Matrix server. Registrations are not open at the moment, but the rooms are public and can be joined from any matrix client (like Element).
- General discussions: Haveno (#haveno:haveno.network) relayed on IRC/Libera (
#haveno) - Development discussions: Haveno Development (#haveno-dev:haveno.network) relayed on IRC/Libera (
#haveno-dev)
Email: contact@haveno.exchange
Running a local Haveno test network
Contributing to Haveno
We are looking for help building Haveno. There are many tasks to complete, and many tasks have bounties.
See the developer guide to get started developing for Haveno. At this stage, we're mostly looking for help building the backend and APIs.
See docs/CONTRIBUTING.md for our styling guides.
If you are not able to contribute code and want to contribute development resources, donations fund development bounties.
Bounties
To incentivize development and reward contributors we adopt a simple bounty system. Contributors may be awarded bounties after completing a task (resolving an issue). Take a look at the issues eligible for a bounty on the dedicated Kanban board or look for issues labelled '💰bounty' in the main haveno repository. Details and conditions for receiving a bounty.
Sponsors
Would you like to help us build Haveno? Become a sponsor! We will show your logo here. Contact us at contact@haveno.exchange.
Support
To bring Haveno to life, we need resources. If you have the possibility, please consider donating to the project:
Monero
42sjokkT9FmiWPqVzrWPFE5NCJXwt96bkBozHf4vgLR9hXyJDqKHEHKVscAARuD7in5wV1meEcSTJTanCTDzidTe2cFXS1F
If you are using a wallet that supports Openalias (like the 'official' CLI and GUI wallets), you can simply put donations@haveno.network as the "receiver" address.
Bitcoin
bc1q4j5a9hfjxltfvv66gnfaw6478hagzpmjx3zkam
