◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[tommyj1]

what to do?

Code:

could not allocate vin for collateral address

[1714763303]

1714763303

[1714763303]

1714763303

[1714763303]

1714763303

[1714763303]

1714763303

[1714763303]

1714763303

[thelonecrouton]

what to do?

Code:

could not allocate vin for collateral address

What were you doing that produced this error?

[antonio8]

what to do?

Code:

could not allocate vin for collateral address

What were you doing that produced this error?

Looks like this is an error when trying to start a BN in the wallet that is not properly funded.

Go ahead and create a BN and start it and you will get the message.



On a side note having all kinds of issues with the wallet (0.30.16.8final and 0.30.16.8b) when trying to send to BN address it takes forever and then I get a message that transaction amount is too large.

If I click on it while waiting because I think it did not send it freezes and I have to restart the wallet.

Have to restart the wallet about 5 or 6 times and when it finally does it resyncs to wallet from day 1.

Right now the wallet should be the main focus of this project. We should not have to redownload the block chain or add this or delete that to get it to work correct.

[bitcreditscc]

what to do?

Code:

could not allocate vin for collateral address

What were you doing that produced this error?

Looks like this is an error when trying to start a BN in the wallet that is not properly funded.

Go ahead and create a BN and start it and you will get the message.



On a side note having all kinds of issues with the wallet (0.30.16.8final and 0.30.16.8b) when trying to send to BN address it takes forever and then I get a message that transaction amount is too large.

If I click on it while waiting because I think it did not send it freezes and I have to restart the wallet.

Have to restart the wallet about 5 or 6 times and when it finally does it resyncs to wallet from day 1.

Right now the wallet should be the main focus of this project. We should not have to redownload the block chain or add this or delete that to get it to work correct.

Are you using coin control?  The reason it sort of freezes when you send is because you have a ton of inputs, likely from mining and having a BN. To avoid this, select the inputs you want to spend in coin control and it will be immediate.

Fixing the wallet is one of any things that need doing, but as you know the developers are few and far between. However this is a priority because if it performs this slow then it can never run a useable colored coins engine.

[thelonecrouton]

On a side note having all kinds of issues with the wallet (0.30.16.8final and 0.30.16.8b) when trying to send to BN address it takes forever and then I get a message that transaction amount is too large.

If I click on it while waiting because I think it did not send it freezes and I have to restart the wallet.

Have to restart the wallet about 5 or 6 times and when it finally does it resyncs to wallet from day 1.

Right now the wallet should be the main focus of this project. We should not have to redownload the block chain or add this or delete that to get it to work correct.

Consolidate your thousands of small inputs into larger lumps using coin control. You are trying to broadcast a transaction that's too big in size (bytes) - you'd have the same issue with any currency's wallet.

[thelonecrouton]

Anyone remember the name of the Bittrex guy with an account here? Their wallet is locked, apparently stuck on block 145337.

edit: PM'd bittrex-matthew.

[bitcreditscc]

Anyone remember the name of the Bittrex guy with an account here? Their wallet is locked, apparently stuck on block 145337.

edit: PM'd bittrex-matthew.

bittrex-richiela

i also sent a Pm , opened a ticket and reminded on IRC

[starblocks]

If anyone gets multiple BN's running in Win 7 please let me know

Far as I got was creating 5 seperate ones in the Banknode screen in the QT (first used command: keypoolrefill 5) plus sending 50k to each, and then after restarting the QT only one BN entry shows - and this one produces the "could not allocate vin for collateral address"

Also the latest QT keeps crashing (at first start with no data folder, after a new wallet plus full sync, after re-syncing freshly etc etc) - it loads eventually but I've had to try many times sometimes

Edit: It's after creating the 5 BN's and sending the collateral and restarting the QT that they don't display properly nor can be started/used only 1 displays - the problem is here somewhere

Side note: Instead of sending 50k each to multiple new BN addresses you could just send to one seperate address in your wallet and use the "move" command to move 50k to each BN you create saving a little trouble I suppose I discovered: move "fromaccount" "toaccount" amount

[antonio8]

what to do?

Code:

could not allocate vin for collateral address

What were you doing that produced this error?

Looks like this is an error when trying to start a BN in the wallet that is not properly funded.

Go ahead and create a BN and start it and you will get the message.



On a side note having all kinds of issues with the wallet (0.30.16.8final and 0.30.16.8b) when trying to send to BN address it takes forever and then I get a message that transaction amount is too large.

If I click on it while waiting because I think it did not send it freezes and I have to restart the wallet.

Have to restart the wallet about 5 or 6 times and when it finally does it resyncs to wallet from day 1.

Right now the wallet should be the main focus of this project. We should not have to redownload the block chain or add this or delete that to get it to work correct.

Are you using coin control?  The reason it sort of freezes when you send is because you have a ton of inputs, likely from mining and having a BN. To avoid this, select the inputs you want to spend in coin control and it will be immediate.

Fixing the wallet is one of any things that need doing, but as you know the developers are few and far between. However this is a priority because if it performs this slow then it can never run a useable colored coins engine.

Same thing using Coin Control. Still takes forever.

Do you have any idea why my second BN that is up and running just shuts off after about 30-40 minutes of running?

[bitcreditscc]

what to do?

Code:

could not allocate vin for collateral address

What were you doing that produced this error?

Looks like this is an error when trying to start a BN in the wallet that is not properly funded.

Go ahead and create a BN and start it and you will get the message.



On a side note having all kinds of issues with the wallet (0.30.16.8final and 0.30.16.8b) when trying to send to BN address it takes forever and then I get a message that transaction amount is too large.

If I click on it while waiting because I think it did not send it freezes and I have to restart the wallet.

Have to restart the wallet about 5 or 6 times and when it finally does it resyncs to wallet from day 1.

Right now the wallet should be the main focus of this project. We should not have to redownload the block chain or add this or delete that to get it to work correct.

Are you using coin control?  The reason it sort of freezes when you send is because you have a ton of inputs, likely from mining and having a BN. To avoid this, select the inputs you want to spend in coin control and it will be immediate.

Fixing the wallet is one of any things that need doing, but as you know the developers are few and far between. However this is a priority because if it performs this slow then it can never run a useable colored coins engine.

Same thing using Coin Control. Still takes forever.

Do you have any idea why my second BN that is up and running just shuts off after about 30-40 minutes of running?

once you have consolidated , it will speed up. I recommend doing that once a week.

[thelonecrouton]

Same thing using Coin Control. Still takes forever.

Do you have any idea why my second BN that is up and running just shuts off after about 30-40 minutes of running?

Select less inputs. In the top left of the coin control window you can see the size in bytes of your transaction. Adding more inputs increases this. Try to keep it under 5000 bytes at a time.  

I think your other problems are from the use of the Create Banknode tab. All it does is generate a new address for you to send the collateral to, and gives you a suggested bitcredit.conf. It got borrowed from Crave and wasn't much actual use for them either, we haven't got around to improving it.

You still need to run a separate instance of bitcreditd per BN on your VPS, or on your home box, with the appropriate bitcredit.conf file for each one.

Things would be easier if start-many/banknode.conf worked but you still need separate clients running somewhere.

[antonio8]

@bitcreditscc and @thelonecrouton

Got everything going correct and yes I had too big of transactions in Coin Control. That is a PITA with all the small transactions.

Set up BN instead of using the tab. Now just looking for a way to filter my ip in the BN list (I will try the VPS later) for now just want to run it from the wallet to see how it goes.

Thanks

[bitcreditscc]

@bitcreditscc and @thelonecrouton

Got everything going correct and yes I had too big of transactions in Coin Control. That is a PITA with all the small transactions.

Set up BN instead of using the tab. Now just looking for a way to filter my ip in the BN list (I will try the VPS later) for now just want to run it from the wallet to see how it goes.

Thanks

all good, i am sure everyone will get it done soon enough, price is just right for new comers to get a cheap BN too.

[dragos_bdi]

I think there are some problems on syncing the banknodes with the network and from here the whole network have problems. I susspect that at least 30 BN are out of sync.
The problem reside from the fact that all banknodes are started on non standard port 8877 on witch the wallet try to connect. From here the poor distribution of banknodes and poor connections count on wallet.

@ hack_
198.52.160.59, 198.52.160.60, 198.52.160.64 being the main nodes, please start on each server on port 8877 a banknode.

@ all banknode owners
Please run a BN on the main port 8877.

Thanks

Edit: @ hack_, please put maxconnection to at least 256 on main nodes

[bitcreditscc]

For those who are wondering about why i am pushing for a multi-tier system :- https://bitcointalk.org/index.php?topic=532.msg6306#msg6306

[bitcreditscc]

I think there are some problems on syncing the banknodes with the network and from here the whole network have problems. I susspect that at least 30 BN are out of sync.
The problem reside from the fact that all banknodes are started on non standard port 8877 on witch the wallet try to connect. From here the poor distribution of banknodes and poor connections count on wallet.

@ hack_
198.52.160.59, 198.52.160.60, 198.52.160.64 being the main nodes, please start on each server on port 8877 a banknode.

@ all banknode owners
Please run a BN on the main port 8877.

Thanks

Edit: @ hack_, please put maxconnection to at least 256 on main nodes

The port BNs are broadcasting is the RPC port , not the listen port, they are all using default unless specifically changed

[dragos_bdi]

I think there are some problems on syncing the banknodes with the network and from here the whole network have problems. I susspect that at least 30 BN are out of sync.
The problem reside from the fact that all banknodes are started on non standard port 8877 on witch the wallet try to connect. From here the poor distribution of banknodes and poor connections count on wallet.

@ hack_
198.52.160.59, 198.52.160.60, 198.52.160.64 being the main nodes, please start on each server on port 8877 a banknode.

@ all banknode owners
Please run a BN on the main port 8877.

Thanks

Edit: @ hack_, please put maxconnection to at least 256 on main nodes

The port BNs are broadcasting is the RPC port , not the listen port, they are all using default unless specifically changed

Are you right, but because all are running on the same machine at least 5 BN, only on one BN can be used port=8877 and rpcport=8878.
from that 5 BN, one must use this settings, but I'm afraid that almost all use different settings, and no one use default settings.

[alganonim]

So to set up 5 BNs on 1 VPN, I should configure ports in that way ?

1st BN , port=8877 , rpcport=8878

2nd BN, port=8876 , rpcport=8879

3rd BN, port=8875 , rpcport=8880

4th BN, port=8874 , rpcport=8881

5th BN, port=8873 , rpcport=8882

....

port decreasing, rpcport increasing to make it simple, I got it right ?

[bitcreditscc]

So to set up 5 BNs on 1 VPN, I should configure ports in that way ?

1st BN , port=8877 , rpcport=8878

2nd BN, port=8876 , rpcport=8879

3rd BN, port=8875 , rpcport=8880

4th BN, port=8874 , rpcport=8881

5th BN, port=8873 , rpcport=8882

....

port decreasing, rpcport increasing to make it simple, I got it right ?

1st BN , listen=8877 , rpcport=8878

2nd BN, listen=0 , rpcport=8879

3rd BN, listen=0  , rpcport=8880

4th BN, listen=0  , rpcport=8881

5th BN, listen=0  , rpcport=8882

is how most are doing it. so yeah maybe try your way and tell us the results.

[alganonim]

Now I'm even more confused ..

listen= shouldn't be 1 or 0 just like daemon and server ?

and port=8877   the same as for exapmle 171.52.160.60:8877 ?


rpcuser=Change-This
rpcpassword=Change-This-Also
rpcallowip=127.0.0.1
rpcport=8776
daemon=1
server=1
listen=0
maxconnections=256
banknode=0
banknodeprivkey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
banknodeaddr=xxx.xxx.xxx.xxx:xxxx
addnode=198.52.160.59
addnode=198.52.160.60
{sometimes I see also the same port as at the end of banknodeaddr=}
port=xxxx
{and additional}
genproclimit=0
logtimestamps=1