When trying to import using "import transaction (raw)" I get "Push operation exceeds data size". This sounds like your transaction is too large for mSIGMA to handle for some reason. Are you trying to consolidate a lot of inputs at once? Perhaps split your transaction in to two and try again with fewer inputs? Unfortunatelly not. I tried first with the 3 inputs I have and then just a solo input. Both didn't work. I noticed there might be trouble stemming from using a bech32 address as the receiver address and tried with a 1xxx legacy one instead, same results - mSIGNA shows an error upon import. |
|
|
|
Yes, importing is available via the following options: from clipboard or from file, optionally in RAW.
Btw sorry, you asked before if tx export was possible, for some reason I missed that option before. Ahh well then, that changes everything! This should (hopefully) be the easiest option going forward then. What I would do is the following: - Get a list of all the addresses which still have funds on them
- Create a new Electrum wallet, select "Import bitcoin addresses or private keys", and insert all your addresses
- In that Electrum wallet, create a transaction sending all those coins to a regular address you control
- At the bottom left of the transaction window, select "Export" (you might have to select "Finalize" first), and export to clipboard
- Import it from the clipboard in to mSIGMA and (hopefully!) sign it
- Export it from mSIGMA, import it back in to Electrum, and broadcast it
I feel like that was VERY close. Did all the steps on the electrum side - works well. When trying to import the transaction with mSIGNA I get the following error and immediately aborting "invalid signature" - if I just select "import transactions". When trying to import using "import transaction (raw)" I get "Push operation exceeds data size". |
|
|
|
This is exciting, is there any info / leaked footage of the design of this one available? I found this from OP: https://i.imgur.com/osUkkQS.jpg - is that the final design? I guess material, size etc are still a secret? Looking forward to it. Funny enough, when I just re-checked the thread I was confused because it's created before the yogging - then realized there was our good SBF-boy wreaking havoc before him.  |
|
|
|
Does the coin control feature allow you to pick individual UTXOs, or just addresses? So if you had received bitcoin three times to the same address, can you pick exactly which output to spend?
Second question - if you can export transactions, can you import them too?
UTXO selection is not available - just individual addresses from within the wallet itself. Yes, importing is available via the following options: from clipboard or from file, optionally in RAW. Btw sorry, you asked before if tx export was possible, for some reason I missed that option before. About the own node solution: Right now don't even have the disc space for a BTC full node (but could use some older HDD lying around) - my worry is, even after finally having a synced full node running and connected to mSIGNA, the sync process will be stuck somewhere - that's what people seem to report on their github a lot.
Would you like to borrow my full node for a little while? That sounds interesting, thanks for the offer. Not sure if it's worth it for the few sats remaining, how would that actually work - Just try to connect to it via the right address? |
|
|
|
|
Ah alles klar!
Gibst Du vorher bescheid, wenn dieser run los geht oder wie genau funktioniert das?
Ich wär gerne mit 0.005 dabei, möchte aber die action nicht verpassen und gerne vorher wissen, wenn es losgeht.
Für run 45 reserviere ich dann auch gleich wenn das passt.
Transaktion kommt morgen.
|
|
|
|
Mega cool sword - gah dah! Thanks for the pics, MJ and pinky. Gotta say 15% or even 10% is very steep, reminds me of ebay charges, which I despise.
That said, you can find some very cool items on the scarcecity and ease of use is definitely nice - glad to see a well working lightning implementation there.
So far only basic experience as a potential buyer, will try and see how the other side feels as a seller.
Any pics of that Hal Finney sword, pinky1234?
As a seller I thought the 15% fee was fair for the exposure and handling of the auction. They essentially act as escrow as well so that should also be considered. Okay, sure escrow and especially exposure may make up for it. Maybe just used to MJs excellent service without high fees and obviously comparing that! Wish the forum had a little more activity... Like I said, I should try it myself and see from there. |
|
|
|
e_o_l_e_o has indeed helped a lot so far. Getting close to sloving it, but seems the derivation path of mSIGNA isn't easy to find out. If anyone has any insight on the correct derivation path for mSIGNA or is tech-savy enough to find it in the code on github, please let us know!https://github.com/ciphrex/mSIGNAHowever, big update! I was able to retrieve around half of the funds. - mSIGNA allows to export transactions as raw data. - mSIGNA allows coin control. - So I just selected the public address I knew still hand coins on it, found an oldschool 1xxxx address in an older electrum wallet to send the funds to and created the signed transaction with mSIGNA and then exported it. - imported the transaction in electrum wallet via tools -> import transaction -> from text -> broadcast. - BAMMM it worked! However, because my mSIGNA wallet is not fully synced I could only retrieve the funds up to the amount the current balance of this unsynced wallet showed. Which is only around half of the total funds. Still a nice recovery. There are two more addresses with around 0.0015 BTC each that I cannot access this way because their balance in the wallet is too high. - If I want to create a tx inside the wallet it works and I can export it (even using the amount I know is on it because I can check via a current explorer). HOWEVER after importing to electrum (which also works) the transaction will be denied by the node, because the transactions includes an amount that exceeds the actual accessible funds. Why? Because the transactions also includes a change address that will receive the "remaining" funds - because mSIGNA is synced at a state that has too many funds than actually available on that address. Still, a nice tiny success. If anyone has more ideas on this, feel free to jump into the discussion. |
|
|
|
Nicehash ist halt eine Börse auf der Hashpower gehandelt werden. Nachfrage regelt den Preis.
Je mehr nachgefragt wird, desto höher steigt der Preis. Genaueres kann ich da nicht sagen, einfach mal selbst auf Nicehash schauen. Preisspanne geht von derzeit 2,5 bis 3,2 BTC / EH / Tag
Verfügbar sind gerade ca. 3 EHs auf Nicehash. Wenn du also 0,1 EHs buchen willst, wird das den Preis nicht sehr hoch treiben.
Willst 2 EHs anmieten, wird der Preis sehr hoch gehen, da du ja alle anderen überbieten musst und die ja auch mitziehen um ihre Rentals am laufen zu halten.
Verstehe. Danke für die Ausführung. Sollte also bei uns nicht sonderlich relevant sein, da wir ja nur einen Bruchteil eines EH/s mieten werden mit um die 20 PH/s, richtig? Zum anderen Thema: Nur weil du 100% Shares der Diff erzeugt hast, heist das noch lange nicht das du einen Block findest. Es kann genau so gut sein das du 200% Shares der Diff erzeugst und keinen Block findest, aber dafür ca. 10-15 BTC verbrannt hast. Gewinnerwartung ist eins, einen Block zu finden das andere. Wenn das so sicher wäre, hätte ich mein Haus verkauft und alles auf Nicehash geschoben, oder einen Kredit genommen und Nicehash gefüttert. Du kannst einen Block bei unter 100% Luck finden oder bei über 100% Luck, ist alles drin und ist eben Glück und nicht vorhersehbar. Unsere drei letzten Blöcke haben wir sehr früh gefunden, hätte auch 90% / 120% oder 250% sein können  Blockparty 08 2021 found with a luck of --> 14% Blockparty 14 2021 found with a luck of --> 13% Blockparty 30 2023 found with a luck of --> 56% Ist klar.  Expected value halt, darum geht's mir. Alles andere ist Varianz, darauf hat man natürlich keinen Einfluss. Was genau bedeuted die Luck Zahl? Bezieht sich das auf die Chance einen Block zu finden? |
|
|
|
|
Gotta say 15% or even 10% is very steep, reminds me of ebay charges, which I despise.
That said, you can find some very cool items on the scarcecity and ease of use is definitely nice - glad to see a well working lightning implementation there.
So far only basic experience as a potential buyer, will try and see how the other side feels as a seller.
Any pics of that Hal Finney sword, pinky1234?
|
|
|
|
Hi Willi, kannst Du etwas zu meinem letzten Post sagen? Hab inzwischen gehört, dass die Nicehash Preise für 0.1 EH/s nicht unbedingt skalierbar sind, dh. sobald wir mehr anmieten wird's teurer pro 0.1 EH/s - wie ist da Deine Erfahrung? Ich denke ich such jetzt mal 2x 0.005 zusammen und mach da einfach mal mit. |
|
|
|
That sounds interesting. Would it tell anything about the derivation path or other wallet properties? How does the script used to send help in my case? It wouldn't tell you anything about the derivation path, but it would tell you if you are indeed looking for a standard nested segwit address. If you are, then we can tackle finding out the derivation path. If the script is something different, then checking derivation paths as you are doing with Electrum or similar will get you nowhere. Can you guide me through the steps without me exposing my pub keys? Find one of your addresses from the mSIGMA wallet which has sent coins out from it, and grab the TXID. Head over to https://mempool.space/ and look up that transaction. Click on where it says "Details" on the right hand side. Underneath your address the first field should be titled "ScriptSig (ASM)". Hopefully next to that it says "OP_PUSHBYTES_22", followed by "0014" and then 40 random characters. If it does, then you've got a nested segwit address. If not, then you've got something different. Okay, wow how do you know this stuff?  Ermm... yes so, there are several interesting things here: ScriptSig says "OP_0 OP_PUSHBYTES_72" then followed by defintely more than 40 chars (looks like around 100) and then it says OP_PUSHBYTES_37 followed by maybe 50 characters Also it says multisig 1/1 - which isn't normal, right? Does a 1/1 multisig even make sense? Seems like you were right and every mSIGNA wallet is indeed multisig - even when it actually isn't really.  |
|
|
|
Kinda cute, that shiba always looks cuddle-worthy. However why is there a genereic ETH logo on the other side? Kinda random and I don't see the connection to Dogecoin at all. Not familiar with mini-brands - it's similar to a kinder suprise egg? |
|
|
|
Although we might take this advise positively, I guess it is still to vague for the average joe/jane.
[...]
I agree with that. Instead of advicing average Jeph and Jane to invest in Bitcoin, send them some of the lesser known but amazing facts about Bitcoin. This can start by providing a few links to Andreas Antonopoulos talks, or just sending them some other informational but intruiging resource. Or, even better, let them download a wallet, send them a few funds while you are on the other side of the globe and let them experience the ease of use and direct, decentralized manner of Bitcoin themselves. A healthy Bitcoin journey shouldn't start from a greed-based but uneducated point. Sure, if they are lucky and ride that first big wave possibly coming in 2024 well, they will be excited. Until the correction comes and then the journey usually ends there because "Bitcoin is obviously dead now". Still, glad you mention dollar-cost-average and your second point isn't too bad either. : ) |
|
|
|
I may not have made that clear in OP: But I can still access my wallet in mSIGNA. Yeah, I get that. My point of importing the seed phrase again was to ensure your wallet is indeed just a single signature wallet derived from that seed phrase and not some more complex multi-sig set up which we would never be able to recover using just one seed phrase. I see. Yes, good point! I am 99.9% certain it's not a multi-sig. First of I would have remembered and written down some info about it on my seed-paper. But most importantly, I tried re-importing via the wordlist into mSIGNA and it worked flawlessly - they display a hash for each "keychain" (actually the HD wallet) and it is the same for the imported wallet via SEED compared to my original wallet. My guess it's only about finding the right derivation path. Having read through the .pdf again, I'm not so sure: NOTE: mSIGNA™ always uses pay-‐to-‐script-‐hash addresses, which begin with the character 3 in Bitcoin, even for 1 of 1 accounts. There is no mention that they use nested segwit addresses, which is the type of address every other wallet will try to recover when given a seed phrase and a P2SH address type. The sentence above I've just quoted suggests they may use some strange custom 1-of-1 script, in which case you will never find it by just playing with the derivation path. You will need to find the exact script being used. Does mSIGMA have the option to import transactions from elsewhere? That would be the easiest way forward - create an unsigned transaction elsewhere, import it to mSIGMA for signing, and then export it for broadcast. If not, then I think the easiest option is going to be to spin up your own node and get mSIGMA to connect to it. Otherwise you will need to comb through the entire source code to figure out exactly the script type and derivation path which is being used. No such option available like importing or exporting tx with mSIGNA. I did check their source code a little bit. Not sure where to look for it and even if I find something how to proceed from there. - Just getting the right derivation path info would probably solve it, right? About the own node solution: Right now don't even have the disc space for a BTC full node (but could use some older HDD lying around) - my worry is, even after finally having a synced full node running and connected to mSIGNA, the sync process will be stuck somewhere - that's what people seem to report on their github a lot. Alternatively - have you spend from any of these addresses in the past? If so, we can view the script for them on the blockchain. That sounds interesting. Would it tell anything about the derivation path or other wallet properties? How does the script used to send help in my case? Can you guide me through the steps without me exposing my pub keys? In the end it's around 300 bucks that are unaccessible right now. Would be nice to have, but don't want to spend weeks trying to recover them. I'm giving away 0.001 BTC for whoever helps the most to recover these funds. Will add info in OP. I reserve the right to decide at my own discretion who will get the funds - if more people are involved in finding a solution I might split it up. Thanks already for your helpful inpot @o_e_l_e_o . btw, I edited OP to include link to mSIGNA source code. |
|
|
|
Hallo Willi. Das sieht ja ganz interessant aus, gerade eben erst drauf gestoßen. Wieviel kostet denn momentan ein Exahash für einen Tag? Auf https://www.nicehash.com/marketplace steht 0.1EH für 0.234 BTC. https://solochance.com/ gibt mir dafür eine 1/25 Chance. Dh für 5.85 BTC hätten wir eine Gewinnerwartung des Blockrewards von 6.25 BTC (plus Transaction fees oder bleiben die aus?). Also einen positiven Erwartungswert von + 6.84% des Einsatzes (und das ohne die fees die ja eigentlich noch obendrauf kommen sollten)! Wie kann es sein, dass Hashingpower verkauft wird, wenn es +EV ist, diese selbst zu nutzen? Oder hab ich da einen Wurm in meiner Rechnung? Mir ist klar, dass es dennoch vom Glück abhängt, ob man nun einen Block findet oder nicht, aber mir geht es um die positive Gewinnerwartung. Wenn das so korrekt ist, wäre ich gerne für 0.005 für ein paar 24h runs in Folge dabei. |
|
|
|
|
Bump. I noticed I forgot a closing tag for my strike-through, oops. So all items listed in OP are available.
Going to update with some pretty photos tomorrow and will be adding on a few coins: loaded Be Your Own Bank, lealana coin set and graded Moonbits.
|
|
|
|
I have one of these they are HUGE in size, made me laugh when I unwrapped it from the mail, I had no idea. Question: do these coins have a designated BTC denomination for them? The one I have says on the COA that it’s supposed to be loaded with 1btc but I’m not near the coin and don’t remember if it saying 1btc anywhere on the physical coin. Do they come with public addresses and/or COA’s ? Sorry for so many questions, Thank you Correct, they were originally to be all loaded with 1 BTC each I am in the process of contacting original seller to see if they have the addresses/COAs Any update regarding if they do come including COA or not? If they do indeed, my bid for lot 5 is 0.017 Oh and I was wondering if these can be graded despite their unusual size. |
|
|
|
They are certainly not our friends, they are looking out for their interests and lining their pockets but what can we do if they decide to enter Crypto.
Big companies are interested in profit anyway, so let's hope that their entry into the crypto space has positive effects.
Obviously. And usually such statements will soon be followed by the proposal of a digital-dollar or maybe some other idea of a (possibly international) centralized "cryptocurrency". Or they indeed just intend to fill their pockets while at the same time trying to gain the maximum control possible on the market. That said, statements like these usually do have a positive short term effect on the crypto market. Still - it's always scary to see the mega companies such as BlackRock possibly making moves. It usually is not in favour of "the people". |
|
|
|
Ahahaha, funny you come up with this (semi-)scam just now. It's not new at all. I heard about this over one years ago and dismissed it on the spot. So, as others have stated already, web5 is just a pure marketing name. I'd highly recommend to watch this awesome 2-minute summary by fireship: https://www.youtube.com/watch?v=HDZWWFSZUF0Probably all you need to know in there. Personally I am waiting for webXP /s |
|
|
|
I still do have the mSIGNA wallet. It doesn't offer any option to export single private keys. The only private key export option is said BIP32 extended private key.
The problem with the software is, I wasn't able to get it to connect to a node so far. The .pdf I linked to above says it should connect to your own node. Are you running a node? Can you import your seed phrase back in to mSIGNA and regenerate the same wallet with the same addresses? If so, then it is hopefully just a case of finding the right derivation path. But I worry given what is written on that .pdf it is going to be significantly more complicated since it apparently uses an unknown multi-sig arrangement. I may not have made that clear in OP: But I can still access my wallet in mSIGNA. That's not the issue. This is where I got all the public keys and see a few of change funds still on there. The issue is using the exportable keys as described in OP via 1), 2) or 3) to import properly via an other wallet. Also, my wallet is NOT setup as a multisig, just a regular HD wallet. Multisig apparantly was optional. My guess it's only about finding the right derivation path. Wonder if there is any tool to determine which is used by mSIGNA here. Thanks for digging up that old pdf - no info on their derivation path used, though. Seems the derivation path issue was already around in 2017: https://bitcointalk.org/index.php?topic=2144498.msg21524209#msg21524209Probable solutions to my problem- get mSIGMA to connect to a node (I don't have a full node) - find the proper derivation path used by the wallet & import to another wallet |
|
|
|
|
Show Posts
