Oh, you mean the lock time. Yeah, sure that should be easy to add. FAIK, it's just setting the LockTime to a value other than zero. You can do it yourself, if you like playing with source code. Look inside wallet/signtx.go, function make_signed_tx() and change: ... to whatever you need. (like a value read from a command line). I really encourage people to play with the code - if you are a programmer, especially if you did a lot of C, Go is a really cool language to code in. I've been coding C all my life, but writing in Go is just so much more pleasant. And it compiles so quickly that at the beginning you cannot even believe it  Of course, there is a testnet switch -t and make sure to use it while you are having fun, to not be sorry at the end. EDIT: As for the lock time, I read that in order for it to work, you would also need to set this: tin.Sequence = 0xffffffff ... to a different value. |
|
|
|
Well, you can put any kind of scripts into the wallet's code, but without a specific application (a user case), I don't see how I could add anything more. So far gocoin supports the following output scripts: * P2KH address (a regular bitcoin address) * P2SH address (that's for multisig) * NULL output describing the next one's encrypted constant (for stealth payments) * NULL output with an arbitrary data (e.g. to attach text messages to transactions) Adding other kind of output scripts is not really a challenge, but I need a specific application for it, before I can put it in. As from the node's side. Gocoin node (unlike bitcoin-qt) does not split transactions into "standard" and "non-standard". As long as the fee per byte is sufficient (plus some other rules are met), it will get routed, despite of the content of a script. EDIT: Personally I think that dividing transaction into "standard" and "non-standard" has been a really stupid idea and I just cannot believe that instead of abandoning it they are just adjusting the rules of the standardness - that's crazy! It would be nice though to measure txs by how much CPU power they require to get verified - and then check the fee not only against the size, but also against the CPU required. But that seems like a too much advanced solution for the mainstream - it will take them at least 5 years to find out that this is an idea worth exploring  |
|
|
|
Do you have any plans to allow scripts in transactions?
I don't think I understand this question, so please precise. But I have another answer to your previous question - times time a positive one Is it possible to spend an unconfirmed transaction?
Not in the current implementation - not without modifying the source code.. Unless it would be an unspent transaction that you made yourself, using gocoin. Actually, it is possible. It just came to my mind. The fetchbal tool - it can fetch unconfirmed balance. And then, having your unconfirmed transaction in the balance folder, you can just use it on the wallet (it won't see a difference). |
|
|
|
|
I see what you mean. You would need the whole client node to have a kind of GUI selection, via its web interface. That's how I do it.
Creating a GUI wrapper (like in Java, C# or even PHP), that would call fetchbal and then allow to edit the unspent.txt file in a more user-friendly way, perhaps even run the wallet at the end - that should not be much of a challenge. But nobody has created it, fwik
|
|
|
|
When building client or wallet:
membind.go:63: cannot use _Ctype_size_t(v.datlen) (type C.size_t) as type C.ulong in function argument
Thanks for reporting. It must be specific for your libc, I cannot reproduce it here. But I've just committed a possible fix - can you try now, please? Otherwise you can always build it by overwriting membind.go (in qdb) with the one from no_gcc folder. You just won't be able to enjoy the recent mem usage optimizations, but should build flawlessly then. |
|
|
|
You can do it using gocoin, in node-less mode. You just need to build fetchbal tool and the walletFetch the balance of your address(es) from a block explorer - e.g.: fetchbal 1HZAQy4sq5JHtkbeEpHNB5NooqpskpNYzB 1GysXMDoDDkgrJcAK92SdEohbHvabu1PTX 1MvkVTM8eJ7FKMZnLLHA9FYUhwdPHE2rNt Now you can edit the file balance/unspent.txt and leave there only the inputs you want to spend. Then use wallet tool with the balance folder to make & sign a transaction. Obviously first you will need to arm the wallet with proper private keys (better do it on an offline machine). And then just broadcast the signed transaction file (e.g. using this page: https://blockchain.info/pushtx) Let me know if you had any questions. |
|
|
|
I have to pay multiple people (200+) at one go from a wallet. I have the addresses and amounts in an excel file. But I dont see any option to upload that file to blockchain.info wallet so that I can pay at one go. I have to copy paste each address and amount individually. Can anyone please suggest any wallet that supports this feature ?
gocoin's wallet can do it. you just run it: wallet -batch payments.txt ... while in payments.txt you have lines like this: addr1=amount1
addr2=amount2
...
addrN=amountN
|
|
|
|
|
Connecting to your service seems like a lottery these days.
Is it going to be fixed one day?
It's really annoying, when you need to keep pressing on reload.
|
|
|
|
|
Wtf?
Make sure you have relatively fresh version of go. I'd advise 1.2 at least, though I think you rather have something pre 1.0
I was doing many changes today - could have broken something. If so, I'll fix it tomorrow.
But i'm pretty sure the last tag should build well, with a proper compiler.
|
|
|
|
I will be really interesting to exchange some test coins with another wallets' stealth addresses. If someone will do this - leave a feedback!
be my guest waPV5rHToBq3NoR7y5J9UdE7aUbuqJybNpE88Dve7WgWhEfvMrcuaSvF6tSQ3Fbe8dErL6ks8byJPcp3QCK2HHviGCSjg42VgMAPJb |
|
|
|
code.google.com/p/snappy-go/snappy - it is some kind of weird URL that go uses to call mercurial. I dont know how they do it, but it works. Install Mercurial in your OS and then just execute: go get code.google.com/p/snappy-go/snappy It should call "hg" with a proper arguments, download the package and build it. It works here. Also, before "go get", you may want to set env variable GOPATH to point to some user folder (so you don't need a root access to store the files). |
|
|
|
Recently I have reorganized the entire repo quite seriously. The latest tag is 0.9.13. There should be some performance improvements, because I moved all the EC math to the internal lib, the one based on ported sipa's code (before only EC_Verify was handled by it). I also added a support for the stealth addresses - feel free to check it out as well, it's a really cool feature: http://www.assets-otc.com/gocoin/manual/stealth-addressesAs for the rest; kill me, but all I remember is that there were plenty of useful changes and the time was flying when I was making them...  Anyway, I think this code will soon become Gocoin 1.0.0 - finally. But first I need to test it a bit more, because the recent changes were really huge. Huge enough to frighten even me. Still so far it looks well, but if anyone could help me by giving feedback on whether the latest code still works good enough for him, I will really appreciate it. Just please don't rush it - let it work for at least a day, before saying that it's fine. Also please be careful - there were changes everywhere, and that includes the wallet part. Triple check your signed transaction, before broadcasting it, making sure that it actually does what you needed it to do. |
|
|
|
In the install-sx.sh script, in the function called install_libbitcoin, change ./configure with --enable-testnet I think I did that. Also added "--enable-testnet" for libwallet I'm looking at config.log in libbitcoin-git and libwallet-git - they both show "ENABLE_TESTNET 1" But the "sx stealth-show-addr" still says "Invalid stealth address" for any testnet stealth. At the other hand it has no problems to decode a non-testnet stealth addresses. EDIT: I think I know where is the problem. In libwallet-git/src/stealth.cpp, there should be: #ifdef ENABLE_TESTNET
constexpr uint8_t stealth_version_byte = 0x2b;
#else
constexpr uint8_t stealth_version_byte = 0x2a;
#endif
|
|
|
|
btw, can I have the sx tools for testnet? the ones I finally managed to build cannot even do $ sx stealth-show-addr waPV5rHToBq3NoR7y5J9UdE7aUbuqJybNpE88Dve7WgWhEfvMrcuaSvF6tSQ3Fbe8dErL6ks8byJPcp3QCK2HHviGCSjg42VgMAPJb
sx: Invalid stealth address. |
|
|
|
|
Yep, I saw it already - thx.
But it seems to be already working well in my s/w (sending and receiving).
I can exchanging coins via stealth addresses with DW - don't need sx for it anymore.
Unfortunately sx nor DW support stealth addresses with non-zero length prefixes ATM, so I cannot test that part of mine.
But zero length prefixes seem to work just fine.
|
|
|
|
|
If I may, I'd like to say that despite of my initial complaints the idea of the stealth addresses, as it has been implemented in DW, is actually pretty cool and works really nice.
Checking an output on whether it belongs to a specific stealth address is not so much time consuming, especially considering the fact that a node usually needs to do a several ECDSA_Verify operations on each transaction anyway.
And the idea with the prefix - very good one.
You can just start with prefix length 0, to protect your anonymity when there are just a few stealth addresses out there..
But when the volume of stealth outputs rises, you can increase the length of your prefix, saving the node's computing power though still staying anonymous.
Whoever designed it, great job!
And thanks - finally somebody not only invented/described, but also delivered an actually useful feature to the bitcoin ecosystem.
|
|
|
|
Is it possible to spend an unconfirmed transaction?
Not in the current implementation - not without modifying the source code.. Unless it would be an unspent transaction that you made yourself, using gocoin. |
|
|
|
Yep, and clean up the house. But since it's after midnight here already, I decided to just have another beer now and postpone any such work till at least tomorrow. I will like to exchange some test coins with another wallets' stealth addresses, so I'll try to catch you later. Cheers |
|
|
|
cmon man upgrade your ubuntu. that is super old! ubuntu 14 is a new LTS
It's because I usually don't upgrade something that works, especially an entire OS. The only reason I upgraded WinXP to Win7 was that I needed a support for two graphic cards at the same time. But I did listen to your advise and have upgraded it to 14.04. The result is that I lost all my user accounts and all the apps, and now... I cannot build the tools again. Not that I would not had expected it CXXLD obworker
/usr/bin/ld: warning: libicuuc.so.48, needed by /usr/local/lib/libboost_regex.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libicui18n.so.48, needed by /usr/local/lib/libboost_regex.so, not found (try using -rpath or -rpath-link)
/usr/local/lib/libboost_regex.so: undefined reference to `u_charType_48'
/usr/local/lib/libboost_regex.so: undefined reference to `icu_48::Locale::~Locale()'
/usr/local/lib/libboost_regex.so: undefined reference to `icu_48::Collator::createInstance(icu_48::Locale const&, UErrorCode&)'
/usr/local/lib/libboost_regex.so: undefined reference to `u_digit_48'
/usr/local/lib/libboost_regex.so: undefined reference to `icu_48::Locale::Locale(icu_48::Locale const&)'
/usr/local/lib/libboost_regex.so: undefined reference to `u_tolower_48'
/usr/local/lib/libboost_regex.so: undefined reference to `icu_48::Locale::Locale()'
/usr/local/lib/libboost_regex.so: undefined reference to `u_isblank_48'
/usr/local/lib/libboost_regex.so: undefined reference to `u_charFromName_48'
/usr/local/lib/libboost_regex.so: undefined reference to `u_isspace_48'
collect2: error: ld returned 1 exit status Anyway, its just my Linux test machine - I don't care about it. But I did have a working sx, before upgrading - no more, though. From the good news. I think the stealth addresses are already working in Gocoin. It's a bit of a hassle to spend money from such. You need to arm the online part with the scankey's secret and then use TextUI to fetch its balance data. But using the wallet for spending to a stealth address - this is as easy as it can be; just use a stealth address in place of a regular one and voila. Although... I cannot quite test it because currently whatever I send to any of my DW testnet addresses (stealth, or not) ends up in a limbo. So I can only test it against my own client - this one can receive coins via a stealth address and spend it further, using own wallet. Also I learned that a prefix of 32 bits would kill any wallet, unless you'd hook it to some kind of a mining board. So my wallet does not support prefixes longer than 24 bits. And no multisig yet. Thanks anyone for your help. That was fun. Now time to clean up the house a bit |
|
|
|
|
Show Posts
