getting a lot of "transaction is too large, transaction cannot be created" errors for some reason, can't even send 30 SRC :<
This is probably due to p2pool payments. You are getting too many fractions of payments so it affects the way you can pay out.
Same issue here after using a p2pool for long enough. Are there any solution? TIA
Also, if any of p2pool node hosters here are interested, I can post my networks.py so we can turn our separate nodes into true p2pool.
Thats one of the reasons why i blocked the p2p port of my pool. I also discussed this with other p2pool operators for QRK a while ago and we agreed that with the lower diff we still have, it's ok to have separate standalone pools.
Creating one big p2pool network would create even more tiny fractions than standalone pools. Also if it's one big decentralized p2pool network, or many seperate p2pools both is a decentralization and good for the coin network
The wallet has that nasty behavior when sending out money to behave like the following:
If it finds a received transaction with the exact amount you try to send, it uses this.
If not it tries to assemle the needed amount from smaller amounts IMHO starting at the smalles amount it has. That way the final transaction will consists of thousend mini-inputs and will be to large.
So as stated you will need to send smaller transactions (smaller in the amount of inputs, i think you can look that up in the logfile of the wallet). After that transaction succeded all used mini-imputs are now consolidated as a new bigger input for the next transaction.
The multiple algorithms listed for this coin, are they all used in every block of the blockchain, or do they take turns and individual block only gets worked on with one or two of the algorthms?
(Sorry if the question has been asked before.)
For every block all of those hashing algorithms are used sequentially and often more than once. That more than once thing is determined randomly simplified spoken.
