-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am Garr255 and I agree to the following. My PGP fingerprint is F78D0BBB9993ABD1C74254117C97C318F51DD18B. This is a non-legal agreement between The Bitcoin Forum ("Forum") and Garr255 ("Treasurer"). This agreement is intended to be enforced in a non-violent, non-legal way by the community. Held Amount: 250 Yearly Fee: 0-1 Deposit address: 15HpBoo2DqaeJPW28ATzZMNnUTfqZQYA9H TREASURER OBLIGATIONS After the treasurer receives the Held Amount of bitcoins, the treasurer owes the Forum the held bitcoins and must keep the entire amount safe at a particular address, never transferring them except: Transactions After the head administrator requests that the treasurer send the held bitcoins somewhere, the treasurer must send the bitcoins as directed within 14 days. Exception: 1 trustee or 3 members of the community council may order the treasurer to temporarily stop all payments. After such an order, the treasurer must not obey administrator transaction requests until the order is reversed by those same trustees or community council members, or until the trustees or community council members are removed. The treasurer *should* delay transactions as long as possible if the administrator is believed to be compromised, under duress, or acting against the best interests of the Forum. Treasurer wrap-up The treasurer may always send the entire held bitcoins amount to any trustee in order to end his obligations in this agreement. He then must also return any fees that were paid in advance. FORUM OBLIGATIONS The forum must pay the Monthly Fee by the first of every month when it is due. These fees may be paid in advance. If the forum is late in paying, the treasurer may take fees out of the held amount. If the held amount is not enough to cover the monthly fee, the contract is ended and neither party has any more obligations or debts. The forum cannot incur any debt. Under no circumstances will the forum's staff members, trustees, or community council members be liable for anything whatsoever. DISPUTES Because this contract does not define any obligations for the forum except monthly fees, and since that issue is completely handled in the previous section, it is not possible for anyone to have a dispute with the Forum under this contract. A dispute may be raised by the Forum (represented by the head administrator) against the treasurer. In case of a dispute, both parties may agree on an entity to act as arbitrator. Only if the parties cannot agree on an arbitrator: the arbitrator will be the first person in the list of community council members excluding trustees and the head administrator, assuming that the person is willing to arbitrate for free and the person is not involved in the dispute. If a party is non-responsive at any point in this process for more than 7 days, that party loses the dispute. The arbitrator can only decide whether the treasurer is in violation of this agreement or not. The arbitrator cannot award damages, order either party to do anything, or decide that the Forum is in violation of the agreement. If the treasurer is in violation of this agreement, he has an absolute moral obligation to correct the violation as soon as possible. If he does not correct his violation within 7 days, he agrees to be ostracised by the Bitcoin community. Additionally, anyone who has obligations to the treasurer is no longer required to follow those obligations in order to be considered to be acting in good faith by this community. The Forum can forgive the violation at any time. THE BITCOIN FORUM Trustees and community council members are added, removed, and reordered by the head administrator. Any change in the list of trustees takes place 60 days after a public announcement. Any change in the list of community council members takes place 30 days after a public announcement. The head administrator can be replaced in any of five ways: Method 1 The head administrator resigns and assigns someone to be head administrator. Method 2 1. One of the trustees publicly and formally states his desire to replace the head administrator. 2. 7 days pass. 3. Any trustee higher on the trustee list except the head administrator can cancel this process. 4. The trustee becomes head administrator if one half of community council members agree. Method 3 1. One half of trustees and two thirds of community council members vote to remove the head administrator. 2. The head administrator is considered to be removed. 3. A plurality vote determines the new head administrator. Method 4 1. One third of community council members agree that the head administrator should be replaced. 2. This is announced as publicly as possible so that no interested party is likely to miss the announcement. 3. 7 days pass. 4. Any trustee, including the head administrator, can cancel this process. 5. A plurality vote determines the new head administrator. Method 5 If it is absolutely clear that the head administrator is inactive and there are not enough active community council members and/or trustees to replace him, the treasurer should consider the head administrator to be whoever seems most capable of continuing the Forum. Voting Above, a fractional number of voters means the fraction of voters rounded down, but at least one. Votes should be delivered to the treasurers once there are enough votes. Treasurers must take appropriate measures to verify the identities of the voters. When a plurality vote is called for, the treasurer should contact all voters. 7 days from this contact, all votes received should be tallied and the person who received the most votes wins. In case of a tie, the vote is repeated. Initial roster with PGP fingerprints / addresses: Head administrator: - - - Michael Marquardt (theymos) - 5E6B3F3BA961193C5C9B4435C6555693DAB591E7 Trustees: - - - The head administrator - - - Stefan Thomas (justmoon) - D16E7B0442B9F02E0660C094C9473700A4B08BF3 - - - Malmi Martti (Sirius) - E526A9B27841593BC2439EB2E904B7FE1BBA4244 Community council members: - - - All of the trustees - - - psy 7FB4272D4D2285DCEA2503EC8957CE7E0ECB3344 - - - John 42B6DC513D9DFDEC4C287CD78353E637B3AAEEB0 - - - hazek 0475D4C3B9C988B8B396BB6D4FD343B39E8803E7 - - - FreeMoney 1Kwbu2Am9L2zbpUTUQ4c6PzhT6bD5CYqC4 - - - BCB D8249B78EB762933E1402A477ABE99DB1179678E - - - Maged F7F974C4D111E276FF243A8D59A6076B32733620 - - - nanotube D8B11AAC59A873B0F38D475CE7F938BEC95594B2 - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (MingW32) iEYEARECAAYFAlFI80AACgkQfJfDGPUd0YvxzgCgrllEddsYfJvlyCyX5A3bMWUU 0gUAn2OVKYHsW1VYor9hUSZWrOzJJ9fU =lROr - -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iF4EAREIAAYFAlFJIfQACgkQxlVWk9q1keeoQAD/bqIIgvxX8MJuS0Drh+vdkfQo 53bCkvXFiFJ7YOQ8354A/38amozWp7vmtzEZ+KLs8jOUYeo1pxg3OQb5XbCLa/f7 =Hxts -----END PGP SIGNATURE-----