
Major changes: - Introduce Controller base class and FxmlController subclass. The latter has awareness of an @FXML "root" Node. Together, these classes functionally replace the ViewCB class, however ViewCB has been left in place so as to avoid the need to refactor all controllers at once. In this commit, the new Controller hierarchy has been applied only to the gui.main.MainViewCB controller. - Eliminate MainPM in favor of placing all logic in MainModel. This is potentially temporary, i.e. the distinction between data model and presentation model may be reintroduced in later commits, but for the purposes of this change, the goal was to simplify and remove as many layers as possible. The precise arrangement of controller and model classes is a topic to be discussed when reviewing this change. Minor changes: - Inject model objects into MainModel instead of MainViewCB. Previously, model objects such as WalletService were injected into both MainModel and MainViewCB. Now this intended separation is more strictly observed. - Remove comment section markers and empty methods from MainModel and MainViewCB - Use public constructors in MainModel and elsewhere. This avoids unnecessary IDE warnings, allows the possibility of unit testing, and generally avoids surprise for the reader. - Eliminate Profiler statements in MainModel and elsewhere. These statements are fine during debugging or optimization sessions, but should otherwise be removed so as not to fill the logs with unimportant information. - Change signature of User#getCurrentBankAccount to return ObjectProperty. Previously, this method returned the underlying BankAccount; now returning ObjectProperty allows other components to add listeners (such as for user persistence when changing accounts in the UI). - Handle user persistence on account change elsewhere; namely add a listener for it in the MainModel constructor. Previously this was done in MainModel#setCurrentBankAccount, which amounts to a side effect in a setter method--something to avoid if possible. - Expose MainModel#getUser, and eliminate delegate methods previously in place that mediated access to the User object. This is mainly for consistency and concision.

What is Bitsquare?
Bitsquare is a cross-platform desktop application that allows users to trade fiat money (dollars, euros, etc) for bitcoin without relying on centralized exchanges such as Coinbase, Bitstamp or (the former) Mt. Gox.
By running Bitsquare on their local machines, users form a peer-to-peer network. Offers to buy and sell bitcoin are broadcast to that network, and through the process of offering and accepting these trades via the Bitsquare UI, a market is established.
There are no central points of control or failure in the Bitsquare network. There are no trusted third parties. When two parties agree to trade fiat money for bitcoin, the bitcoin to be bought or sold is held in escrow using multisignature transaction capabilities native to the bitcoin protocol.
Because the fiat money portion of any trade must be transferred via traditional means such as a wire transfer, Bitsquare incorporates first-class support for human arbitration to resolve any errors or disputes.
You can read about all of this and more in the overview, whitepaper, arbitration and risk analysis documents. Several screencasts are available as well.
Status
Pre-alpha and under heavy development.
Building from source
- Install the latest JDK (8u20 or better)
- Clone this repository
- Build and launch the Bitsquare JavaFX client by running:
./gradlew run
Pass command line arguments to the app via the Gradle -Pargs
property as follows:
./gradlew run -Pargs="--help"
Or, build an executable jar with the appJar
task:
./gradlew appJar
Run the app as follows:
java -jar build/libs/bitsquare-<version>-app.jar
Pass the --help
flag to see what options are available:
java -jar build/libs/bitsquare-<version>-app.jar --help
To build a headless bootstrap node jar, run the bootstrapNodeJar
task:
./gradlew bootstrapNodeJar
Run the bootstrap node:
java -jar build/libs/bitsquare-<version>-bootstrapNode.jar
See doc/build.md for additional information.
Staying in Touch
Contact the team and keep up to date using any of the following:
- The Bitsquare Website
- The #bitsquare IRC channel on Freenode (logs)
- Our mailing list
- @bitsquare_ on Twitter
- Get in contact with us
- GitHub Issues
License
Bitsquare is free software, licensed under version 3 of the GNU Affero General Public License.
In short, this means you are free to fork this repository and do anything with it that you please. However, if you distribute your changes, i.e. create your own build of the software and make it available for others to use, you must:
- Publish your changes under the same license, so as to ensure the software remains free.
- Use a name and logo substantially different than "Bitsquare" and the Bitsquare logo seen here. This allows for competition without confusion.
See LICENSE for complete details.