While direct barter between individuals is a goal.

Time Locking / aka segwit code allows counterfeiting and will never be implemented in ZEIT.
Barterdex requires time locking / segwit style code to allow the cross chain atomic swaps for their system to work.


 

I had a single masternode working and reachable on private and public net but after switching to a multiple (ten) masternode config I am able to start them all and they show mining but none of them are actually running and bound to the port I gave them. It goes to 00m:00s for all of my MNs. I do earn mining rewards but they aren't actually running. I have put 100k coins in every address associated with this and am able to start them all via the My Creamnodes tab. Thanks for any help

rpcallowip=127.0.0.1
rpcuser=...
rpcpassword=...
rpcport=57077
port=56066
promode=1
masternode=1
masternodeaddr=... (ten times with diff ports)
masternodeprivkey=... (ten times with diff privkeys)
staking=0
server=1
listen=1
daemon=1
rescan=0
reindex=0
defaultkey=1
logtimestamps=1
maxconnections=50
rpcthreads=30
verifychain=0
dns=1

trying to start staking on a server.

no peers.

none of the peers connect ... here's my conf file.

----

addnode=115.163.56.7
addnode=87.98.182.171
addnode=167.114.224.79
addnode=167.114.224.82
addnode=2.26.10.33
addnode=212.123.176.143
addnode=213.127.117.26
addnode=213.155.254.2
addnode=213.229.0.41
addnode=213.46.197.237
addnode=23.245.7.15
addnode=40.112.185.197
addnode=5.9.20.83
addnode=51.254.68.179
addnode=70.75.222.15
addnode=75.118.69.81
addnode=77.130.254.239
addnode=78.248.188.112
addnode=82.69.45.247
addnode=84.72.115.99
addnode=88.115.126.51
addnode=90.182.204.175
addnode=91.44.203.1

rpcport=22715
rpcallowip=127.0.0.1
rpcuser=randomuser
rpcpassword=asifiwouldtellyou


----


Also, when trying to build the headless daemon on a unix machine, I get a double definition of scrypt_core from the both scrypt-x86_64.S and scrypt_mine.cpp -- I commented the one out of scrypt_mine.cpp and that allowed me to build, but I don't like the solution ...

short answer: i dont claim that their project is a copy, it's even different, i refer only to that article that refers to my writings without mentioning it nor accurately representing them.
long answer, including additional thoughts on the article, i'll write later on

old refs of mine regarding tezos:
https://bitcointalk.org/index.php?topic=950309.msg17917492#msg17917492
https://bitcointalk.org/index.php?topic=950309.msg14904326#msg14904326
https://bitcointalk.org/index.php?topic=950309.msg18686581#msg18686581
nothing negative, though from the article i learned that they're turing complete (more to come)

the plan is to finish the paper first, that'd be safe and successful to my estimation, but, if buyers will repeat this request from me due to e.g. fear of competition (i.e. if more people agree with you), i can postpone publications by putting time into code

(i'll reply later with little more detail about tezos)

I'm doing so DD into the team of Blockpool.

Who is this Coinbar Digital Currency Group? Can't even find a website for them.

If it's based on existing math (as most things around) with some added value, only this added value would be new. I don't like "discovery" word in such matters, better "new arrangement". Regardless definitions, I will keep you updated.

Wouldn't be new, just with emphasis on different things.

In the present scheme of blockchain there is no possibility to perform more than two operations at once, stemming from the fact that every next blocks depends on the previous. Of course this is mitigated by packing multiple transactions into one block and hashing them collectively. But it’s far from concurrency, rather it’s just a way to deal with this very limited structure. In lattice things are different. There are multiple root points that are referred to from the main root. It resembles child chains in some applications, but is very different on the basic level of functionality.
With lattice, many operations can be performed at the same moment in time by different miners/processing units. And still the whole structure will retain integrity. Because clusters can but usually won’t overlap.

But at the same time it provides means for features like lattice encryption.

Up to the point that one of the features in my idea acts exactly as synapses and I also postulate homomorphically encrypted seeded entities acting as local authorities and being "hidden variables" of this network, something that can be compared to a primitive consciousness.

In homomorphic transformations leading to certain arrangement of lattice[.]

Those who will need to know details will read the whitepaper and associated docs. All math will be there. The rest will have dev docs aimed at providing comfortable interface.

I remember having some blackcoins in a wallet when I first started out  staking coins to give it a try.
Lost the waller and didn't try to get anymore.
Good to see there still is interest in it almost two years later.
I might try to collect these again and see where they take me.
Any exchanges taking it yet?

each assetchain is its own chain and gets its own deterministically determined port

the REVS dir will be created in ~/.komodo/REVS

from ~/komodo/src you can issue equivalent to komodo-cli calls using the fiat/revs script

I know revs isnt fiat, but that is where all the pax chain scripts were and it was easiest to put revs in there

you can run the komodod -ac_name=REVS -ac_supply=1300000 to run the REVS chain

iguana wallet will be supporting REVS, but not sure of timeframe, shouldnt be that long

it uses the same privkey as BTCD if it was from local wallet snapshot and the same privkey as the KMD payout address if from the ICO payout. currently only commandline iguana supports converting passphrase to importprivkey compatible wif string

but the GUI will soon support that