 Show Posts
|
|
Pages: [1]
|
I'm struggling with a contract I deployed some time ago https://github.com/ethereum/dapp-bin/blob/master/wallet/wallet.sol and have come to a brick wall. I am trying to use MyEtherWallet to interact with the contract. One of my MetaMask accounts is using the private key of an account that is a signer on this contract and is linked to MEW. I believe the function I want to call in order to retrieve ETH from this contract is execute: // Outside-visible transact entry point. Executes transaction immediately if below daily spend limit.
// If not, goes into multisig process. We provide a hash on return to allow the sender to provide
// shortcuts for the other confirmations (allowing them to avoid replicating the _to, _value
// and _data arguments). They still get the option of using them if they want, anyways.
function execute(address _to, uint _value, bytes _data) external onlyowner returns (bytes32 _r) {
// first, take the opportunity to check that we're under the daily limit.
if (underLimit(_value)) {
SingleTransact(msg.sender, _value, _to, _data);
// yes - just execute the call.
require(_to.call.value(_value)(_data));
return 0;
}
// determine our operation hash.
_r = sha3(msg.data, block.number);
if (!confirm(_r) && m_txs[_r].to == 0) {
m_txs[_r].to = _to;
m_txs[_r].value = _value;
m_txs[_r].data = _data;
ConfirmationNeeded(_r, msg.sender, _value, _to, _data);
}
}
However I'm not sure what the input values should be. MEW gives me the _to address (my destination wallet), _value (which I think is how much I want to send?), _bytes (I'm completely lost here, I tried to use letters and numbers, found that a hex was acceptable e.g. 0x), and finally "Value in ETH". Am I on the right track here? I can't find much documentation on this contract despite it being built by one of the Eth Devs a few years back. |
|
|
|
|
So I am looking in to starting my full node. I have the latest Litecoin zip file on a FAT32 USB drive. When starting my node, I only see 8 connections. It sounds as if I have to open up inbound connections to the node via port forwarding aka STATIC NAT.
Before I do this I'm curious what the security implications of this are. How secure is the node service? Is there a github repository I can look at for known vulnerabilities, or? My concern is by doing this it could open up my home internal network to outside attackers. I unfortunately don't have the option to put this into a DMZ of sorts.
|
|
|
|
|
Excellent, that fixed it! To fix, I had to do the following to get rid of the RED LED and ECONNREFUSED message:
1. Download new Apollo OS image (check first page in this thread for link to MEGA download)
2. Unzip .img file from the download
3. Used RaspberryPi Imager (I had it handy, works great for imaging MicroSD cards) to point to the .img file and my MicroSD card inserted in a USB to SD card adapter
4. Inserted MicroSD card back into Apollo miner
5. Configured my laptop to act as a DHCP server for the miner, verified it had an IP address, and logged in
6. Did first startup stuff like enter pool info and browser password
7. Set up wifi on miner
8. Logged in to miner via SSH and issued 'sudo ifdown eth0' to turn off ethernet
9. Restarted mining process
10. Mining!
Thanks for the help figuring this out. Super happy that it was something simple and hopefully this will help someone else in the future.
|
|
|
|
Hey all,
I just bought a Futurebit Apollo (< 1 week ago) and had it running fine connected via ethernet. My wife complained it was "too loud" where it was... so I logged in, powered it down, flipped the PSU I/O button to off, and started moving it to another room. Powering it back on, it connected to the wifi no problem but would not start. The LED on the front is a solid RED. I can SSH/HTTP to the device without issue. It does respond and is online.
After digging through the /var/log/syslog entries it looks like it is receiving the "Error: connect ECONNREFUSED 127.0.0.1" message which seems to have only been posted here once before. I validated that yes, my pool information had not changed, but tried to delete/re-enter it just for testing. No go. The miner refuses to start.
The beginning of this thread indicates a RED LED on the miner could be a hardware fault, or something to do with a power supply not providing the proper voltages? I noticed the PSU had an LED indicator as well that remains dark even though it provides power enough to boot the system.
Am I completely fucked at this point or do I need a new power supply?
Out of curiosity - move it back to where you had it originally and see if it works - if so, then miner is fine and its the wifi most likely that is keeping it from mining. I should have mentioned - I did try this. Same power port on my surge protector, same ethernet cable used before. Same red LED on the miner and no LED on the PSU. maybe corrupt sd card - were you running the node version? and if so, did you go into the gui and shut down the node prior to powering it off? While I did buy the Full Package, I didn't opt for the Full Node as I thought I could just buy a flash drive off of Newegg later. So I was not running the Node option. I'm not sure how the MicroSD card could become corrupt moving it from room to room, but at this point I'll try anything to get it to work again. Will report back once I dd my card with the latest version of Apollo OS and try again... |
|
|
|
Hey all,
I just bought a Futurebit Apollo (< 1 week ago) and had it running fine connected via ethernet. My wife complained it was "too loud" where it was... so I logged in, powered it down, flipped the PSU I/O button to off, and started moving it to another room. Powering it back on, it connected to the wifi no problem but would not start. The LED on the front is a solid RED. I can SSH/HTTP to the device without issue. It does respond and is online.
After digging through the /var/log/syslog entries it looks like it is receiving the "Error: connect ECONNREFUSED 127.0.0.1" message which seems to have only been posted here once before. I validated that yes, my pool information had not changed, but tried to delete/re-enter it just for testing. No go. The miner refuses to start.
The beginning of this thread indicates a RED LED on the miner could be a hardware fault, or something to do with a power supply not providing the proper voltages? I noticed the PSU had an LED indicator as well that remains dark even though it provides power enough to boot the system.
Am I completely fucked at this point or do I need a new power supply?
Out of curiosity - move it back to where you had it originally and see if it works - if so, then miner is fine and its the wifi most likely that is keeping it from mining. I should have mentioned - I did try this. Same power port on my surge protector, same ethernet cable used before. Same red LED on the miner and no LED on the PSU. |
|
|
|
|
Hey all,
I just bought a Futurebit Apollo (< 1 week ago) and had it running fine connected via ethernet. My wife complained it was "too loud" where it was... so I logged in, powered it down, flipped the PSU I/O button to off, and started moving it to another room. Powering it back on, it connected to the wifi no problem but would not start. The LED on the front is a solid RED. I can SSH/HTTP to the device without issue. It does respond and is online.
After digging through the /var/log/syslog entries it looks like it is receiving the "Error: connect ECONNREFUSED 127.0.0.1" message which seems to have only been posted here once before. I validated that yes, my pool information had not changed, but tried to delete/re-enter it just for testing. No go. The miner refuses to start.
The beginning of this thread indicates a RED LED on the miner could be a hardware fault, or something to do with a power supply not providing the proper voltages? I noticed the PSU had an LED indicator as well that remains dark even though it provides power enough to boot the system.
Am I completely fucked at this point or do I need a new power supply?
|
|
|
|
|
