-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathcreatingbops.html
More file actions
140 lines (130 loc) · 7.91 KB
/
creatingbops.html
File metadata and controls
140 lines (130 loc) · 7.91 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Upscale Pay Effective WP- Trust strangers in trustless manner.</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link href="css/socicon.css" rel="stylesheet" type="text/css" media="all">
<link href="css/iconsmind.css" rel="stylesheet" type="text/css" media="all" />
<link href="css/bootstrap.css" rel="stylesheet" type="text/css" media="all"/>
<link href="css/interface-icons.css" rel="stylesheet" type="text/css" media="all"/>
<link href="css/owl.carousel.css" rel="stylesheet" type="text/css" media="all"/>
<link href="css/theme.css" rel="stylesheet" type="text/css" media="all"/>
<link href="css/custom.css" rel="stylesheet" type="text/css" media="all"/>
<link href='https://fonts.googleapis.com/css?family=Lora:400,400italic,700|Montserrat:400,700' rel='stylesheet' type='text/css'>
</head>
<body data-reveal-selectors="section:not(.masonry):not(:first-of-type):not(.parallax)">
<div class="nav-container">
<nav>
<div class="nav-bar" data-fixed-at="700">
<div class="nav-module logo-module left">
<a href="index.html"><img alt="logo" class="logo logo-dark" src="img/logo-pay.png"> <img alt="logo" class="logo logo-light" src="img/logo-light.png"></a>
</div>
<div class="nav-module menu-module left">
<ul class="menu">
<li>
<a href="#">About</a>
</li>
<li>
<a href="/create.html">Create work </a>
</li>
<li>
<a href="/browse.html">browse work </a>
</li>
</ul>
</div>
</div>
<div class="nav-mobile-toggle visible-sm visible-xs">
<i class="icon-Align-JustifyAll icon icon--sm"></i>
</div>
</nav>
<section class="blog-post">
<div id="nav-placeholder"></div>
<div class="container">
<div class="well" >
<h2>Creating Effective Work Payments</h2>
<p>None of these settings can be changed after a WP has been created, although you can add more ether or log additional payer statements. So double-check everything for typos, and make sure there aren't any extra or missing zeros in your ether amounts!</p>
<p>As WPs themselves are new methods of payment, there isn't a lot of experimental data: your mileage may vary. Here, we'll go through each input and talk about what has worked for us in the past.</p>
<h3>Payer</h3>
<p>This is the address that will control the payment. In most cases this will be your address. Note that you can double-click this input to auto-fill with your current Ethereum address.</p>
<h3>WP Title</h3>
<p>This will appear at the top of the WP on the interact page, as well as in the list of WPs on the browse page. This is displayed as a single line of no more than 100 characters, so we suggest keeping the title under this limit.</p>
<p>The title, like all of these fields, <b>cannot be edited after creation!</b> So make sure there aren't any typos or spelling errors.</p>
<h3>Payment Amount</h3>
<p>If a worker commits, this is how much you're committed to spending (or burning). If no one commits you can recover this payment and at any time you can add more funds.</p>
<h3>Service Deposit</h3>
<p>For a worker to commit to the WP, they must deposit this amount into the WP. At that point you'll be able to release or burn the total amount in the WP, which will be your initial payment plus the worker's deposit.</p>
<p>As a starting point, we recommend setting this to between 1/3 and 2/3 of the payment amount.</p>
<p>Higher service deposits mean it will take longer to find a worker, but the worker will be more confident and committed. Too high, and no one will commit at all; too low, and you risk getting incompetent, lazy, or dishonest workers.</p>
<h3>Auto-release</h3>
<p>This is the amount of time, after a worker has committed, that the WP will wait for input from you before the worker can trigger an auto-release. You can delay this timeout as many times as you want, resetting the timer to the full amount you set here. This is essentially to protect workers from "lazy payers" who don't bother to return to the payment regardless of whether the service was rendered effectively.</p>
<p>The shorter this timeout is, the more attractive the WP will be to workers; the longer it is, the less often you'll have to babysit the BP to make sure it doesn't auto-release before the worker has completed the job.</p>
<p>We recommend setting this at least as long as you expect the work to take, or possibly twice or three times as long. For a payer without an established reputation, a short auto-release timeout helps convince prospective workers that they are protected from a lazy payer.</p>
<p>For established payers, this is less essential, and can be set much longer.</p>
<p>You can set this value to decimal amounts, such as 0.1 days.</p>
<h3>Initial Statement</h3>
<p>This is where you give more detail on the work you want done. Good initial statements have the following characteristics:</p>
<ul>
<li>Clear, concise, and to-the-point.</li>
<li>Clearly state in which cases you will burn the entire payment, in which cases you'll release the entire payment, and examples of when you would release or burn part of the payment.</li>
<li>State how much involvement you expect to have in the work: should the worker be in constant contact, should they contact you only when it's done, or something in between?</li>
<li>Specify any time constraints on the job, and what your burn/release policies are in the case of missed deadlines.</li>
</ul>
</div>
</div>
</section>>
<footer class="footer-2 text-center-xs bg--white">
<div class="container">
<div class="row">
<div class="col-sm-8">
<ul class="footer__navigation">
<li>
<a href="#">About</a>
</li>
<li>
<a href="#">Terms</a>
</li>
<li>
<a href="#">Careers</a>
</li>
<li>
<a href="#">Contact</a>
</li>
</ul>
</div>
<div class="col-sm-4 text-right text-center-xs">
<ul class="social-list">
<li>
<a href="#"><i class="socicon-twitter"></i></a>
</li>
<li>
<a href="#"><i class="socicon-dribbble"></i></a>
</li>
<li>
<a href="#"><i class="socicon-vimeo"></i></a>
</li>
<li>
<a href="#"><i class="socicon-instagram"></i></a>
</li>
</ul>
</div>
</div>
<div class="row">
<div class="col-sm-12">
<a class="type--underline" href="#">hello@upscalepayments.com</a>
</div>
</div>
<div class="row">
<div class="col-sm-12">
<div class="footer__lower">
<span class="type--fine-print">© Copyright
<span class="update-year">2017 Upscale</span> - All
Rights Reserved</span>
</div>
</div>
</div>
</div>
</footer>
</div>
</body>
</html>