 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
|
Thank you for letting me know about the Cuckoo Cycle algorithm. I remember hearing it once, but never did a deeper digging on how it works. Will definitely now.
After some research I have concluded that the original TSP does not fit as PoW since verifying the solutions requires NP time.
However, in a modified version of TSP where we try to find a route < GIVEN_LENGTH the solution verification can be done in P time.
|
|
|
|
|
Hi
I'm just wondering if the Travelling salesman problem could be used as a PoW algorithm?
|
|
|
|
@voileipa I've paid for a YourCoin, but the generation is currently at: 2015-04-22 19:04:16,419 : Coin request received
2015-04-22 19:04:16,782 : Confirmation email sent
2015-04-22 19:05:13,860 : Confirmation received
2015-04-22 19:44:02,333 : Payment received: 0.075 BTC
2015-04-22 19:44:02,338 : Payment confirmed
2015-04-22 19:44:02,344 : Waiting for unique genesis block... This is the status since 2 days. I tried to contact you via email, twitter, again email... No answer. Now I'm trying it here. I'll send you a PM in some minutes. Please solve this issue. EDIT: This problem is solved, thanks.We were having a brief shortage of SHA256 genesis blocks. Hi, why is not possible to create a pos coin?
thanks
Well.. it would require some implementation and there is not too much demand for that... |
|
|
|
|
Support for x11 algorithm added.
|
|
|
|
Warning!!! You can lose bitcoins.Too risky, the step is too much, "Send 0.1 BTC to address ADDRESS1" its so big amount  ~iki I guess the "risk" lies more on the side of "creating a raw transaction in command line" rather than in the "delayed transaction" concept itself. |
|
|
|
You can create a delayed bitcoin transaction quite simply. Donīt pay trancastion fee.  Haha. Broadcast and pray. |
|
|
|
I see this is to "authorize" destination address to broadcast the transaction where the coins are sent to him. There's no way to automate that, is it? I mean in the bitcoin protocol itself. Of course such a service could be developed. Yeah. The "owner" of the destination address must broadcast the transaction. |
|
|
|
Hi, do you know if it is possible to obtain genesis with pos coins without fixed block value?
thanks and your software is amazing
Can you be more specific? The script accepts a value parameter: -v VALUE, --value=VALUE
the value in coins for the output, full value (exp. in bitcoin 5000000000 - To get other coins value: Block Value * 100000000) |
|
|
|
Are anybody able to connect a JSON RPC to their coincreator wallets?
Remember to add the server=1 in your conf file so the qt wallet opens the rpc port. |
|
|
|
|
>bitcoin derivative services
>accepting fiat
whatttt
|
|
|
|
If all TxIn inputs have final (0xffffffff) sequence numbers then locktime is ignored. Thanks for the response. I set the sequence number to 0 and after that my bitcoind didn't broadcast the transaction until the given block height was reached: >./bitcoin-cli sendrawtransaction $SIGNED_RAW_TX
error: {"code":-26,"message":"64: non-final"} After the block height was reached I finally got the transaction in the block chain as expected: https://blockchain.info/tx/d61839fb690395ba638ba804c5af4bf0111ff269ca1e0b251cff737ca6189557I hope all nodes will relay (now and in future) transactions with custom nLockTimes and sequences! |
|
|
|
|
I'm trying to create create a delayed transaction for myself. I'm using nLockTime and the following steps. The situation what I'm trying to reach is that there are 1 BTC that is not reachable until 10 000 blocks are found.
Are the following steps correct?
1. I create a new key-address pair. (KEY1 1Address1)
2. I send 1BTC to address 1Adddress1
3. I create new key-address pair. (KEY2 1Address2)
4. I create a transaction with nLockTime (currentblockheight + 10000). The input is 1Address1 and output 1Address2. I sign it with KEY1. HOWEVER, I do not broadcast the transaction.
5. I destroy KEY1.
6. Now I have a transaction, which is now valid until 10 000 blocks are found and I store it. After 10 000 blocks are found I broadcast the transaction and unlock the bitcoins with KEY2.
Does this work or can I just replace the nLockTime in the transaction with 0, so the transaction becomes instantly valid?
|
|
|
|
|
Unlike most altcoins, there would be no reward halving: e.g. every block will _always_ contain 1000 coins.
This way, there is really no "incentive" to mine and hold coins. But they can be spent e.g. for voting or injecting stuff to the blockchain.
Just popping some ideas here..
|
|
|
|
Altcoin where coins become unusable after some time? (so you have to use them)
Are there any?
i dont really see a point for this, as you can always send coins to different addresses you have control of. The coins would be traced to the block they were created in. If that block is e.g. "1000 blocks old" the coins are invalid. |
|
|
|
|
Added X11/X13/X15 support.
|
|
|
|
|
Altcoin where coins become unusable after some time? (so you have to use them)
Are there any?
|
|
|
|
|
