Check-in [15d5fb582f]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Bump version number
Timelines: family | ancestors | descendants | both | trunk | 0.5.6-20171101
Files: files | file ages | folders
SHA1: 15d5fb582f59e5cd064df5b2f08799253b6c3a44
User & Date: bernd 2017-11-01 21:35:47
Context
2017-11-01
22:13
add size of ge25519 check-in: f6cc0aedf5 user: bernd tags: trunk
21:35
Bump version number check-in: 15d5fb582f user: bernd tags: trunk, 0.5.6-20171101
2017-10-26
00:25
Added net2o-squid.fs to installed files check-in: 0a83ba8fc8 user: bernd tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to configure.ac.

11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU Affero General Public License for more details.

# You should have received a copy of the GNU Affero General Public License
# along with this program.  If not, see <http://www.gnu.org/licenses/>.

AC_INIT([net2o], [0.5.6-20171026], [bernd@net2o.de], [net2o], [https://fossil.net2o.de/net2o/reportlist])
AC_PREREQ([2.59])
AC_CONFIG_MACRO_DIR([m4])
AC_USE_SYSTEM_EXTENSIONS
LT_INIT

AC_MSG_CHECKING([for gforth])








|







11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU Affero General Public License for more details.

# You should have received a copy of the GNU Affero General Public License
# along with this program.  If not, see <http://www.gnu.org/licenses/>.

AC_INIT([net2o], [0.5.6-20171101], [bernd@net2o.de], [net2o], [https://fossil.net2o.de/net2o/reportlist])
AC_PREREQ([2.59])
AC_CONFIG_MACRO_DIR([m4])
AC_USE_SYSTEM_EXTENSIONS
LT_INIT

AC_MSG_CHECKING([for gforth])

Changes to do.

1
2
3
4
5
6
7
8
9
10
11
12
#!/bin/bash

echo "This script builds net2o from scratch"

GFORTH=gforth-0.7.9_20171026

if [ "$(uname -o)" = "Cygwin" ]
then
    CONFOPT="--prefix=/usr $*"
else
    CONFOPT="$*"
fi




|







1
2
3
4
5
6
7
8
9
10
11
12
#!/bin/bash

echo "This script builds net2o from scratch"

GFORTH=gforth-0.7.9_20171101

if [ "$(uname -o)" = "Cygwin" ]
then
    CONFOPT="--prefix=/usr $*"
else
    CONFOPT="$*"
fi

Changes to rng.fs.

81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
    init-rng$ $@ r/w create-file throw >r
    rng-key c:key# r@ write-file throw
    r> close-file throw ;

\ Sanity check

Variable check-rng$
Variable check-old$
s" ~/.checkrng" check-rng$ $!  check-rng$ $save
$10 cells buffer: rngstat-buf

: rngstat ( addr u -- float )
    \G produces a normalized number, gauss distributed around 0
    rngstat-buf $10 cells erase  dup 3 rshift { e }
    bounds ?DO
	1 I c@ 4 rshift cells rngstat-buf + +!







|
|







81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
    init-rng$ $@ r/w create-file throw >r
    rng-key c:key# r@ write-file throw
    r> close-file throw ;

\ Sanity check

Variable check-rng$
$Variable check-old$
s" ~/.checkrng" check-rng$ $!
$10 cells buffer: rngstat-buf

: rngstat ( addr u -- float )
    \G produces a normalized number, gauss distributed around 0
    rngstat-buf $10 cells erase  dup 3 rshift { e }
    bounds ?DO
	1 I c@ 4 rshift cells rngstat-buf + +!

Changes to wiki/squid.md.

317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
...
491
492
493
494
495
496
497





498
499
500
501
502
503
504
previous block's hash as starting key for the hash calculation, so
that they contribute to the unchangeable chain, and can't be moved to
any other fake chain (they won't verify there).  Furthermore, each
transaction (despite anonymous) adds to the trust value: more
transactions in one block means that it is more trustworthy, because
more people found its way to this branch of BlockChain reality.

Note that the distributed BlockChain below makes it far more expensive
to fake a chain: You need to generate signatures and activities in all
of them; the fake activities you generate are with the coins you own;
you have no others.  Sanctions for misbehavoir can make sure these
coins are lost; the fake chain is the proof of misbehavior.

Those additional coins could be used to compensate for the loss of the
victim of double spending.
................................................................................
inability to mutual trust.  Or maybe they just have those dollar signs
in the eyes, and fall for the hype?  Who knows.  Proper
decentralization is also a way to create reliable software, so it's
still worth to pursue.

## How to really distribute book-keeping






An important design goal for me is to handle massive ammounts of
micropayments, because that's an application where I see a legitime
need for cryptographic payment protection.  Ransomware fees, tax
evasion, and illegal business are probably already handled well by
BitCoin.

All coins have a value, a unit (if you want to keep different kinds of







|







 







>
>
>
>
>







317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
...
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
previous block's hash as starting key for the hash calculation, so
that they contribute to the unchangeable chain, and can't be moved to
any other fake chain (they won't verify there).  Furthermore, each
transaction (despite anonymous) adds to the trust value: more
transactions in one block means that it is more trustworthy, because
more people found its way to this branch of BlockChain reality.

Note that the partitioned BlockChain below makes it far more expensive
to fake a chain: You need to generate signatures and activities in all
of them; the fake activities you generate are with the coins you own;
you have no others.  Sanctions for misbehavoir can make sure these
coins are lost; the fake chain is the proof of misbehavior.

Those additional coins could be used to compensate for the loss of the
victim of double spending.
................................................................................
inability to mutual trust.  Or maybe they just have those dollar signs
in the eyes, and fall for the hype?  Who knows.  Proper
decentralization is also a way to create reliable software, so it's
still worth to pursue.

## How to really distribute book-keeping

A distributed database can be replicated or partitioned (or both).
BlockChains as of now are replicated; that's the scaling problem
mentioned in the bullshit bingo sheet above.  They also need to be
partitioned to gain all the benefits of modern distributed databases.

An important design goal for me is to handle massive ammounts of
micropayments, because that's an application where I see a legitime
need for cryptographic payment protection.  Ransomware fees, tax
evasion, and illegal business are probably already handled well by
BitCoin.

All coins have a value, a unit (if you want to keep different kinds of