Hi,

i would just like to check something.. i was working my way through the code using your coin as an example and have noticed there may be a bug/issue..

essentially i have noticed that almost all coins define the block halfving through the following methods:

chainparams.cpp (Line 34) - This is the half every block value.

main.cpp (line 1250)  - the GetBlockValue is used to return the coin value.


your code will always return a block reward of 120 coins forever.. so there technically there is no coin cap?

is this an intended function or something you forgot to add to the code?

ok thanks all, 

i have found a really good read which is exactly the type of thing i have been looking for.  the URL is:

http://www.michaelnielsen.org/ddi/how-the-bitcoin-protocol-actually-works/

i thought i would let you guys know so you can read it if you wish or pass it on to other people wanting to learn

ok i think i have the gist of things,  thank you all for your very helpful and insightful responses

ive not been doing this long so im still getting to grips.  if you have any good material on explaining the protocol in depth that would be epic!  i have read most of the parts of the main bitcoin wiki but something that can give more of an example would be awesome!

if you cant think of anything then no worries, i always like learning by playing and you guys have been more than helpful as it is

ok,

thanks for the clarification, so the only limit on the amount of coins is relative to how much you hold in your wallet.  i can only imagine the "Transaction To Large" error occurs when the QT client variable contains a larger number than anticipated?

how many daemons are you looking to run?  HOST-32 seems a little overkill if all you are going to be doing is running the daemons.  take a look at http://www.kimsufi.com/  it is run by the same people and provide much cheaper dedicated servers

with regards to running a daemon, i assume you mean bitcoind? it should work/compile on any *nix/windows OS to be honest.. im only just getting to grips with the API myself so i cant help much there with the exception that if your going to access the API externally you need to make sure access is restricted to trusted IP addresses only... you dont want everyone attempting to access your API.

ahh ok,

previously i have tried to send a large amount of coins (admittedly with altcoins) and have received errors "Transaction To Large", when i sent smaller amounts they were sent with no problem.  which lead me to believe that there is some arbitrary limit..  i am trying to compile a DB on the various characteristics of altcoins and thought this would be another neat field.

i am no C programmer but from my limited knowledge from what i see, the only restriction is possibly based on the size of the transaction? i've only been at this a couple of weeks so im just looking for confirmation whether an arbitrary value exists or if it is possible to quickly determine whether sending a large amount of coins would be successful (assuming i have the volume of coins already in my wallet).

Hi,

i have been looking into the bitcoin source and to try and understand each coin's characteristics from a code perspective.  i am having trouble in identifying the constant that determines the maximum amount of coins you are permitted to send in one go (e.g Send X amount of coins from Personal/Wallet A to Person/Wallet B).

can anyone give me any pointers as to where in the code this check is made?  i know there are checks to determine whether the maximum transaction size is too big.. i assume its somehow tied into that.  if that is the case does anyone have any rough equation i can put in to get the number out (i know the max amount varies per coin) or can they point to the lines of code that contain the upper limit checks.

my main goal is to produce a small database of various alt coins and hold stats on them (one of which is the max amount of coins permitted per transaction).. now i know each altcoin can be coded slightly different but they are all forked from the main bitcoin code so if i can understand where and why in the bitcoin code then it should be easy to identify it in the other coins.


any help would be greatly appreciated!

Hi,

i have been looking into the bitcoin source and to try and understand each coin's characteristics from a code perspective.  i am having trouble in identifying the constant that determines the maximum amount of coins you are permitted to send in one go.

can anyone give me any pointers as to where in the code this check is made?  i know there are checks to determine whether the maximum transaction size is too big.. i assume its somehow tied into that.  if that is the case does anyone have any rough equation i can put in to get the number out (i know the max amount varies per coin) or can they point to the lines of code that contain the upper limit checks.

my main goal is to produce a small database of various coins and hold stats on them (one of which is the max amount of coins permitted per transaction).



any help would be greatly appreciated!

The coin hit CoinEX today!

i think so.. they said they need security guys and no one has responded to me.. the coin is also tanking hard.. do they know something we dont?

thats fair enough and a sensible approach

any idea on timelines? ;-D

I agree,  there needs to be some service/use for the coin other than trading on an exchange.  that will raise its profile to the point where it will hit an exchange.

i believe cassie is working on bitbay? i dont know if it will take QBT and/or how far along the service is tbh.

Hi,

i am a penetration tester, my time is extremely limited and i cant promise much i would be willing to go over everything and see if i can highlight any issues.

are there any rewards for such a thing?

ahhh, very well done.  im really happy you managed to get this issue resolved

have you managed to get anyone to look at this?

ahh ok, thank you for clearing that up.. so at the minute this is more of a theoretical attack where he has stacked the cards in his favour.

thanks for the link, so all addresses are affected regardless of the client (due to them being based off the same RNG weakness), has this weakness not been resolved in newer versions of OpenSSL?  if so could it be worth upgrading OpenSSL and recompiling the wallet or have i completely missed the point?

in the mean time, services that use public wallets would have to generate new addresses (to send and receive money periodically?).  whats stopping someone going after the public key of an exchange like cryptsy, what would a service like this do to mitigate this issue?




it would be great to identify whether your key is particularly weak and more susceptible and to also identify the risks of services using the same wallet to send and receive payments.. are they going to have to change their addresses regularly from now own just to avoid this attack?

so it is possible to identify weak private keys if they are close to any of the rendezvous points on your eliptic curve.

my questions would be:

Are standard wallets (the addresses generated by the QT client) affected by this?
are there any mitigations that can be used?
will the pub/priv key generation sequence require a new, more secure implementation?

i believe one already has been outlined of moving the coins to a new address/wallet? every few months?  would there be any way in which it is possible to increase the difficulty of the private keys?

to be honest i really wished this coin would have made it, but its not obvious the client was not tested and the person who released it doesnt know how to fix it which doesnt give the coin much legs to stand on.  even if this issue was fixed.. whats going to happen at the next issue (we are already at v3).

im really sad that this could be the nail in the coffin for this coin.

if it doesnt get resolved soon this is going to go the way of CENT/PENNIES and will not get picked up by any other exchanges!