I suggest that you do not support or post on VC threads if you have problem with the coin/code. We have enough of your BS posts. Stick to other coins.
A reply of yours, quoted below, was deleted by the starter of a self-moderated topic. There are no rules of self-moderation, so this deletion cannot be appealed. Do not continue posting in this topic if the topic-starter has requested that you leave. You can create a new topic if you are unsatisfied with this one. If the topic-starter is scamming, post about it in Scam Accusations. well here's looking forward to a nice new clean launch  if the pre-mine is going to be adequately transparent i'll be happy to build a Mac qt. this is the last time I am telling u get the fuck of my coin. Shiit like u are not welcome here. Go to ur BS Coin.
this is the last time I am telling u get the fuck of my coin. Shiit like u are not welcome here. Go to ur BS Coin.
just post in yr OP about the premine. i don't care that you have so many coins, i only care you are hiding them. No one cares ur twitter or BS threads. u seems very desperate. U must have done something that caused ur own coin to tank, did u cheated them & disappear with their BTC.
Stay fucking off our coin. You are not welcome anymore.
Please beware of the scam artist with user id BumbaCoin?
Do not pay him with BTC? cannot be trusted.
Very careful if you are mining it or Bumbacoin ask you to pay upfront.
|
|
|
|
lmao. QUESTION : how does the block reward work for this coin  first hundred block reward does not seem to match the code. https://github.com/vcoin-z/virtualcoin/blob/9.2.0/src/main.cpp#L1324or i forked it also https://github.com/bumbacoin/virtualcoin/blob/9.2.0/src/main.cpp#L1324for some random reason dev sent me 100k VC. i had looked at block rewards previously, and i obviously don't fully appreciate their subtlety. but it appears on a cursory inspection that the max block reward is 50 coins, so for the life of me i dinna ken where 100k would've come from to be randomly sent to me. ... EDIT. i was pretty confused by the reward schedule, but after a bit of looking i realised it was reasonably straight forward, hidden in plain sight as it were if(nHeight >= 100 && nHeight < 3000) { if((nHeight >= 101 && dDiff > 75) || nHeight >= 1000) { // 222000/(((x+2600)/9)^2) nSubsidy = (222000.0 / (pow((dDiff+2600.0)/9.0,2.0))); if (nSubsidy > 25) nSubsidy = 5; if (nSubsidy < 5) nSubsidy = 1; } else { nSubsidy = (1112.0 / (pow((dDiff+51.0)/6.0,2.0))); if (nSubsidy > 500) nSubsidy = 5; if (nSubsidy < 25) nSubsidy = 1; } } else { nSubsidy = (1111.0 / (pow((dDiff+1.0),2.0))); if (nSubsidy > 500) nSubsidy = 5; if (nSubsidy < 1) nSubsidy = 1; nSubsidy = pow (11.0, 6.0);
} mystery solved nSubsidy = pow (11.0, 6.0); is 11^6 = 1771561
and introduced a shiny new 387,420,489 coin premine instead !!! such joyhttps://bitcointalk.org/index.php?topic=1751957.msg17500726#msg17500726 |
|
|
|
another scam coin seems to be virtual coin, currently "hiding" their 387,420,489 coin premine https://bitcointalk.org/index.php?topic=1751957.0i had an amusing discussion with an Indonesian(?) person about their attempts to compile the src (which was pretty fucked up for a bit), it boiled down to them wanting to mine because of a tweet that suggested #VirtualCoin worth $100 EACH Not selling anything below that. https://mobile.twitter.com/PayTM_/status/827697763513020417i wonder if something like a forum or wiki might be good for listing scam coins? |
|
|
|
the code has been *mostly* fixed now. here's an amusing discussion i had with someone about how to compile it before it was fixed. https://github.com/vcoin-z/virtualcoin/issues/3still has a slight problem with a non compilable leveldb, so you need to copy that from another coin. but while we're talking about scams  block 11 has a reward of 387,420,489 coins the code is deliberately confusing. int64 static GetBlockValue(int nBits, int Vcoinh, int64 nFees) { double dDiff = (double)0x0000ffff / (double)(nBits & 0x00ffffff); /* fixed bug caused diff to not be correctly calculated */ if(Vcoinh > 100 || fTestNet) dDiff = ConvertBitsToDouble(nBits); int64 Vcoinr = 50; if(Vcoinh >= 1 && Vcoinh < 1000) { if((Vcoinh >= 101 && dDiff > 75) || Vcoinh >= 1000) { // 222000/(((x+2600)/9)^2) // Vcoinr = (222000.0 / (pow((dDiff+2600.0)/9.0,2.0))); Vcoinr = dDiff * .4356; if (Vcoinr == 25) Vcoinr = (1 + 250.00) - (Vcoinh / 4); if (Vcoinr == 5) Vcoinr = 250.00 - (Vcoinh / 4); } else { Vcoinr = dDiff * .4426; // Vcoinr = (1112.0 / (pow((dDiff+51.0)/6.0,2.0))); if (Vcoinr == 500) Vcoinr = (5 + 250.00) - (Vcoinh / 4); if (Vcoinr == 25) Vcoinr = 250.00 - (Vcoinh / 4); if (Vcoinh > 10 && Vcoinh < 12) Vcoinr = pow (pzx,pzy); } } else { Vcoinr = dDiff * .4826; // Vcoinr = (1111.0 / (pow((dDiff+1.0),2.0))); // if (Vcoinr > 500) Vcoinr = 250.00 - (Vcoinh / 4); // if (Vcoinr < 1) Vcoinr = 250.00 - (Vcoinh / 4); // Vcoinr = 1; } see this thread of mine. https://bitcointalk.org/index.php?topic=1751957.0amusingly enough this has been an ongoing trick for a couple of re launches of the same coin a few times (all the way back to 2014 i think - which explains the old genesis block) they re-released with version 13.0.8 about a month ago with a slightly smaller "hidden premine" of 170million (which also featured in earlier version of coin) https://bitcointalk.org/index.php?topic=557946.msg17500615#msg17500615. so far dev has been locking the old and making new threads, completely ignoring it and now also deleting posts with situations like this, you can play spot the sockpuppet this is the last time I am telling u get the fuck of my coin. Shiit like u are not welcome here. Go to ur BS Coin.
No one cares ur twitter or BS threads. u seems very desperate. U must have done something that caused ur own coin to tank, did u cheated them & disappear with their BTC.
Stay fucking off our coin. You are not welcome anymore.
|
|
|
|
How much cost of annually NODE HOSTING, and this node is setup. also what is this NODE HOSTING future?
i'll do an annual node for $60 US, (i'm upgrading monthly price to $5.50) *(depending on a quick review) it will not be accessible by anyone else (except the coin network of course). what do you mean by FUTURE? if you want an annual node i'll put it up for 12 months. then we'll see what's happening at the end. |
|
|
|
github source has been updated, assumedly to current version. the reward schedule does not seem to have appreciably changed pre-mine is evident amongst the confusion of the code. if (VcoinHT > 10 && VcoinHT < 12) VcoinRD = pow (pzx,pzy); with int pzx = 3; int pzy = 4*4+2; block 11 will have a reward of 3^18= 387420489 https://github.com/vcoin-z/virtualcoin/blob/9.2.0/src/main.cpp#L1349. the reward for block 11 is not clearly included in source, the obvious way would be a single line with all relevant info, if (VcoinHT =11) Vcoinr = 387420489 instead 11 is obfuscated, VcoinHT > 10 && VcoinHT < 1 the whole reward schedule is confusing as fuck. and the use of pow (pzx,pzy) (which is a relic of age old Virtual Coin source) i assume pow is used as it is very similar to PoW and is overtly less suspicious than a direct value, but pzx and pzy are declared seperately at https://github.com/vcoin-z/virtualcoin/blob/9.2.0/src/main.cpp#L52 and L57 with the added bonus of pzy also not being a simple clear value, but rather 4*4+2 |
|
|
|
|
okay, so as expected block 12 contains a large amount of coins.(blocks 11 and 13 both show 0 coins)
"txid" : "7b4d0e0ebe43c0c8e7b2a842bfc803ef84ced6cd67bd9d09309d19eee9e0645c",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"coinbase" : "5c0101062f503253482f",
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 387420489.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "024cfbb1b3529e2b79b1d4aa1d04471f827fb4fafaca19a7159bf6ec11a5c12cd4 OP_CHECKSIG",
"hex" : "21024cfbb1b3529e2b79b1d4aa1d04471f827fb4fafaca19a7159bf6ec11a5c12cd4ac",
"reqSigs" : 1,
"type" : "pubkey",
"addresses" : [
"VVx2Y6TLchaRAHphTde5ysqv7Y8mLVnuav"
]
and a getinfo
{
"version" : 140001,
"protocolversion" : 70029,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 58,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 6.98429165,
"testnet" : false,
"keypoololdest" : 1486087961,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
block 58 gives a reward of 1 VC

{
"txid" : "a6f9f409150fec6b3fbc55d065eddd8724d9aa88a201732a01df7a9641ff60e9",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"coinbase" : "013a02cd01062f503253482f",
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 1.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "0246ba16cfa3782b55129b74d77ddac763eee1503db3f261e4ce10eb36512d4fcd OP_CHECKSIG",
"hex" : "210246ba16cfa3782b55129b74d77ddac763eee1503db3f261e4ce10eb36512d4fcdac",
"reqSigs" : 1,
"type" : "pubkey",
"addresses" : [
"VWjXrxRZSRKGsUYRKmZuLJfGaVdSMjSko5"
]
}
}
]
}
block 57, 1 coin to VVRUBuL9JGudzoG1zCf7CbepMAmzHqRXkp
block 55, 1 coin to VBbkyGZR6TyWZLxgHPMbrck8oChWSURyJG
seems that the code base generates a new address for each block mined perhaps?
NOTE. to see this information you need a full indexed copy of the blockchain,
to do this you need to restart with
txindex=1
in the conf file.
then to get all info's the following commands are used,
getblockhash
getblock
getrawtransaction
decoderawtransaction
|
|
|
|
i've decided to keep an eye on VC as it seems an effort in scam pre-mine. mainly cos of the amusing way they "hid" the pre-mine. just re-released yet again as version 14.0.2 and they have not updated the github source, i assume because i've been looking at the code and pointing out the premine blocks. so instead will have to settle for downloading the windows qt and trawling the first 20 or so blocks to see what happens. EDIT. apparently the win qt is 150 megs, seems excessively large AND can't unzip it as it's password protected.. havent tried installing yet. need a VM :p https://drive.google.com/uc?export=download&id=0B0du_MpVWXexbl9KYm9WcWtfb0Uhttps://bitcointalk.org/index.php?topic=1775186.. can't unzip, but the installer generates a ~24 mb qt, and the roaming folder, i dont have any anti virus installed on teh VM so no idea what else it's doing, but a scan with Trend Micro HouseCall revealed no problems. |
|
|
|
new win32 qt is now available featuring split and combine thresholds,
to set you will need to modify your bumbacoin2.conf, included in the zip is a conf file you can use to modify. it should just work with no extra effort. but to be safe as always, back your data uphttps://drive.google.com/open?id=0B5j8d4FSc7drNHF4Z2NxV2R5Qzgbranch has been integrated into main git, but not release on github as yet https://github.com/bumbacoin/bumbacoin2-source/and source https://github.com/bumbacoin/bumbacoin2-test/tree/stakeTestingto utilise the new variables. two lines to include in your conf to adjust are, (these figures below are the default settings). splitthreshold=50 combinethreshold=5000 also to note, max split amount is 5,000 max combine amount is 100,000 +++++++++++++++++++++++++++++++++++++++++++++++simply, any inputs below the split threshold will not split any more, and inputs above the combine threshold will not combine any further. but there is also the wee thing about age, a staking input younger than 9 hours will consider splitting, a staking input older than 9 hours will consider combining. also coins in different addresses will not combine, so if your coins are in multiple addresses then they will not combine with each other. // so, as a vague starting point, i look at how many coins i have, and make a decision about how many inputs i want my wallet to handle, eg. 100k coins, 100 inputs, if i set the split threshold at 2000, then after each input stakes and splits 6 times it will get to around 1.5k coins, which is about 65 inputs so i could set the split a bit lower.. remembering they will only split if younger than 9 hours. as far as combining happens. if the input is over 9 hours, and under the threshold, it will combine with other inputs until total value exceeds the threshold. the obviously logic is under 9 hours, it will split to give the input less weight and hence take longer to stake, over 9 hours, then it can combine to reduce input load. thinking 100 inputs is good, i can put the combine threshold at 1000 so they will never combine over that - although, a single input that keeps staking will get larger. i hope this makes sense, this is the first time i've tried to put this to words, so perhaps the 5th draft will be clearer .. plausibly the split age could be not good. tbh, the silly maths involved in working this out is all dependent on difficulty as well. so higher diffs will make inputs take longer, so less likely to split. please let us know how your staking goes. .. using the debug console you can reveal your settings ... getinfo { "version" : "v1.1.0.1", "protocolversion" : 60014, "walletversion" : 60000, "balance" : 49683.83136928, "newmint" : 0.00000000, "stake" : 0.00000000, " split threshold" : 500.00000000, " combine threshold" : 4500.00000000, "blocks" : 1193595, "timeoffset" : -3, "moneysupply" : 21577027.66531583, "connections" : 6, "proxy" : "", etc etc
|
|
|
|
for extra lols, here's the new re-jigged Virtual Coin code. it certainly seems to me that the effort to disguise their pre-mine is highly over done. https://github.com/vcoin-z/virtualcoin/blob/9.2.0/src/main.cpp#L1326int64 static GetBlockValue(int nBits, int VcoinHT, int64 nFees)
{
double dDiff =
(double)0x0000ffff / (double)(nBits & 0x00ffffff);
/* fixed bug caused diff to not be correctly calculated */
if(VcoinHT > 100 || fTestNet) dDiff = ConvertBitsToDouble(nBits);
int64 VcoinRD = 50;
if(VcoinHT >= 1 && VcoinHT < 1000) {
if((VcoinHT >= 101 && dDiff > 75) || VcoinHT >= 1000) {
// 222000/(((x+2600)/9)^2)
<<<<<<< HEAD
// VcoinRD = (222000.0 / (pow((dDiff+2600.0)/9.0,2.0)));
VcoinRD = dDiff * .4356;
if (VcoinRD == 25) VcoinRD = (1 + 250.00) - (VcoinHT / 4);
if (VcoinRD == 5) VcoinRD = 250.00 - (VcoinHT / 4);
}
else {
VcoinRD = dDiff * .4426;
// VcoinRD = (1112.0 / (pow((dDiff+51.0)/6.0,2.0)));
if (VcoinRD == 500) VcoinRD = (5 + 250.00) - (VcoinHT / 4);
if (VcoinRD == 25) VcoinRD = 250.00 - (VcoinHT / 4);
if (VcoinHT > 10 && VcoinHT < 12) VcoinRD = pow (pzx,pzy);
}
} else {
VcoinRD = dDiff * .4826;
// VcoinRD = (1111.0 / (pow((dDiff+1.0),2.0)));
// if (VcoinRD > 500) VcoinRD = 250.00 - (VcoinHT / 4);
// if (VcoinRD < 1) VcoinRD = 250.00 - (VcoinHT / 4);
// VcoinRD = 1;
=======
nSubsidy = (222000.0 / (pow((dDiff+2600.0)/9.0,2.0)));
if (nSubsidy > 25) nSubsidy = 5;
if (nSubsidy < 5) nSubsidy = 1;
} else {
nSubsidy = (1112.0 / (pow((dDiff+51.0)/6.0,2.0)));
if (nSubsidy > 500) nSubsidy = 5;
if (nSubsidy < 25) nSubsidy = 1;
}
} else {
nSubsidy = (1111.0 / (pow((dDiff+1.0),2.0)));
if (nSubsidy > 500) nSubsidy = 5;
if (nSubsidy < 1) nSubsidy = 1;
nSubsidy = pow (11.0, 6.0);
>>>>>>> origin/9.2.0
}
if(VcoinHT >= 1000 && VcoinHT < 6000)
{
<<<<<<< HEAD
VcoinRD = dDiff * .4726;
// VcoinRD = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0)));
// if (VcoinRD > 25) VcoinRD = 5; // increase from 25 to 50 per block
// if (VcoinRD < 5) VcoinRD = 1; // increase from 5 to 10 per block
=======
nSubsidy = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0)));
if (nSubsidy > 25) nSubsidy = 5; // increase from 25 to 50 per block
if (nSubsidy < 5) nSubsidy = 1; // increase from 5 to 10 per block
>>>>>>> origin/9.2.0
}
if(VcoinHT >= 6000)
{
<<<<<<< HEAD
VcoinRD = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0)));
if (VcoinRD > 25) VcoinRD = dDiff * .4356; // increase from 25 to 50 per block
if (VcoinRD < 5) VcoinRD = 1; // increase from 5 to 10 per block
=======
nSubsidy = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0)));
if (nSubsidy > 25) nSubsidy = 2; // increase from 25 to 50 per block
if (nSubsidy < 5) nSubsidy = 1; // increase from 5 to 10 per block
>>>>>>> origin/9.2.0
}
// printf("\n \n height %u diff %4.2f reward %i \n \n", Vcoin.HT, dDiff, Vcoin.RD);
if (dDiff > 100 && VcoinHT <= 1000) VcoinRD = 100; // increase from 5 to 10 per block
if (dDiff > 100 && VcoinHT > 1000) VcoinRD = 50; // increase from 5 to 10 per block
if (dDiff < 0.5 && VcoinHT > 15 ) VcoinRD = 1; // increase from 5 to 10 per block
VcoinRD *= COIN;
// yearly decline of production by 20% per year, projected 3M coins max by year 20XX.
<<<<<<< HEAD
// for(int i = 17520; i <= Vcoin.HT; i += 17520) Vcoin.RD *= 0.80;
=======
// for(int i = 17520; i <= nHeight; i += 17520) nSubsidy *= 0.80;
>>>>>>> origin/9.2.0
return VcoinRD + nFees;
} in particular if (VcoinHT > 10 && VcoinHT < 12) VcoinRD = pow (pzx,pzy); https://github.com/vcoin-z/virtualcoin/blob/9.2.0/src/main.cpp#L1371with int pzx = 3; int pzy = 4*4+2; possibly block 11 will have a reward of 3^18= 387420489 ??confirmed below they're apparently having connection issues so it's impossible to connect to the network yet to actually look at the block rewards. but there is a checkpoint for block 13 so i'm guessing it's a big reward |
|
|
|
|
can't even compile the source under linux without major modifications.
i wonder why someone made such a confusing mess of the code?
|
|
|
|
well, perusing the new code shows the reward protocol to be even more confusing than before congratulations on that. however there is still definite signs of potential insta-mine with this line
nSubsidy = pow (11.0, 6.0);
https://github.com/vcoin-z/virtualcoin/blob/9.2.0/src/main.cpp#L1371
basically, if certain conditions are met, then the block reward will equal 11^6 or 1771561 coins,
(in the last iteration that was the first 100 blocks).
i'm not going to analyse that code to work out how the outcome of the new code,
easier to wait for the actual release and check out the first 100 blocks to see how the actual reward pans out.see below .. |
|
|
|
@dev i PM'ed you two weeks ago about running a node bounty.
is the bounty still relevant ?
PM replied and PIE sent (and more will come  ) thank you and good PIE to all |
|
|
|
|
@dev i PM'ed you two weeks ago about running a node bounty.
is the bounty still relevant ?
|
|
|
|
johnnysof,
as Apple mentioned.
Just edit VirtualCoin.conf file in Mac OS.
change to listen=1
port=443
& see it starts, it may not sync, but if it starts than we know new wallet will also work.
OSX Unable to bind to 0.0.0.0:443 on this computer (bind returned error 13, Permission denied) |
|
|
|
this link for mac wallet still working |
|
|
|
i agree that a reboot of the chain needs to use the 177 million coin premine to distribute coins to previous holders,
as joblessminer pointed out, we also did the same thing with bumba. relaunched bumba2 with premine distributed to prior holders of bumba1. i also recently participated in the B3 swap from one chain to another. i fully support such a premine to be used to move balances to a new chain,
but as a new comer to Virtual Coin, there is a dearth of information on such a swap. and if there is a swap, then discussion of the premine is necessary. i look forward to further discussion of how such a swap will happen.heh and also $1
|
|
|
|
|
Show Posts
