So it's just as self-regulating process as with the usual PoW mining.
Oh, of course. I knew that PoS has its own difficulty to regulate the number of blocks generated, but I was in stupid mode. Apologies for my temporary brain fart.
Topic: [ANN] Orbitcoin v1.6.0.0 ~ NeoScrypt ~ Green Stake ~ 4 Years Old - page 119. (Read 201256 times)
Oh, of course. I knew that PoS has its own difficulty to regulate the number of blocks generated, but I was in stupid mode. Apologies for my temporary brain fart.
If there is any development you guys need please contact us, here is our portfolio so far:
epawncoin Website: http://epawncoin.com
epawncoin Wallet: http://wallet.epawncoin.com/
epawncoin Android Application: https://play.google.com/store/apps/details?id=com.epawncoin.wallet
kimdotcoin Wallet: http://kimdotcoin.co.nz/
Kimdotcoin Android App: https://play.google.com/store/apps/details?id=com.raxe.kimdotcoin
Compasscoin Wallet: http://wallet.compasscoin.org
Compasscoin Android App: https://play.google.com/store/apps/details?id=com.compasscoin.wallet
STLCoin Wallet: http://wallet.stlcoin.org/#/
STLCoin Android App: https://play.google.com/store/apps/details?id=com.stlcoin.wallet
Epawncoin Exchange: http://coinpod.net
If you have any questions please do not hesitate to contact us:
https://twitter.com/RaxeSoftware
[email protected]
Skype: raxe.io (Raxe.io Support)
well done
good job.....
good job.....
So it's just as self-regulating process as with the usual PoW mining.
Oh, of course. I knew that PoS has its own difficulty to regulate the number of blocks generated, but I was in stupid mode. Apologies for my temporary brain fart.
I've been thinking about a coin with fixed reward PoS for a while (...it's probably already been done...)
Are PoS minted blocks also eligible to generate further PoS themselves once they've matured sufficiently? If so, surely there would be issues with exponential runaway? If you start with 1 ORB then do nothing, after 30 days (or whatever) it will PoS mint an additional 1 ORB, so your balance is now 2 ORB; after 30 more days, you will PoS mint an additional 2 x 1 ORB, so you now have 4 ORB, and so on. In a year your 1 ORB will grow to 4096 ORB, at the end of 2 years it will be 16 million.
This can't be right. So is there some code to prevent PoS funds minting more PoS blocks?
No any "exponential runaway". If many people (more than needed to generate the target number of PoS blocks) will do so it just rise PoS difficulty up while keeping amount of PoS blocks (and coins productions via PoS) at same level. (= each person running PoS will get less coins)Are PoS minted blocks also eligible to generate further PoS themselves once they've matured sufficiently? If so, surely there would be issues with exponential runaway? If you start with 1 ORB then do nothing, after 30 days (or whatever) it will PoS mint an additional 1 ORB, so your balance is now 2 ORB; after 30 more days, you will PoS mint an additional 2 x 1 ORB, so you now have 4 ORB, and so on. In a year your 1 ORB will grow to 4096 ORB, at the end of 2 years it will be 16 million.
This can't be right. So is there some code to prevent PoS funds minting more PoS blocks?
And with high PoS diff it is better(=greater probability of finding the block) to have in wallet few relative large incoming transactions vs very many small transactions.
So it's just as self-regulating process as with the usual PoW mining.
Plus i thinks you miss this: "The minimum amount to generate a PoS block is 20 ORB."
So just one PoS block is not enough to generate another PoS bloсk even now (at very low PoS diff) only if stack few PoS blocks up to 20 ORBs at same address.
Couple of patches to allow Orbitcoin to compile cleanly on FreeBSD:
util.cpp (in function LogStackTrace) :
Copy makefile.unix to makefile.freebsd, then patch:
util.cpp (in function LogStackTrace) :
Code:
1000c1000
< #ifndef WIN32
---
> #if !defined(WIN32) && !defined(__FreeBSD__)
Copy makefile.unix to makefile.freebsd, then patch:
Code:
15a16,21
> BOOST_INCLUDE_PATH=/usr/local/include
> BDB_INCLUDE_PATH=/usr/local/include/db48
> BOOST_LIB_PATH=/usr/local/lib
> BDB_LIB_PATH=/usr/local/lib/db48
> OPENSSL_INCLUDE_PATH=/usr/local/lib
>
51d56
< -l dl \
62c67
< xCXXFLAGS=-O2 -fomit-frame-pointer -fno-stack-protector $(EXT_OPTIONS) -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter \
---
> xCXXFLAGS=-O2 -fomit-frame-pointer -fno-stack-protector $(EXT_OPTIONS) -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter \
113c118
< @echo "Building LevelDB ..."; cd leveldb; make libleveldb.a libmemenv.a; cd ..;
---
> @echo "Building LevelDB ..."; cd leveldb; gmake libleveldb.a libmemenv.a; cd ..;
I've been thinking about a coin with fixed reward PoS for a while (...it's probably already been done...)
Are PoS minted blocks also eligible to generate further PoS themselves once they've matured sufficiently? If so, surely there would be issues with exponential runaway? If you start with 1 ORB then do nothing, after 30 days (or whatever) it will PoS mint an additional 1 ORB, so your balance is now 2 ORB; after 30 more days, you will PoS mint an additional 2 x 1 ORB, so you now have 4 ORB, and so on. In a year your 1 ORB will grow to 4096 ORB, at the end of 2 years it will be 16 million.
This can't be right. So is there some code to prevent PoS funds minting more PoS blocks?
Are PoS minted blocks also eligible to generate further PoS themselves once they've matured sufficiently? If so, surely there would be issues with exponential runaway? If you start with 1 ORB then do nothing, after 30 days (or whatever) it will PoS mint an additional 1 ORB, so your balance is now 2 ORB; after 30 more days, you will PoS mint an additional 2 x 1 ORB, so you now have 4 ORB, and so on. In a year your 1 ORB will grow to 4096 ORB, at the end of 2 years it will be 16 million.
This can't be right. So is there some code to prevent PoS funds minting more PoS blocks?
To the rescue again I see 
I really hope that people appreciate your improvements to PoS and the contributions this brings. Perhaps you should write a short paper on the short comings of the original PoS and explain the work you have done here?
I'm mining Orb but if anyone has 0.5 Bitcoins worth then please send me a PM.
I really hope that people appreciate your improvements to PoS and the contributions this brings. Perhaps you should write a short paper on the short comings of the original PoS and explain the work you have done here?
I'm mining Orb but if anyone has 0.5 Bitcoins worth then please send me a PM.
Orbitcoin v1.6.0.0
(19-Sep-2016)
32-bit Windows GUI client
64-bit Windows GUI client
32-bit Linux GUI client & daemon
64-bit Linux GUI client & daemon
32-bit MacOS X (10.5+) GUI client
64-bit MacOS X (10.8+) GUI client
Source code
Block chain data for rapid deployment:
.orbitcoin.tar.xz (2394300 blocks, 1102Mb)
md5sum (.orbitcoin.tar.xz) = 10539be16ef1bc76ddb16caf3c39c48e
(for Windows users, rename extracted .orbitcoin to data)
NeoScrypt CPU and GPU miners
CPUminer (source code and binaries)
CUDAminer (source code and binaries)
NSGminer (source code and binaries)
NSGminer: The Fastest NeoScrypt GPU Miner
Specifications
advanced hybrid proof-of-work (PoW) and proof-of-stake (PoS)
fixed rate of 33% PoW blocks and 67% PoS blocks
3.77 million coins to be produced
block hashing is BLAKE2s
PoW hashing is NeoScrypt
PoS hashing is SHA-256d
2 minutes combined block target (6 minutes for PoW, 3 minutes for PoS)
retargets every block using Orbitcoin Super Shield (OSS)
time warp and instamining protection
advanced checkpointing against 51% attacks
transaction messaging supported
the 1st implementation of 0% PoS
PoW and PoS blocks carry the same fixed reward of 1 ORB
coin age for PoS: 1 day min. to 16 days max.
6 confirmations for regular transactions
200 confirmations for minted coins
very low transaction fees (most transactions are free)
no destruction of transaction fees (all collected by a block finder)
the default P2P port is 15298, RPC port is 15299
I2P/Tor ready
Example orbitcoin.conf
Quote
irc=1
dns=1
qtstyle=2
daemon=1
server=1
stakegen=1
logtimestamps=1
minersleep=2000
stakemintime=72
stakecombine=50
stakesplit=100
port=15298
rpcport=15299
rpcuser=someuser
rpcpassword=somepassword
addnode=seed0.orbitcoin.org:15298
addnode=seed1.orbitcoin.org:15298
dns=1
qtstyle=2
daemon=1
server=1
stakegen=1
logtimestamps=1
minersleep=2000
stakemintime=72
stakecombine=50
stakesplit=100
port=15298
rpcport=15299
rpcuser=someuser
rpcpassword=somepassword
addnode=seed0.orbitcoin.org:15298
addnode=seed1.orbitcoin.org:15298
Some FAQ on staking
Block reward and optimal stake size
Merchants & Services
CoinToPay.com
Web Site
Block Explorer
Mining Pools
TheBlocksFactory (1% fee, PPLNS; located in France)
Faucets
Cryptoguru.tk
Exchanges
Cryptopia (ORB/BTC)
TradeSatoshi (ORB/BTC)
NovaExchange (ORB/BTC, ORB/LTC, ORB/DOGE, ORB/ETH)
ExchangeWar.info (price monitoring)
Advancement Fund
Our advancement fund is for Orbitcoin promotion and development actions approved by the community.
It's a public ledger with all transactions visible. It's a secure cold wallet.
You can also contribute to the fund if you please.
oRBBYYiaQ6Kw5fhf2b9YiT86HmynCBsoej
Orbitcoin is one of the oldest PoW / PoS altcoins launched on the 30th of July 2013 at Cryptocointalk!
Jump to: