Bitcoin Forum
November 12, 2025, 03:33:03 PM *
News: Latest Bitcoin Core release: 30.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 [2] 3 4 5 6 7 8 9 »
21  Bitcoin / Project Development / Looking for the next "Steve Jobs" (well - a marketing guru at least) on: February 05, 2016, 03:39:08 PM
Actually I'm not a fan of Steve Jobs (but instead of Steve Wozniak as some of my earliest programming was done on an Apple ][ clone).

The CIYAM project not only has blockchain technology but Software Manufacturing technology which no other similar project can offer (yup - it is years ahead of Ethereum).

The one thing lacking is a key partner for marketing development (I understand the need for such a partnership).

If you have a vision that will work with the CIYAM open source ethos then welcome to introduce yourself (some proof of your achievements will be required and no stupid ad sig posts please).

(serious interested parties should PM me - posts are being permitted for relevant questions only)
22  Bitcoin / Project Development / Can you find a fault with this "slow" POW algorithm? (possible bounty) on: February 05, 2016, 02:31:26 PM
Now the first thing to note is that I'm going to delete any stupid posts or posts that say nothing useful (and posts that basically say "I recommend that you don't write such an algorithm yourself" will be deleted).

If you're wondering about my "ability" to create code then here are some examples of what I have done (some of which are based upon or include the work of other open source projects - so citing other open source code worth looking at is fine as a response):

https://github.com/ciyam/ciyam/blob/master/src/diff.h - an O(NP) diff implementation (that works out the "path" not just the distance)

https://github.com/ciyam/ciyam/blob/master/src/date_time.cpp - a huge amount of stuff for date and time things

https://github.com/ciyam/ciyam/blob/master/src/btree.h - a generic B+Tree implementation

https://github.com/ciyam/ciyam/blob/master/src/cache.h - a generic multi-region cache implementation

Okay - so hopefully after seeing those examples you can believe that I am not an idiot who doesn't know how to code and can therefore perhaps consider looking at the following: https://github.com/ciyam/ciyam/blob/master/src/crypt_stream.cpp#L442
(it is a memory-hard POW algo that was designed to work in a similar manner to scrypt)

It is entirely likely that I might end up using Cuckoo instead (as I quite like that algo but I just think it might be a little too complex for what I want) but for now I am using this so I'd like to see if anyone can find a serious issue with it.

(there might be a bounty offered later - but for now am just seeing if anyone is curious to take a look)
23  Bitcoin / Development & Technical Discussion / Is there really demand for a decentralised BTC to LTC exchange? on: February 02, 2016, 11:45:03 AM
Firstly note that I will be deleting posts to do with "block size" (there are plenty of other topics where you can post about that) and any pointless posts.

If you are really interested in using a decentralised BTC to LTC exchange (let's assume just those two for now) then to register your interest you'll need to provide a Bitcoin signed message for an address that has at least 1 BTC or 1000 LTC (other posts that add nothing will be deleted).

I will be checking that said messages are valid (so any that aren't will also be deleted).

Relevant questions about said decentralised exchange are welcome but not silly ones (so don't post "Can it do XYZ coin also?" and just assume that the answer to that is no for now).

The reason I am trying to get a feel for whether or not there is any actual support for this (by people who actually have BTC and/or LTC) is to avoid wasting time on development if there isn't any real interest (I suspect that there is actually very little interest).

Some points to note about the likely way that this will be implemented (assuming there was enough interest):

- there will be a web application (hosted by ciyam.org) for finding and locking into trades (and doing much of the tricky stuff necessary for ACCT using CLTV)

- there will be a special wallet that you will need to install (most likely in a VM image for added security and simplicity of installation) that uses a web UI (via a locally run web server)

- trades would not be realistically able to be performed faster than one every two hours (due to the inaccuracy of time stamps in Bitcoin and its clones and due to the fact you'd want to have at least one confirmation before proceeding at each step)
24  Bitcoin / Bitcoin Discussion / The real disastor that could happen (forking Bitcoin)... on: February 01, 2016, 04:20:24 PM
If we actually end up with a forked blockchain then we will have "two Bitcoins" (or more depending upon the software being used).

What will this do?

For a start I predict it will cause all exchanges to "stop trading" (as they will not want to risk fiat losses in case they have ended up on the wrong fork).

Once the exchanges have stopped then the miners can no longer sell their BTC block rewards so that means within a very short time there will be a serious problem in the mining area.

The amount of electricity that miners are paying for is so large that they will most likely shut down their hashing operations if the exchanges have closed down which will reduce the difficulty (in two weeks).

After two weeks if the problem hasn't been worked out then everyone is basically going to walk away and the Bitcoin experiment will be declared a failure.

This is what we are facing (so you've got to wonder why Gavin wants to try and push for this).
25  Economy / Reputation / Troll who claims they are going to sue me on: February 01, 2016, 04:12:10 PM
https://bitcointalk.org/index.php?topic=1348800.msg13743739#msg13743739

Just to make sure the troll who posted this will stick by their threat and try and sue me.
26  Bitcoin / Bitcoin Discussion / Why do we not already have a multi-sig escrow service? on: January 30, 2016, 04:49:31 PM
Seeing as there was a recent scandal with an Escrow I wonder why the existing trusted escrows don't just work together with P2SH N of M addresses for people to use with much greater confidence that they won't be scammed?
27  Bitcoin / Bitcoin Discussion / The "interblocknet" (a possible future of the service industry) on: January 30, 2016, 01:46:05 PM
What is the "interblocknet" and why does it matter?

The revolution that Bitcoin has started with money will continue with services but as we know Bitcoin will never scale to handle all of the world's transactions so how will this be managed?

IMO we are going to end up with many blockchains (most likely one blockchain per major service or even company) that allow for specific service payments which will remove the "middle-men" (i.e. websites currently who are instead replaced with "miners").

Consider something like Uber - do drivers really need to pay a % fee to a company in order to offer a service?

If there was instead a "blockchain service" whose tokens were perhaps "kms of travel" then you can do away with the centralised website and the commissions (only requiring a mining fee to keep that blockchain going).

It is possible that these will be "side-chains" although I think it might be wise to have more than one "core blockchain" (in case of systematic failure).
28  Bitcoin / Bitcoin Discussion / What is a team and what is not a team. on: January 29, 2016, 06:12:43 PM
So with all of this stupid debate about trying to replace the Core Devs with whatever thing Gavin wants to associate himself with this week (as we all know he might change allegiance next week).

Can we just instead have a team that works?

(oh - yes - we have one - but Gavin is not happy because he left and thinks that he should still be in control after he left)
29  Bitcoin / Bitcoin Discussion / Why IMO the focus needs to be on settlement and governments (and not on coffees) on: January 28, 2016, 04:29:27 PM
It appears that most of the (more vocal) forum members here don't think that "Satoshi's stash" is a big reason for governments to not want to use Bitcoin as a "Gold 2.0" (https://bitcointalk.org/index.php?topic=1343072.0) and maybe that what is most important is the promise to keep the supply fixed at 21M.

But I think the announcement made by the PBOC that China is considering to soon release its own "nationalised" digital currency should be something of a wake-up call (http://www.cnbc.com/2016/01/20/chinas-central-bank-plans-to-launch-its-own-digital-currencies.html).

I had predicted such a thing might happen back in December of 2012 (https://bitcointalk.org/index.php?topic=129047.0) and now it looks as though this might be actually starting to happen (and no I am not working with the PBOC so don't blame me for anything other than that old topic).

I guess the question is whether or not they will fix the supply limit. If they don't then Bitcoin still has its advantage - but if they do then I think Bitcoin is going to have a big problem.

If you can buy a digital gold equivalent without any hassle (or much of a fee) from your local bank then are you going to be as motivated to want to buy into Bitcoin?

This problem will get worse if multiple countries decide to do the same thing (creating protection for their national savings from being moved offshore).

If there is little motivation to even have Bitcoin because there are local digital scarcities available that are government backed and supported then I think the arguments for being able to buy coffees for Bitcoin become simply irrelevant.

Am interested in relevant opinions but not ad sig rubbish posts or plain rubbish posts (will delete all of those).
30  Bitcoin / Bitcoin Discussion / Are Satoshi's percentage of BTC a serious problem for government acceptance? on: January 27, 2016, 04:08:33 PM
I am making this topic self-moderated to avoid nonsense posts but I won't delete any reasonable arguments on either side of this question (and yes it is my decision what is reasonable in this topic - if you don't like that then please create your own topic - it isn't that hard after all).

So - although we are seeing some governments accepting Bitcoin as having a role we are seeing others basically trying to ban it outright (Russia being the current example of this).

I wonder if part of the problem is the perception (however likely or not) that Satoshi is aligned with (or was the creation of) a government and therefore the Satoshi *stash* effectively belongs to that government (which is estimated at around 5-10% of all bitcoins).

To me it makes some sense that a country might fear that if Bitcoin were to be adopted as a "new gold" then if it turns out that one country already has 5-10% of the new gold standard then that would be a "hard pill to swallow".

I'm not advocating for "deleting Satoshi's stash" but simply raising the question that if we are wanting Bitcoin to be Gold 2.0 then perhaps this issue cannot just be disregarded.

(and no - this is not "Satoshi envy" from myself and also I think it is perhaps good to discuss something other than the block size)
31  Bitcoin / Development & Technical Discussion / ACCT using CLTV - More Effective than a sleeping pill! on: January 25, 2016, 06:00:26 PM
So using the CIYAM Trade application along with using a CIYAM console acting as a Bitcoin/Litecoin wallet I demonstrated to my wife how you could exchange LTC for BTC without a 3rd party (or fees other than tx fees) and apparently it was so boring she fell asleep.

Code:
Generating a spendable amount of RHS for "user1"...
Generating a spendable amount of LHS for "user2"...

Login as "user1" and create a Trading Pair (with Maximum Amount as at least 25) and then Logout.

Now login as "user2" and create a tx from the offer in the All Open Offers list with the following details:

Sending Amount: 25
Refund Address: mtW4pzRHXwNwkHa2mdy2EokKy5GZ4aMWtu
Receiving Address: mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT
Secret Hash: 2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b

Now login as "user1" and edit the Trade Transaction in the My Trade Transactions list with the following:

Refund Address: mids4AKKn42KmcJTvaynUzmnhWnmfgwRMw
Receiving Address: mgF67ucKz7CddjuJwDvDUgC5HiJBRDGNBx

Now login as "user2" and from the tx click on the Waiting tx and copy and paste the Sending Address:

USER2_P2SH=2N1dPcqdkNyfNqysHDqWRq8hqSs6sT91LTP

Now "user2" will send LHS to their P2SH address.

Now login as "user1" and from the tx click on the Waiting tx and copy and paste the Sending Address:

USER1_P2SH=2NFtwQWeiQzMgeidPCrZZhATv6ULXqA8WaB

Now "user1" will send RHS to their P2SH address...

[
    {
        "involvesWatchonly" : true,
        "account" : "user2 (user1's p2sh)",
        "address" : "2NFtwQWeiQzMgeidPCrZZhATv6ULXqA8WaB",
        "category" : "receive",
        "amount" : 25.00000000,
        "vout" : 1,
        "confirmations" : 4,
        "blockhash" : "55647bfcc1ea60124e3e358a046a1e6494babb666d656aec3a9ad7ea3b179e71",
        "blockindex" : 1,
        "blocktime" : 1453733457,
        "txid" : "1b0effc3dbb318d988c5f8f3525c1e79fec7f327aebbc2028274361139042870",
        "walletconflicts" : [
        ],
        "time" : 1453733457,
        "timereceived" : 1453733475
    }
]

Now enter the following from the transaction information above:
TXID=1b0effc3dbb318d988c5f8f3525c1e79fec7f327aebbc2028274361139042870
VOUT=1

Now login as "user2" and from the tx click the Receive Checked button and paste the Secret Reveal Script:
SCRIPT=76a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142
236ea542963ca5022db4332cd63aa2ed895af6888ac68

0100000001702804391136748202c2bbae27f3c7fe791e5c52f3f8c588d918b3dbc3ff0e1b01000000d44730440220456e9d366d89034c7321a900f17e60506cb9e6fb3c280587301609fda6af65
8502206d785719bc42de81ce05ac4b461fc9d4aab5286d4ec3ef8d0589ab3ed1076d7501210334ae38e2f6331bfc4832893edd540377bcfc08b1a63730339b91cf8a6e0b6636067365637265744c
6176a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142236ea
542963ca5022db4332cd63aa2ed895af6888ac68000000000100f90295000000001976a91439f079037b44caa047b19f66f9446ad29ca1835888ac00000000

Now "user2" will redeem RHS from the "user1" P2SH address tx (exposing their secret).

Balance of RHS for "user2" is:
25.00000000

Now login as "user1" and from the tx click the Receive Checked button and paste the new Check Address:
ADDR=mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT

[
    {
        "involvesWatchonly" : true,
        "account" : "user1 (user2's reveal)",
        "address" : "mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT",
        "category" : "receive",
        "amount" : 25.00000000,
        "vout" : 0,
        "confirmations" : 1,
        "blockhash" : "5ea97dcb1e76ca90ef0b71aae2208488df5d8344248be2713fbb8f1bae8a1667",
        "blockindex" : 1,
        "blocktime" : 1453733502,
        "txid" : "d374d12b0cee799e7d3b233332b87ae41f18ffae9c1a5dc49f7436df4f216fcf",
        "walletconflicts" : [
        ],
        "time" : 1453733502,
        "timereceived" : 1453733536
    }
]

Now copy and paste the secret reveal txid:
TXID=d374d12b0cee799e7d3b233332b87ae41f18ffae9c1a5dc49f7436df4f216fcf

{
    "txid" : "d374d12b0cee799e7d3b233332b87ae41f18ffae9c1a5dc49f7436df4f216fcf",
    "version" : 1,
    "locktime" : 0,
    "vin" : [
        {
            "txid" : "1b0effc3dbb318d988c5f8f3525c1e79fec7f327aebbc2028274361139042870",
            "vout" : 1,
            "scriptSig" : {
                "asm" : "30440220456e9d366d89034c7321a900f17e60506cb9e6fb3c280587301609fda6af658502206d785719bc42de81ce05ac4b461fc9d4aab5286d4ec3ef8d0589ab3
ed1076d7501 0334ae38e2f6331bfc4832893edd540377bcfc08b1a63730339b91cf8a6e0b6636 736563726574 76a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf5
27a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142236ea542963ca5022db4332cd63aa2ed895af6888ac68",
                "hex" : "4730440220456e9d366d89034c7321a900f17e60506cb9e6fb3c280587301609fda6af658502206d785719bc42de81ce05ac4b461fc9d4aab5286d4ec3ef8d0589a
b3ed1076d7501210334ae38e2f6331bfc4832893edd540377bcfc08b1a63730339b91cf8a6e0b6636067365637265744c6176a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25
fe97bf527a25b87637576a91439f079037b44caa047b19f66f9446ad29ca1835888ac6704d0dea656b17576a9142236ea542963ca5022db4332cd63aa2ed895af6888ac68"
            },
            "sequence" : 0
        }
    ],
    "vout" : [
        {
            "value" : 25.00000000,
            "n" : 0,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 39f079037b44caa047b19f66f9446ad29ca18358 OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a91439f079037b44caa047b19f66f9446ad29ca1835888ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "mkoJtKoxHmdL8aXJvPudmUgZKC1xXHb9KT"
                ]
            }
        }
    ]
}

Now copy and paste the revealed secret:
HEX_SCRT=736563726574

[
    {
        "txid" : "e6af2d2c7e6cda9ea14c166a57c83112376a39b24524b5d2b1e607d740663b71",
        "vout" : 0,
        "address" : "2N1dPcqdkNyfNqysHDqWRq8hqSs6sT91LTP",
        "account" : "user1 (user2's p2sh)",
        "scriptPubKey" : "a9145bf232454e73c9cafa022f52d819bbf59c63df1087",
        "amount" : 25.00000000,
        "confirmations" : 9,
        "spendable" : false
    }
]

Now copy and paste the P2SH txid and vout:
TXID=e6af2d2c7e6cda9ea14c166a57c83112376a39b24524b5d2b1e607d740663b71
VOUT=0

Now click the Secret Checked button and paste the Secret Reveal Script:
SCRIPT=76a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91407f8009f5b6b12a5ae10e0ae539ea06ce232cfbf88ac67047387a756b17576a9148
e6eac4b9e5944a76f2305a736ed2a7d65742f7688ac68

0100000001713b6640d707e6b1d2b52445b2396a371231c8576a164ca19eda6c7e2c2dafe600000000d4473044022027523c5d0aaf22798d0503c67c073bf4a78522d88d8128720091289845ac0f
1d022078d69e74bea88f7d727a4a04650179136ca24872477f052f58d17f825ce1b0ad01210220d666741f2e8be672556ca8f0b7a7352516422c7b7b3f0681d39adf4cabd953067365637265744c
6176a8202bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b87637576a91407f8009f5b6b12a5ae10e0ae539ea06ce232cfbf88ac67047387a756b17576a9148e6eac
4b9e5944a76f2305a736ed2a7d65742f7688ac68000000000100f90295000000001976a91407f8009f5b6b12a5ae10e0ae539ea06ce232cfbf88ac00000000

Now "user1" will redeem LHS from the "user2" P2SH address tx.

Balance of LHS for "user1" is:
25.00000000

So I've built a decentralised exchange but I am getting the feeling that I have probably wasted my time doing so (am glad it hasn't taken me more than a couple of weeks).

Does anyone really think that this kind of idea is going to work?
32  Economy / Reputation / Check out @franky1 the liar who claims he has written a Bitcoin client on: January 19, 2016, 06:21:03 PM
Before he deletes it: https://bitcointalk.org/index.php?topic=1332557.msg13607751#msg13607751

This idiot is claiming that he has written his own Bitcoin client (without even saying what language it was supposedly even written in) and then refused to show any actual evidence of it (beyond the above bullshit post).

When someone is that dishonest I don't think you should pay much attention to anything else that they have to say.
33  Bitcoin / Bitcoin Discussion / "Bitcoin Classic" is a classic attempt at a hostile takeover on: January 18, 2016, 05:07:53 PM
Again we have another "we must increase the block size ASAP" fork crap - under the most stupid name "Bitcoin Classic".

It's a "classic" alright - a "classic attempt to FUD people into letting a small bunch of wannabe Bitcoin overlords take over the project".

The blocks are not even nearly full most of the time (apart from attacks which are just spam being used to fill up the mempool for FUD reasons).

The reason that people don't use Bitcoin for normal txs is "why the hell would they?".

Even if a vendor were to offer a cheaper price for paying in BTC you still have to change your fiat into BTC to purchase from them (and then most likely BitPay or another provider is going to take at least 1% commission).

If you don't purchase your BTC via an exchange (and no average person is going to do that to just buy something) then most likely you are going to pay at least 5% commission - so if you are ending up with 6% commission - did you save anything from using a credit card?

Also you can't get a refund if you pay with BTC - so the masses are not screaming to pay with BTC at all (far from it - if it cannot be reversed then I suspect 99% of people would not want to use it as certainly every person I have spoken to does not like the idea).

Can we stop with the FUD and let the project just continue to improve the tech?
34  Bitcoin / Development & Technical Discussion / Is the following idea possible in Bitcoin's Script? on: January 12, 2016, 01:33:46 PM
What I am wanting to create is a Bitcoin script that will do the following:

- check <data1> against <sig1>
- check <data2> against <sig2>

then only redeem if both sig checks work but *additionally* I need it to ensure that <data1> is identical to <data2> and that <sig1> is different to <sig2>.

Is this even possible?
35  Bitcoin / Bitcoin Discussion / Day trading BTC for those keen (never risk more than you can afford to lose) on: January 07, 2016, 01:29:28 PM
If you are thinking of "day trading" BTC then this is a simple guideline that might be of some use (and as the title points out don't risk losing money you can't afford to lose by doing "day trading" as it is inherently a risky activity).

Firstly - do a thorough check about the exchange you intend to use for your day trading (make sure they are established and that they can prove they have BTC reserves in cold storage and after that consider things like their trading and withdrawal fees, etc.).

Next - only inject as much actual fiat as you are prepared to lose (i.e. think of it as gambling and that you are taking a bet).

Next - assuming that you are starting with fiat you need to purchase some BTC with that fiat. In order to give yourself the ability to buy at a potentially lower price later you might want to simply purchase BTC with half of the fiat that you injected (so now you have half fiat and half BTC held in your exchange account).

Next - create bids and asks and record them yourself (don't just rely upon the exchanges records and be sure to check they are reporting everything accurately).

Next - if you manage a buy then create a sell for a price greater than you just bought for (allowing for any fees of course) and if you manage a sell then create a buy for a price less than you sold for.

Hint - it is always worth having a very low buy and very high sell in place just in case of dramatic price changes.

Next - do not deviate from the method - if you end up running out of fiat or BTC then you just "have to wait" for the price to enable you to trade again.

The last point is perhaps the most important - if you can't stop yourself from breaking such a simple set of rules then you are most likely going to end up losing.

Can you profit out of such a simple day-trading system?

Provided that BTC remains as volatile as it has for the last few years then it is very likely that you can.
36  Bitcoin / Project Development / AT and CLTV - Truly disruptive technology! on: January 05, 2016, 05:54:40 PM
After having played with the new CLTV Bitcoin (and soon to be Litecoin) op code (https://bitcointalk.org/index.php?topic=598860.msg13435766#msg13435766) CIYAM is now busy working on a decentralised crypto to crypto exchange.

We had already somewhat achieved that goal with the ACCT AT between Qora and Burst but unfortunately the PR didn't go well (apparently the funds that were meant to be used for PR were stolen) and of course it didn't involve Bitcoin (so wasn't noticed by most Bitcoin followers either).

But now I think we have something much more exciting about to happen. It will allow people to trade QORA/BURST with BTC/LTC without the need for any centralised exchange.

Unlike others trying to do similar things we are not going to be setting up a centralised website for order matching (nor taking a commission) - both Qora and Burst will be able to work as exchanges themselves (due to their AT support) and we will consider creating either a CIYAM application (which will be decentralised and free of charge) or an addition for Bitcoin/Litecoin (also free of charge) to work in a similar fashion.

Basically what we are talking about is "true disruption" (so even the new businesses that are making money out of crypto to crypto trades will be put out of business with this model).

(a note to mods - although Qora and Burst are alts this topic is about using OP_CHECKLOCKTIMEVERIFY to trade between them and Bitcoin so this is relevant to Bitcoin - I hope this isn't confusing the boundaries too much to work out whether this topic is in the right place or not)
37  Bitcoin / Development & Technical Discussion / Why can't I use a negative value for OP_CHECKLOCKTIMEVERIFY on: January 03, 2016, 10:55:20 AM
I've been testing a P2SH redeem script that looks like this:

Code:
OP_DUP
OP_SHA256
<secret hash>
OP_EQUAL
OP_IF
OP_DROP
OP_DUP
OP_HASH160
<public key hash 1>
OP_EQUALVERIFY
OP_CHECKSIG
OP_ELSE
<CLTV value>
OP_NOP2
OP_DROP
OP_DUP
OP_HASH160
<public key hash 2>
OP_EQUALVERIFY
OP_CHECKSIG
OP_ENDIF

I got it to work using -regtest (after a lot of mucking around as it appears that "coinbase" txs can't send to P2SH addresses without screwing up the scriptPubKey script) by using a <CLTV value> of 0x7f (block 127) and the CLTV redeem is working perfectly (in that it won't redeem until you have generated 127 blocks).

But if I change the <CLTV value> to 0xff (for block 255) suddenly the script interpreter is complaining about a "Negative locktime".

So how exactly am I supposed to tell it block 255?

(and according to the documentation locktime is an unsigned value so why is the OP_CHECKLOCKTIMEVERIFY reading a signed value?)
38  Bitcoin / Development & Technical Discussion / Having troubles with DER signatures on: January 02, 2016, 10:51:17 AM
This is the code I've written for creating Bitcoin signatures: https://github.com/ciyam/ciyam/blob/master/src/crypto_keys.cpp#L513 (the code was originally from Bitcoin itself and is using OpenSSL).

It had been working fine (and I also added code to ensure low S values) but now whilst I am trying to test a CLTV tx I am always getting the following error when attempting to send a transaction:

Code:
error: {"code":-26,"message":"16: mandatory-script-verify-flag-failed (Non-canonical DER signature)"}

This is a sample DER encoded signature:

Code:
3045022100da3114f49f3135fa0e3723a2c05ec304f4d16ce3e3f11920e7caa296dd53a9e202206870c44c3681bb9339c1233895a86c6b2861e3d6e6fa562601accae47fc445b201

I do see in the above that there is 00 after the 21 length and am wondering if the zero padding is the problem (the comments I read in the latest Bitcoin code seem to indicate that leading zeroes should not be there unless the value is negative - hmm... but isn't that number negative?).

If so what should I change in my code to make sure that the DER signature is being canonically constructed (i.e. is it even possible to be done correctly using OpenSSL or do I need to write code to get rid of the leading zeros myself)?
39  Bitcoin / Bitcoin Discussion / Can we just stop with the block size panic crap? on: January 01, 2016, 07:20:26 PM
It is becoming apparent that there are paid shills participating in every topic to do with the block size debate.

Apparently Mike Hearn simply cannot let a "dead horse" die. Sad

I do not work for any company (other than my own) and am not sponsored to make any statement but I will make this statement.

Bitcoin is not suitable for "coffees" and why should it be (as practically no-one in the world is paid in Bitcoin)?

What Bitcoin is very suitable for is "remittance' (sending money overseas) yet so far it has virtually no market share in that sphere (which it should dominate).

Can we start focusing on remittance rather than coffees?
40  Bitcoin / Development & Technical Discussion / Is this BIP65 sample script standard? on: December 23, 2015, 02:44:38 AM
From the BIP section Trustless Payments for Publishing Data the following script appears:

Code:
    IF
        HASH160 <Hash160(encryption key)> EQUALVERIFY
        <publisher pubkey> CHECKSIG
    ELSE
        <expiry time> CHECKLOCKTIMEVERIFY DROP
        <buyer pubkey> CHECKSIG
    ENDIF

Although the release notes for Bitcoin core mention stuff about BIP65 it is not clear to me whether that means that the above is standard.

Assuming it is standard then if HASH160 was to be changed to say SHA256 would it still be standard?
Pages: « 1 [2] 3 4 5 6 7 8 9 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!