388:
91:...". So text text I added isn't an exact citation, but it is saying the same thing. I could make an exact citation, but that would include much more technical detail (which was recently cut away by someone). I think the important thing here is that the research paper says it is possible, and then describes how they did it.
26:
and thought I would suggest to you that you summarize a bit, as it is possible that these editors will attempt to delete your content. If they do delete your content, please stay with it and keep editing, and also make an entry on the talk page. Sometimes it requires talk page entries (like you have
21:
Hello Lars, I notice you have started to edit the
Ethereum page. Are a somewhat new wiki editor? Your edit/contributions list history is short so I wanted to wish you a welcome from an a fellow editor. I just wanted to send you a note that the Ethereum page gets sort of dramatic sometimes. There are
191:
So back to why I wrote this in the first place. I just think that, should it not have a citation, given that article and the general contentiousness of adding anything, even simple statements to it, you'll probably want to make sure you add a citation. That's all I came here to say. Good luck.
90:
Thanks for the welcome! Though I have been editing articles since
Knowledge launched :-) Anyway, the Microsoft research articles states at the end of the introduction, bullet point 3, "Given a Solidity program and allegedly functionally equivalent EVM bytecode, we can verify their equivalence by
297:
is not a list of things that the
Ethereum developers claim to be possible with Ethereum. It's a list of notable Ethereum applications. In this case, notability means that someone other than the people involved have noticed the applications and written about them. The source needs to be
356:. These sources (Kickstarter, Indiegogo) are separate from the subject itself. The subject cannot influence or change what's listed on these sites, as they are out of the project's control. This isn't the same as sourcing it to the project's own webpage. --
222:, an open source project that was developed by Manuel Araoz and Esteban Ordano and launched in 2013. The Proof of Existence article is not about "proof of existence" as a general concept, but about an open source project with no apparent connection to what
173:
Super. Now I've got it. I don't think you need to include as exact quotation from the material, at least not now. Encyclopedic summarizing of it is often best. But if challenged, or if issues arise, sometimes that could be
27:
already made for a different edit) to get content added to the page. Anyhow, just wanted to send you a hello, and thank you for editing the page. The page needs more editors who seek to add content and clarity to this subject.
260:
was a indeed a special project article, not the concept I thought it would be. So I agree the link wasn't relevant in this context. However, as a concept, Proof Of
Existence was mentioned by one of the Ethereum developers in
332:
page about if
Solidity is part of Ethereum or if it is a language for multiple platforms. Maybe you are interested to comment on the suggestion to merge the two articles. Maybe your technical knowledge might be useful here.
265:. But that would be first-party source, which is not a good source. Wouldn't the Luxembourg Stock Exchange be a third party source that validates it is indeed possible to do what Ethereum developers claim?
22:
a few editors who delete content constantly, and there are a few editors who try to balance it, and a few other editors other editors at other ends of the spectrum. I noticed you made this edit
226:, other than that they probably do something similar. If Manuel Araoz and Esteban Ordano are not using Ethereum in their project, then I think their project should be removed from the
118:
As for your comment. I'm not sure I understand. Do you mean citation? ... or quotation? I meant the former, But from you comment, I think you might mean the latter.
65:), and has editors who are/will challenge nearly every statement that is added to the prose. I suspect the statement will be removed if not. Cheers.
61:
That article is in a very contentious state right now (see its Talk page), has discussion/debates going on on multiple discussion boards (including
234:
to support its inclusion. Otherwise it will be removed, because a press release by LuxSE is not an independent, third-party source. --
280:
439:
451:
407:
455:
218:
Hello! The service that the
Luxembourg Stock Exchange will provide does not appear to have any direct connection to
470:
461:
109:
Hi. Thanks for clarifying your time on
Knowledge. I just noted the new WELCOME statement above. Now I know.
353:
447:
419:
395:
230:
list. The service that LuxSE will provide could be a valid entry, but only if you are able to provide an
466:
338:
272:
268:
148:
92:
32:
443:
411:
403:
311:
239:
257:
219:
414:
rather than repeatedly undoing other users' edits once it is known that there is a disagreement.
399:
361:
334:
28:
307:
303:
251:
235:
231:
329:
197:
123:
73:
62:
299:
55:
47:
262:
223:
373:
357:
442:
to discuss controversial changes; work towards a version that represents
294:
227:
193:
142:
119:
85:
69:
51:
474:
365:
342:
315:
284:
243:
201:
156:
127:
100:
77:
36:
427:
Edit warring is disruptive regardless of how many reverts you have made
147:
You are right, I used the wrong word. I was talking about a quotation.
24:
https://en.wikipedia.org/search/?title=Ethereum&oldid=736322635
438:
If you find yourself in an editing dispute, use the article's
386:
454:. In some cases it may be appropriate to request temporary
302:, about the service that will be provided by LuxSE, and
23:
446:
among editors. You can post a request for help at an
433:Do not edit war even if you believe you are right.
328:Hi Lars, there is an ongoing discussion on the
263:http://www.hudsonjameson.com/ethereummarriage/
8:
398:according to the reverts you have made on
266:
394:You currently appear to be engaged in an
7:
458:. If you engage in an edit war, you
224:LuxSE now plans to do with Ethereum
420:Knowledge's policy on edit warring
418:Please be particularly aware that
14:
50:for that recent edit you made on
232:independent, third party source
406:with others, to avoid editing
306:of both LuxSE and Ethereum. --
1:
343:15:38, 14 December 2016 (UTC)
202:20:16, 3 September 2016 (UTC)
157:18:50, 3 September 2016 (UTC)
128:17:56, 3 September 2016 (UTC)
101:17:16, 3 September 2016 (UTC)
78:16:42, 3 September 2016 (UTC)
316:14:58, 8 November 2016 (UTC)
285:14:24, 8 November 2016 (UTC)
244:13:41, 8 November 2016 (UTC)
214:LuxSE and Proof of Existence
68:And welcome to Knowledge.
54:, you really need to add a
37:11:34, 27 August 2016 (UTC)
490:
475:16:54, 8 August 2017 (UTC)
412:try to reach a consensus
402:. Users are expected to
366:18:17, 3 July 2017 (UTC)
276:
152:
96:
448:appropriate noticeboard
352:I think you've misread
391:
390:
295:Ethereum#Applications
228:Ethereum#Applications
46:Lars, if you have a
452:dispute resolution
392:
378:Ok, I'll buy that!
258:Proof of Existence
220:Proof of Existence
400:IOTA (technology)
348:Secondary sources
287:
271:comment added by
481:
467:Quinton Feldberg
389:
377:
354:WP:PRIMARYSOURCE
255:
146:
89:
17:Ethereum Welcome
489:
488:
484:
483:
482:
480:
479:
478:
456:page protection
387:
385:
371:
350:
326:
256:Thank you, the
249:
216:
140:
83:
56:source citation
48:reliable source
44:
19:
12:
11:
5:
487:
485:
436:
435:
430:
415:
384:
381:
380:
379:
349:
346:
325:
322:
321:
320:
319:
318:
289:
288:
215:
212:
211:
210:
209:
208:
207:
206:
205:
204:
182:
181:
180:
179:
178:
177:
176:
175:
164:
163:
162:
161:
160:
159:
133:
132:
131:
130:
113:
112:
111:
110:
104:
103:
43:
40:
18:
15:
13:
10:
9:
6:
4:
3:
2:
486:
477:
476:
472:
468:
465:
464:from editing.
463:
457:
453:
449:
445:
441:
434:
431:
428:
425:
424:
423:
421:
416:
413:
409:
405:
401:
397:
382:
375:
370:
369:
368:
367:
363:
359:
355:
347:
345:
344:
340:
336:
331:
330:Talk:Solidity
323:
317:
313:
309:
305:
301:
296:
293:
292:
291:
290:
286:
282:
278:
274:
270:
264:
259:
253:
248:
247:
246:
245:
241:
237:
233:
229:
225:
221:
213:
203:
199:
195:
190:
189:
188:
187:
186:
185:
184:
183:
172:
171:
170:
169:
168:
167:
166:
165:
158:
154:
150:
144:
139:
138:
137:
136:
135:
134:
129:
125:
121:
117:
116:
115:
114:
108:
107:
106:
105:
102:
98:
94:
87:
82:
81:
80:
79:
75:
71:
66:
64:
59:
57:
53:
49:
41:
39:
38:
34:
30:
25:
16:
459:
437:
432:
426:
417:
408:disruptively
393:
351:
327:
267:— Preceding
217:
67:
60:
45:
20:
404:collaborate
383:August 2017
304:independent
335:Jtbobwaysf
273:LarsPensjo
174:necessary.
149:LarsPensjo
93:LarsPensjo
29:Jtbobwaysf
444:consensus
440:talk page
410:, and to
308:Dodi 8238
252:Dodi 8238
236:Dodi 8238
450:or seek
422:states:
396:edit war
324:Solidity
300:reliable
281:contribs
269:unsigned
52:Ethereum
462:blocked
460:may be
42:Sources
374:Ferret
358:ferret
63:WP:RSN
471:talk
362:talk
339:talk
312:talk
277:talk
240:talk
198:talk
153:talk
124:talk
97:talk
74:talk
33:talk
194:N2e
143:N2e
120:N2e
86:N2e
70:N2e
473:)
364:)
341:)
314:)
283:)
279:•
242:)
200:)
155:)
126:)
99:)
76:)
58:.
35:)
469:(
429:.
376::
372:@
360:(
337:(
310:(
275:(
254::
250:@
238:(
196:(
151:(
145::
141:@
122:(
95:(
88::
84:@
72:(
31:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.