Topic: Bullion (CBX) 'the Digital Precious Metal' | 2019 Roadmap published - page 31. (Read 359514 times)

I'm following this thread for a while and  i must say: great coin and a great dev-team!  

I've bought some CBX past months, even some when the price was less than 0.00009 and look at the price today!

If i would sell my CBX today for the actual price i could make lots of profit but i won't sell, i really think CBX will grow much
more in near future.
So my CBX wallet will run & stake for a long time.

About MN, i just hope that when there are no open slots available a MN will earn by general staking like other non-MN's.

I'm pretty sure the team knows what they are doing, they have my trust...

Mostly true but if it did take months?? (in crypto that is akin to decades) would you actually park you coins there and get nothing in return whilst you wait?

If you would that is cool. Not sure many would though.

We can try it and see. However like you say if it ever becomes worth 1000's per day to have a MN then most will make sure they do have the reliability to retain a MN and you  could be waiting a very long time indeed.

I would think the queue should earn at the very least 50% stakers rate.

This is exactly how I see it. I don't usually post here but I had to back you up on this. I find it funny that some people are saying that 12 hours is not much. Come on man, 12 hours is already way too long. If you're not taking this seriously, why should you deserve to be a masternode? Because you were able to pay 2000CBX?

Nah man, if you go down, you go down. You failed and should move back to the back of the line. I don't care if you were hit by a hurricane.

My two cents:

Surely the base insentive here is to reward the most stable/reliable BPN nodes, always online always processing transactions - without fail. If you have a flaky connection or are about to move house I would suggest you set up some proper infrastructure to host your BPN (Amazon, Azure etc...) The amount of money you can make from running a BPN will/could well go above and beyond a hobbyist crypto-staker and as such it would be inappropriate or unrealistic to think you could casually just run it on your old laptop whilst making a small fortune. - Aside from up-time and high reliability what about security? (physical and digital), what about backup and disaster recovery? - when the money gets serious the old laptop in the cupboard approach will not do, some bitcoin mines have diesel generators on standby and even employ guards to protect their assets!

If running a BPN is not for you then feel free to stake, it's not as profitable however its still free money

I like the idea of a limited queue, it fosters competition to "be the best", you deploy the most stable/reliable infrastructure you can muster and wait your turn, it might take a few months to grab a place in the queue but if it takes 4-8 months to be in a position to make thousands a day for basically doing nothing then I think I can wait...

FR

Yes, and at first sight your suggestion seemed to me like an interesting idea; except that the whole point of limiting the BPNs to 125 was to make sure these would get 6-18% return on their investment, on a 2% inflation coin. If we allow such a rotation as what you are suggesting, we are essentially adding more nodes to the 125, thus reducing the yield. This defeats why we are doing this whole BPN system.

We will see how this 125 queue plays out in real life, but I don't think that this 125 BPN limit, with lossless queue enlisting and the continuous real life disconnecting of people (whatever the reason - not always accidental ), will be such a problem since it may not fill up that quickly.

Interesting solution that seems more equitable to me for enter in one MN rather than waiting for someone to lose their connection or sell their CBX.

What about a time cycle - sharing of masternode role ?

We have a fixed number of 125  MN operating simultaneously.
Masternodes begin to operate and they take their MN ID and fill the queue order.
As the number of MNs is > 125 then cycling begins and MN ID #1 forfeit the role and goes to last position of the queue and MN ID #126
takes MN ID #125 and begin to participate (MN ID #127 takes pos. #126 and so on).
The cycling time can be let's say 6 to 72 hours so any of the MN candidates can estimate the exact time is needed
for taking the role (MN ID #128 -> 3 positions X 6 hours = 18 hours to take the role and 6 hours X 125 = 750 hours to forfeit it... and so on)
(*the cycling time can be fixed or variable -based on the MN candidates number-)

I think this approach has many benefits against ordinary established MN implementations.

I always believe that a master node must not be a privilege but a supporting=participation role with additional reward.

just my 2 cents...  

Hello my friends,does anybody knows how compile the CBX wallet in linux? i have tried compile it on my centos 6.5 but throw errors as below:
---------------------------------------------------------------------------------------------------------------------------------------
[root@emall163 src]# export BOOST_INCLUDE_PATH=/home/ljdzxx/install/boost.1.55.0/include
[root@emall163 src]# export BDB_INCLUDE_PATH=/home/ljdzxx/install/bdb4.8/include
[root@emall163 src]# export OPENSSL_INCLUDE_PATH=/home/ljdzxx/install/openssl/include
[root@emall163 src]# export BOOST_LIB_PATH=/home/ljdzxx/install/boost.1.55.0/lib
[root@emall163 src]# export BDB_LIB_PATH=/home/ljdzxx/install/bdb4.8/lib
[root@emall163 src]# export OPENSSL_LIB_PATH=/home/ljdzxx/install/openssl/lib
[root@emall163 src]# make -f makefile.unix
g++ -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -I/home/ljdzxx/CryptoBullion-CBX/src -I/home/ljdzxx/CryptoBullion-CBX/src/obj -I/home/ljdzxx/install/boost.1.55.0/include -I/home/ljdzxx/install/bdb4.8/include -I/home/ljdzxx/install/openssl/include -DUSE_UPNP=0 -DUSE_IPV6=1 -I/home/ljdzxx/CryptoBullion-CBX/src/leveldb/include -DUSE_LEVELDB -I/home/ljdzxx/CryptoBullion-CBX/src/leveldb/helpers -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -msse2 -o cryptobulliond obj/alert.o obj/version.o obj/checkpoints.o obj/netbase.o obj/addrman.o obj/crypter.o obj/key.o obj/db.o obj/init.o obj/irc.o obj/keystore.o obj/main.o obj/net.o obj/protocol.o obj/cryptobullionrpc.o obj/rpcdump.o obj/rpcnet.o obj/rpcwallet.o obj/rpcblockchain.o obj/rpcrawtransaction.o obj/script.o obj/sync.o obj/util.o obj/wallet.o obj/walletdb.o obj/noui.o obj/kernel.o obj/pbkdf2.o obj/scrypt_mine.o obj/scrypt-x86.o obj/scrypt-arm.o obj/scrypt-x86_64.o obj/txdb-leveldb.o -Wl,-z,relro -Wl,-z,now  -L/home/ljdzxx/install/boost.1.55.0/lib -L/home/ljdzxx/install/bdb4.8/lib -L/home/ljdzxx/install/openssl/lib -Wl,-Bstatic -l boost_system -l boost_filesystem -l boost_program_options -l boost_thread -l db_cxx -l ssl -l crypto -l miniupnpc -Wl,-Bdynamic -l z -l dl -l pthread /home/ljdzxx/CryptoBullion-CBX/src/leveldb/libleveldb.a /home/ljdzxx/CryptoBullion-CBX/src/leveldb/libmemenv.a -lrt
obj/txdb-leveldb.o: In function `init_blockindex(leveldb::Options&, bool)':
/home/ljdzxx/CryptoBullion-CBX/src/txdb-leveldb.cpp:61: undefined reference to `leveldb::DB::Open(leveldb::Options const&, std::__cxx11::basic_string, std::allocator > const&, leveldb::DB**)'
/home/ljdzxx/CryptoBullion-CBX/src/txdb-leveldb.cpp:63: undefined reference to `_ZNK7leveldb6Status8ToStringB5cxx11Ev'
obj/txdb-leveldb.o: In function `CTxDB::TxnCommit()':
/home/ljdzxx/CryptoBullion-CBX/src/txdb-leveldb.cpp:158: undefined reference to `_ZNK7leveldb6Status8ToStringB5cxx11Ev'
obj/txdb-leveldb.o: In function `CTxDB::ScanBatch(CDataStream const&, std::__cxx11::basic_string, std::allocator >*, bool*) const':
/home/ljdzxx/CryptoBullion-CBX/src/txdb-leveldb.cpp:203: undefined reference to `_ZNK7leveldb6Status8ToStringB5cxx11Ev'
obj/txdb-leveldb.o: In function `bool CTxDB::Read, std::allocator >, int>(std::__cxx11::basic_string, std::allocator > const&, int&)':
/home/ljdzxx/CryptoBullion-CBX/src/txdb-leveldb.h:84: undefined reference to `_ZNK7leveldb6Status8ToStringB5cxx11Ev'
obj/txdb-leveldb.o: In function `bool CTxDB::Read, std::allocator >, uint256>(std::__cxx11::basic_string, std::allocator > const&, uint256&)':
/home/ljdzxx/CryptoBullion-CBX/src/txdb-leveldb.h:84: undefined reference to `_ZNK7leveldb6Status8ToStringB5cxx11Ev'
obj/txdb-leveldb.o:/home/ljdzxx/CryptoBullion-CBX/src/txdb-leveldb.h:84: more undefined references to `_ZNK7leveldb6Status8ToStringB5cxx11Ev' follow
--------------------------------------------------------------------------------------------------------------------------------------------------
seems the complier can't find leveldb? but  i'm sure the leveldb file path(/home/ljdzxx/CryptoBullion-CBX/src/leveldb/libleveldb.a /home/ljdzxx/CryptoBullion-CBX/src/leveldb/libmemenv.a) is right and this 2 file exists, as i want stake my CBX(few hundred of) in my company's linux PC ,does anybody have successful experience on it? sorry i'm from china so no good at english.

We are considering leaving a BPN spot open for 24 hours in case of an unscheduled "Windows Update", or power outage disconnect; I think this leaves enough time for the BPN runner to see that something is wrong and take appropriate measures to correct it.

While it is unfair that people would lose their BPN position because of an unscheduled random event, the CBX network needs securing (there is a real job to do: someone that disconnects is no longer helping) and it's also extremely important to leave openings so that it won't be impossible to get on the BPN network to newcomers, who are willing to invest to buy their 2000 CBX share. If it's impossible to get on, CBX might seem less attractive to new investors.

Hello and welcome!

The way CBX works is a little different than standard PoS. We employ our own design, PoSP (proof-of-stake-participation). What this algo does is it takes the overall coin supply inflation (2% per year) and rewards it to only the coins that are staking on the network. Offline coins forfeit their potential reward to those that are online and staking. With this, the reward that a user will experience is far higher than the 2% inflation rate. From there however things are random and dependent on the amount of other CBX that are staking at any given time across the network. Right now, just under 30% of all coins are staking (https://chainz.cryptoid.info/cbx/#!extraction). So that means you should presently be earning between 6-7% interest on your CBX over the course of a year - if of course you are staking the entire time.

Hello CBXers. I am relatively new to PoS, but pretty familiar with ASIC/GPU mining.

I was intrigued by Crypto Bullion and started two wallets on the same day, however I can't find anything on PoS payout frequency for CBX.

I made a wallet with 42 coins in it, after 3 days I received a payout, 3 more days another payment.

Now it has been over a week with nothing.

Same time frame, I opened a second wallet on my laptop and put 10 coins in it. After 15 days an equal payment as the first one in the 42 coin wallet.

Does the amount of CBX in the wallet not matter? And is the payout extremely random?

CRYPTO BULLION coins inflation is indeed a low probability. This will make people who invest in it feel at ease. A good coin should be supported.

Yeah, there would be ways around it. I'm still wondering how the distribution of 125 spots will be made up fairly.

maybe a limit needs to be impose on per wallet , but i guess they just split it. could the masternode count be increased so they more holder stand a fair chance

Very interesting project, I found a lot of interesting information about the project. Very impressive new wallet. When exactly will the results ...

193193 CBX presumed lost, and at least 300 000 CBX in strong hands, that leaves 500 000 CBX that "can be" available at higher prices; this project is well positioned to gain nicely in the coming months.

We should look at how many of the first big addresses are actually staking, for an indication of how many BPNs will be active in general.

About the BPN queue; I think 125 BPN spots is a sweet number as it's neither too small nor too big. If someone gets dropped over the weekend because of a Windows update I don't think it will be too hard to get back on; experience will tell how that will go of course. I suggest we try it as described, since it's all new uncharted territory; we can always make changes later on if it becomes unliveable.

Don't forget that, if everybody is fighting for a BPN spot, that means that 250 000 CBX are in the BPN queue - and it also means that regular PoSP stakers will be rare, therefore earnings with regular PoSP might be even more interesting in a situation like that.

That's quite interesting. So we could only be talking about 750k coins?

whilst we are conducting these changes.... this is just an idea..

Is it maybe worth while to x100 the minting obviously everyones balance goes x100

75million seems a more useable kind of number.

Also it seems a strange thing to say but a huge proportion of noobs here do not comprehend that the projects assumed value is the market cap. They think the cheap the single unit or token the cheaper the deal they are getting. This has actually caused a huge rise in % on low sat value coins.

Now you may believe that only someone crazy would actually invest on a per token value basis, but Byteballs entire community has been pressuring tonych to change from gigabyte to megabyte for ages now due to the constant and apparent (when reading multitudes of threads) stating by noobs that iota is better value because it is cheaper. They obviously are only taking into account the unit value. When confronting them on this and telling them to look at market cap not unit price they still seem unable to accept this. Most will say it is easier for something to go from 1c to 2c than from 1000 to 2000 bucks.

Also if we are talking really about 750k useable coins if you were to get any kind of uptake at all then every transaction would be 0.000?


However since CBX is going for a storage of wealth like bullion status then this may not be a good idea and we could leave it as is.


Just an idea of course and possibly not a great one depending on how you look at it.

I've just done the tedious task of adding up all the CBX in the top 500 addresses that haven't been active for over 1000 days.

193193.15 CBX

I would presume most of these lost or forgotten. The actual amount of lost CBX could be at least 250K or more.

I have to agree with the points brought up by others.

I am also wondering how the BPN list of 125 will be decided. From my understanding the top 3 wallets/people could take up 75 spots and top 6 wallets/people could completely fill out the 125 BPNs. I understand rewarding the people that have stuck around the longest or have accumulated the most coins but curious as how this will be worked out with other people having over 2000+CBX.

I know that I wouldn't want to put my stack into a que if I wasn't getting rewarded and never knowing how long(if ever) it would be that I would get my higher reward.

Also, what is the point of having your vault running if you aren't earning interest while queued? Won't you be at high risk of missing the 12 hour deadline if your node becomes active? Why bother even buying or joining the queue in the first place.....