Ratelance

Ratelance is freelance platform that seeks to remove barriers between potential employers and workers.
Our goal is to create a secure, reliable and formally verified platform that makes it easy to delegate tasks.

We are focused on creating an environment of collaboration and DeTrust :handshake:, while helping individuals and businesses to

• :mag: locate the right freelancer for their project,
• :file_folder: verify his previous works,
• :white_check_mark: sign a contract with selectible cost and stakes,
• :lock: provide an encrypted communication channel and
• :rocket: make it easy to complete the tasks!

Contact us

• Read latest news: https://t.me/ratelance
• Vote for us in different hackatons by DoraHacks: https://dorahacks.io/buidl/4227
• Propose something, report a bug, etc: issues

Install

$ git clone https://github.com/ProgramCrafter/ratelance.git
$ pip3 install --upgrade tonsdk pynacl requests bitarray bitstring==3.1.9
$ cd ratelance
$ python3 cli_main.py

Pros of this system

1. There are no TODOs in contracts; their code is hopefully final
2. Contracts' states are simple, which makes it easier to verify their correctness
3. Distribution of reward is flexible, which allows worker and job poster to negotiate half-payment or something more interesting
4. System is symmetric, which allows workers to post announcements that they are ready to take some jobs
5. Contracts are written in FunC; that ensures less errors while converting to TVM assembly than high-level languages like Tact
6. System utilizes newest TON features, such as wallet v4 plugins
7. CLI is almost ready to be used, it covers whole contract lifetime

Current state

• contracts :white_check_mark:
  • platform contracts with unit tests
  • tests are based on toncli; they can be run as cd contracts; python3 build.py
  • test results from the build system are located in contracts/toncli.log; all tests pass successfully
  • compiled contract codes are located in contracts/build/boc directory
• cli
  • [x] Getting information about jobs, posting and revoking
  • [x] Applying for jobs, revoking offers
  • [x] Listing offers, delegating job to someone
  • [ ] Automatically verifying job/offer existence and validity
  • [ ] Encrypted communication channel on top of job contract
  • [x] Negotiating payments
  • [x] Working with keyring
  • [ ] Integration with system keys storage/using password for keyring encryption
  • used contract codes are located in cli/assets, they are not synchronized automatically on recompilation
• freelance-highlevel.idr
  • [x] High-level contracts representation
  • [x] Transaction loop implementation
  • Further work on formal contract description is suspended, as it means simulating something at least closely similar to TON, and as such it should be funded separately.

Algorithm described in detail

Common user story

1. Poster creates an job contract sending his stake (order value + fee + safety deposit) to it.

2. An analytic message is sent by poster to pre-specified address in parallel, for job contracts to be found easier.

3. Worker creates an offer contract in response to specified job, stores hash of order.

4. An analytic message is sent by worker to job contract in parallel, for offer contracts to be found easier.

5. Poster chooses an offer and sends its address (and proof that it's really an offer == StateInit) to job contract.
6. Job contract calculates hash of current order state and sends a "collapse" request to offer contract. Job contract locks.
7. Offer contract checks the incoming message and requests money from worker's wallet, locking meanwhile.
8. Worker's wallet accepts message from plugin and responds with wanted amount of money.

9. Offer contract forwards this money to job contract, destroying itself and unplugging from wallet.

10. Job contract transforms into multisig wallet (2/4: poster, worker, Ratelance platform and TON validators)
    • poster+worker – an agreement was established, everything is OK
    • poster+Ratelance – worker has not accomplished the work, poster gets a refund
    • worker+Ratelance – poster does not accept provided work, worker gets the money
    • poster+TON validators – something done by worker is deemed so inacceptible by TON that even voting is conducted
    • worker+TON validators – heavy disagreement between poster and worker, so that Ratelance cannot be a referee

    • Ratelance+TON – order is deemed so inacceptible by TON that even voting is conducted

11. Single-party-signed messages go to job or other pre-established address as analytic messages with minimal value.

12. Upon receiving message with required signatures, job contract sends out TON and self-destroys.

Reverts

• 1,2. Poster sends a "job revoke" message, job contract performs a full refund and self-destroys.
• 3,4. Worker revokes a plugin via his wallet, offer contract self-destroys.
• 5,6,7. No way back.
• 8. If worker's wallet responds "not enough funds" (bounce), offer contract unlocks itself and job contract, returning to step 5.
• 9,10. No way back.
• 11. No way to revoke a message once signed. Open another job contract to change conditions.
• 12. No way back. Money is sent in unbounceable mode.

Possible failures

• 12. Invalid message signed by parties just won't let the transaction execute.
• 11.  –
• 10. Insufficient funds for transformation. Taking 0.2 TON (total 0.2).
• 9. - Insufficient value to forward. Taking +0.1 TON.
  • Insufficient money to unplug. Taking +0.2 TON (total 0.5).
• 8. Insufficient value to process message. Taking +0.2 TON (total 0.7).
• 7. - Insufficient money to lock the contract. Taking +0.1 TON (total 0.8).
  • Contract does not exist, message bounces.
• 6. Insufficient funds to lock the contract. Taking +0.2 TON (total 1.0).
• 5.  –
• 4.  –
• 3.  –
• 2.  –
• 1.  –

TL-B schemes

Moved to interaction.tlb.