karel-3d

#include <iostream>
#include <string>
#include <vector>
#include <boost/algorithm/string/split.hpp>
#include <boost/algorithm/string.hpp>

class RPCDocExample {
private:
  std::string description;
  std::string code;

karel-3d

{
  "abandontransaction": {
    "group": "wallet",
    "firstArguments": "\"txid\"",
    "description": "Mark in-wallet transaction \u003ctxid\u003e as abandoned\nThis will mark this transaction and all its in-wallet descendants as abandoned which will allow\nfor their inputs to be respent.  It can be used to replace \"stuck\" or evicted transactions.\nIt only works on transactions which are not included in a block and are not currently in the mempool.\nIt has no effect on transactions which are already abandoned.",
    "tables": [
      {
        "name": "Arguments",
        "lines": [
          {

karel-3d

--- /dev/fd/63	2018-10-04 08:22:17.000000000 +0900
+++ /dev/fd/62	2018-10-04 08:22:17.000000000 +0900
@@ -64,35 +64,6 @@
 
 
 ---
-name: estimatefee
-btcversion: 0.17.0
-btcgroup: util
-permalink: en/doc/0.17.0/rpc/util/estimatefee/

karel-3d

Proposal for unified Bitcoin Core RPC Doc format

Name and arguments

Every RPC doc starts with a single line with a very simple usage example. The first word is the same as the command name. The example is exactly one line.

Description

After the first line with the attributes, there is a general description of the command. It can be separated from the first line by newlines, but doesn't have to.

karel-3d

010000001bd104187d72aa28d579bf7eaac6622594f49f776489a8e219b1d1a25880377d04000000006b483045022100ab580c7c1715ab51e872ebed7e83e975a65f6c26fcd164b95ac01ff5a0c7f39c02201fa4e75defcb3b00f3e462678cbf761d215e0b755c2a22500c116e29537ac85d012103dd8067b504e57999f99e4678e9d8e6b19a75101aa9c32717a2ecc83f32aa2cfdffffffff4214fd4ae43dc82436d94a8af466dc2f9e72e86bd3446d4d79d0e0253cf01777000000006b483045022100fb1bbcf763a019c57b5bbd314677fd3ac85ce318a85327f7cd9404418cf9235102207f3e4f86248bc88dcb85f3877d3e1e7926b8b91b906b74aeac8d97285433e8ee012103681b076a922accd753a026fb8521601b0a41ac1daebdc82d3f41de04f8c86cafffffffffd104187d72aa28d579bf7eaac6622594f49f776489a8e219b1d1a25880377d04080000006b483045022100eecb7634734e6d5ac3e49a964b47b67114f67abf88d18d2131f664bbf43db8b902205771c5c146c626f03d884226381ed81a46bf475c8743f8c18bc583a2e7dce42f0121039a4040abc8b954cad124bae55ad6f6f9570765da8d2e5421b174055c9bf8e8baffffffffe1032d328280300bc4926cd1bc9138996a91e301d5ebf646cdd1b3d4574a46a11e0100006b483045022100c11542720962517e404329a126c244a447433882

karel-3d

; (C) Copyright 2011 Hewlett-Packard Development Company, L.P.

[Version]
Signature="$WINDOWS NT$"
Class=USB
ClassGUID={36FC9E60-C465-11CF-8056-444553540000}
Provider=%MFG%
DriverVer=08/21/2014,1.0.0.227
CatalogFile=hpbuio140l.cat

karel-3d

Chrome App Owners,

You're receiving this email because you have at least one Chrome app published in the Chrome Web Store.

Chrome Apps are currently scheduled to stop working on Windows, Mac & Linux in Q1 2018, as Chrome continues to focus on moving the open web forward.

The Chrome team is now working to enable Progressive Web Apps (PWAs) to be installed on the desktop. Once this functionality ships (roughly targeting mid-2018), users will be able to install web apps to the desktop and launch them via icons and shortcuts; similar to the way that Chrome Apps can be installed today.

In order to enable a more seamless transition from Chrome Apps to the web,

karel-3d

=============================================
   Bitcoin Gold 0.15.0: src/test-suite.log
=============================================

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0

karel-3d

Statistics of bitcoin input (script) lengths from august 2015 to august 2017-ish

I wanted to know, how long inputs are in bitcoin transactions.

The script is here. It is in node, and it is using bitcoinjs-lib libraries.

Complete results are here (just the final ones), sorted by counts.

tl;dr:

karel-3d

(note: this is 3/2015, not entirely fixed, but not that fatal now)

I have found a cool (and kind of stupid) way to make a browser tab unresponsive, sometimes crash the whole browser and in some cases crash the entire OS

Just add this peace of code to your website and make the user reload or close the tab.

 window.onbeforeunload = function () {
   while (true) {
     console.log("AAAA");
   }