Bitcoin Forum
June 20, 2024, 06:09:56 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 [105] 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 ... 334 »
2081  Alternate cryptocurrencies / Altcoin Discussion / Re: Creating metacoin for a decentralized exchange? on: March 11, 2015, 04:34:05 PM
How does Automated Transaction differ from Open Transactions? I'll have to read more about it.

You can find some information here: http://ciyam.org/at (am sorry it is mostly very technical).

To explain succinctly though AT is a "smart contract" implementation that can be added to *any* blockchain (so it does not have its own blockchain).

It already works and we have created Lottery and Crowdfund ATs that have been running "live" for weeks.
2082  Alternate cryptocurrencies / Altcoin Discussion / Re: Creating metacoin for a decentralized exchange? on: March 11, 2015, 04:24:13 PM
Incidentally, this is false.

For the type of options that are normally sold for stocks what I stated is 100% correct (perhaps you are referring to some type of option that only applies to the US?).

You sell options as an "insurance" against loss on the underlying stock. So the seller of the option is hedging and the buyer is speculating.

This is generally most useful for stocks that don't pay much in the way of dividends (as you are less likely to want to sell options on blue chip shares that pay good dividends).
2083  Alternate cryptocurrencies / Altcoin Discussion / Re: Creating metacoin for a decentralized exchange? on: March 11, 2015, 04:22:54 PM
http://mercuryex.com/ looks interesting too, I haven't tried it out. They are using the atomic cross chain swap to allow trading between the two. I think there is a centralized orderbook, tho so it isn't completely decentralized.

The Automated Transactions project (aka AT) has already created an atomic cross-chain transfer smart contract that could operate on any platform that implements AT (it is on Burst and soon to be on Qora).

If you guys are seriously interested in a completely decentralised solution then perhaps you should think about integrating AT with BitShares (I know at least two BitShares devs are interested in it).
2084  Alternate cryptocurrencies / Altcoin Discussion / Re: Creating metacoin for a decentralized exchange? on: March 11, 2015, 03:08:40 PM
There are use cases that bitassets can fulfill that nothing else in the space is capable of atm. I wouldn't be so quick to dismiss it all as "snake oil" because you haven't taken the proper time to research it for yourself and are making assumptions instead.

You are probably unaware that Dan Larimer used to chat with me on Skype before Bitshares even existed and that I knew about this whole concept before nearly anyone on this forum.

I am not making assumptions at all - calling something xBTC that has no BTC to back it up is not what I think of as being a valid product (but again that is just IMO).

And for the record I am not claiming that it *is* snake oil but the way it is being sold (by you in particular) looks just like that (so please stop telling me to "educate myself").
2085  Alternate cryptocurrencies / Altcoin Discussion / Re: Creating metacoin for a decentralized exchange? on: March 11, 2015, 09:45:53 AM
I added the bold part because without 100% reserves you simply have a fractional debt scheme.

Yes - very good point.

This is why a Ripple BTC is not worth a real BTC (as you can't be sure that all the issued "tokens" can be redeemed).

Constantly posting links to large blog entries or papers (rather than giving a simple explanation) is another problem I have with these "products". Typically this is the "snake oil" sales approach in the financial world.

We all saw (and many have felt) the result of Credit Default Swaps (which were also very complicated "derivatives").
2086  Alternate cryptocurrencies / Altcoin Discussion / Re: Creating metacoin for a decentralized exchange? on: March 11, 2015, 09:37:13 AM
Imo, no convertibility, no parity.

This is exactly my issue with these "products" - if it is called xBTC then I expect to be able to exchange it for actual BTC.

So if you are able to actually exchange 1 bitCNY for 1 CNY somewhere then that is fine (and the name makes perfect sense) but if there is nowhere you can do that then the name is about as meaningful as bitXYZ.

Whilst I don't think that there is any intention to deceive it "seems" deceptive to name something xBTC if you can't exchange it with actual BTC (i.e. why are you using that name?).

I am quite familiar with options trading (used to do some of that years ago) and although options are often never exercised they always *can* be if the conditions are met (i.e. the underlying share ownership will be transferred).

Trading something that with a name that doesn't have an actual matching asset is just something I'd never do (but perhaps that's just me).
2087  Bitcoin / Bitcoin Technical Support / Re: SHA-256 in c++ with crypto++ on: March 11, 2015, 06:24:50 AM
Or maybe *you* should stop being condescending and at least provide good code.

I was not meaning to be condescending (but admittedly got a bit frustrated - I have now removed the offensive comments from my post).

Here is the fixed code (that I have tested with g++) that will work assuming that your string is the binary hash:

Code:
#include <iomanip>
#include <sstream>
#include <iostream>

using namespace std;

string print_hash_as_hex( const string& hash )
{
   ostringstream outs;

   if( hash.length( ) == 32 )
   {
      for( size_t i = 0; i < 32; i++ )
         outs << hex << setw( 2 ) << setfill( '0' ) << ( int )( unsigned char )hash[ i ];
   }

   return outs.str( );
}

int main( )
{
   string hash( "\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a\x9a" );

   cout << print_hash_as_hex( hash );
}

Replace the first line in "main" with your SHA256 string object.
2088  Bitcoin / Bitcoin Technical Support / Re: SHA-256 in c++ with crypto++ on: March 10, 2015, 06:34:18 PM
The output you are getting "is the digest in binary form".

So just pass that to the function I gave you and you should see your hash in ASCII form.

2089  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][XCP] Counterparty - Pioneering Peer-to-Peer Finance - Official Thread on: March 10, 2015, 06:24:29 PM
But why doesn't your PoC here contain C code: https://ciyam.org/at/at_auction.html

Details, and please, ELI5 if you can't point to code which adequately highlights your LLVM automated transaction concept. LLVM contracts are sorely lacking in details and implementation.

Our use cases are currently written in AT assembly code.

LLVM is what we can deliver but not what we have now (can Ethereum deliver LLVM - answer is no).

How can AT be done with LLVM is simply because it is a virtual CPU (not a VM).

Ethereum has a VM which cannot work with LLVM at all (their strategic mistake I pointed out more than a year ago).


2090  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.2 Automated Transactions on: March 10, 2015, 04:51:28 PM
What's wrong with the double-click and drag functionality?  On Windows; instead of just double clicking; double click any part of the first word "BURST" and drag the mouse to the last word in the address.  This highlights the address from the first word (section) to the last word and nothing else.

Just try it with a tab/pad and you'll see the problem.

Telling everyone that they should change how they use their UI is not a good idea (and won't work).
2091  Bitcoin / Bitcoin Technical Support / Re: SHA-256 in c++ with crypto++ on: March 10, 2015, 04:48:33 PM
if I use your code

Code:
    cout << print_hash(myStringSHA) << endl;
    
    for (size_t i = 0; i < myStringSHA.size(); ++i) {
        printf("%02x", myStringSHA[i]);
    }
I get exactly the same as before:
Code:
ffffffba7816ffffffbfffffff8f01ffffffcfffffffea414140ffffffde5dffffffae2223ffffffb00361ffffffa3ffffff96177affffff9cffffffb410ffffffff61fffffff2
ffffffba7816ffffffbfffffff8f01ffffffcfffffffea414140ffffffde5dffffffae2223ffffffb00361ffffffa3ffffff96177affffff9cffffffb410ffffffff61fffffff2
and the size of myStringSHA is still 29 and not 32...

So your problem is the string not the output of the string.

If you feed my function the actual "binary digest" it'll work perfectly.
2092  Bitcoin / Bitcoin Technical Support / Re: SHA-256 in c++ with crypto++ on: March 10, 2015, 03:28:11 PM
Let me see if I can "put you out of your misery" by creating a simple "print" function for you:

Code:
string print_hash( const string& hash )
{
   ostringstream outs;

   if( hash.length( ) == 32 )
   {
      for( size_t i = 0; i < 32; i++ )
         outs << hex << setw( 2 ) << setfill( '0' ) << ( unsigned )hash[ i ];
   }

   return outs.str( );
}

You'll need to add the #include <sstream> and #include <iomanip> but that should solve your problem.

You might want to throw an exception if the length isn't 32 (it will just return a blank string in that case as is).
2093  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.2 Automated Transactions on: March 10, 2015, 01:25:27 PM
hmm.. underscores work for me.. but good to know!  Maybe it's a windows versus other operating systems thing?

Might even depend upon which browser - but using a lower case letter is *guaranteed* to work everywhere.

Ok, I'll probably switch it to either BURSToSYYSoQMGRoBCYNoBVQ2A  or BURSTxSYYSxQMGRxBCYNxBVQ2A, unless anyone else has a reason they prefer a specific alphanumeric character to act as a separator.

Using 'o' was the other lower case letter I was thinking of too. Smiley

2094  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.2 Automated Transactions on: March 10, 2015, 05:51:39 AM
I agree with CIYAM.. we should change that "-" to something that can be copied on double-click. Decided to play with the code and figured out how to switch it over to "_" which happens to be copyable.  Here try double clicking what will become my new wallet address:  BURST_SYYS_QMGR_BCYN_BVQ2A

Except underscores don't select the whole thing when double clicking either.

Yup - I would recommend something like this:

BURSTxSYYSxQMGRxBCYNxBVQ2A

(doesn't look beautiful but at least works everywhere for selection)
2095  Bitcoin / Project Development / Re: 20 BTC bounty for first AT *atomic cross-chain transfer* with Script clone on: March 10, 2015, 05:45:26 AM
Although off-topic (and that service is not running on any "mainnet" yet) it is using the same method that the AT atomic cross-chain transfer was based upon (that which was first described by forum member TierNolan).

Note that the "refund" txs are problematic on Bitcoin (and most alts also) as the nLockTime is non-standard unless already past (i.e. you can't broadcast the refund via any normal method). Presumably you'll need to use their website for this part as well as finding other "orders" (making it still fundamentally a centralised service).
2096  Bitcoin / Development & Technical Discussion / Re: An easy way to remember a bitcoin address on: March 09, 2015, 05:28:59 PM
There are many dimensions:

Thanks for the summary:

1. Do we want the ability to encode all outputs in the blockchain, or just some of it (say, only the first 4 outputs in all txs)? hhanh00's scheme is easier to implement as it only encodes the first 4 outputs in a tx. My scheme is more complex and the length of all components are variable.

I guess the "target audience" is what matters (for me 4 outputs would be fine as I would be using it for "cold storage" which would have generally only 1 output anyway).

2. hhanh00's address is shorter than mine in some case, while the opposite in some other case.

I think 5 "words" is fine (whichever approach).

3. How many bits of checksum is needed? I proposed 20bits so the error tolerance is about 1 in a million. Should we use more? Could we squeeze a few bits for other purpose? (Satoshi used 32 bits in standard bitcoin address.)

As many as possible without adding an extra word.

4. Do we need a version bit (like in standard bitcoin address)? It will occupy 1 bit (which could be otherwise used for other purpose. In order to keep the address short, every bit is very valuable) but it makes potential future upgrade easier. Otherwise, future upgrade will need to use 2048 completely different words, or people have to denote the version of the address externally (e.g. using a URL like header)

A version bit seems reasonable to me.

5. Do we want miner to have the ability to mine a vanity address? My scheme disallows it in response to gmaxwell's comments (see first page). The other scheme allows miners to mine vanity address.

I am not quite sure of the implications of this - but it would be better to probably not allow it.

6. Do we want the addresses look like random (i.e. outputs/txs close to each other will have statistically unrelated addresses) or not?

If the point is to help someone remember the address then random is better so they don't get confused IMO.
2097  Other / Politics & Society / Re: The end of copyright and patent is where we should be headed - OPEN SOURCED :) on: March 09, 2015, 05:07:21 PM
The concept of having a true understanding of what open source is..

Tired already - so unwatching - enjoy your topic (I think you'll find that I am not so popular so this topic will die pretty soon).
2098  Other / Politics & Society / Re: The end of copyright and patent is where we should be headed - OPEN SOURCED :) on: March 09, 2015, 05:03:18 PM
You have an agenda. I have an agenda. We all do. Once you realized that, the concept of locking a thread will feel so... 21st century technology...

Hmm... okay - how about I just "unwatch" from now on then (so you can't tell) ?

(thus no "agenda" you can talk about)

Basically you guys seem to think you have the right to "bully people" but sorry - "you lose" (you have no such right).

So feel free to "bitch about me behind my back" but it isn't going to bother me at all.
2099  Other / Politics & Society / Re: The end of copyright and patent is where we should be headed - OPEN SOURCED :) on: March 09, 2015, 04:59:41 PM
I might be more polite when you stop being a hypocrite. And you replied anyway.

I replied but did not answer any question (as I said I would not).

But you're still a brainwashed Disenfranchised peasant.

Again with the insults - do I insult you?

If you have anything to offer to discussion then can't you do it without resorting to being a child?

(this is generally why I don't bother engaging with a lot of people on this forum because they can't help but to carry on like children)

You might think that you have "won some sort of victory" when I lock a topic or unwatch it - but actually I never think anything further about it after that (so you *victory* is only in your own mind).
2100  Other / Politics & Society / Re: The end of copyright and patent is where we should be headed - OPEN SOURCED :) on: March 09, 2015, 04:48:51 PM
Open means open.

So I think the important changes we are seeing are things like Open Source and Creative Commons.

These are ideas that challenge the traditional models of paying "fees for use" and reduce friction to creating new things (and that is IMO the key thing).

I hope we could focus more on that than on "my supposed agenda" (or the fact that I live in China).
Pages: « 1 ... 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 [105] 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 ... 334 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!