14:00:41 [discord] : why is it when i try to miine with my gpu it crashes???? amd radeon rx560 4gb ddr5... 15:31:21 Hi fluffypony, I was sent here from Telegram in reference to the MyMonero project. Is this yours and are you able to answer some questions about it? I'm trying to incorporate Monero into an existing JavaScript project and it seems like your library would be the ideal (possibly only) solution! I've already incorporated BTC and BCH, and have spent a 15:31:22 lot of time with Ethereum and smart contracts, so we could probably skip some of the basics. 15:32:16 monican_agent: you might have better luck in the #mymonero channel :) 15:32:32 what are you trying to do though? 15:33:35 asymptotically I need to be able to: create addresses, including private keys, preferably using a master derivation one (like HD wallets) 15:33:58 asymptotically Then I need to be able to create raw transactions, and finally sign them. 15:34:36 asymptotically The constraint is that I have to be able to do this using JavaScript only (no dependence on RPC wallet or daemon or external API) 15:35:09 i think you need the daemon (or at least a copy of the blockchain) to be able to create a transaction though 15:35:38 you might want to look into https://github.com/moneroexamples/openmonero 15:38:56 asymptotically If I understand correctly, I'd need to gather transaction outputs in order to generate a new transaction, is that correct? Let's say I'll have access to the transactions somehow (e.g. stored in an offline database). Now I need to use that information to generate a new transaction and then sign it. At some point in the future, that 15:38:56 transaction may be posted -- for this I can use RPC, but for the generation and signing of the tx, I can't. 15:40:27 asymptotically I've looked at OpenMonero but I don't think it's JavaScript, is it? Am I looking in the wrong place maybe? 15:41:11 it's the backend to a wallet service like mymonero, where the server does the hard work (scanning for transactions) but the user still keeps their keys 15:41:15 are you able to use WebAssembly? i think you'd want to use exactly the same code to generate your transactions so that you don't accidentally make them stick out 15:41:25 asymptotically I'd need to implement this for Node.js 15:42:10 asymptotically I believe that Node can use WASM. When I "require" the MyMonero library it reports that WASM is available. 15:42:38 asymptotically MyMonero seems okay so far but beyond simply including it I can't find any information on actually using it. 15:43:37 endogenic, ^^ 15:44:23 There are some unit tests where parameters are listed but I haven't a clue as to what most of them do. 15:45:30 monican_agent, you wanna connect with endogenic . For details on what he/they can offer, checkout his recent chat on monerotalk. https://www.monerotalk.live/paul-shapiro-mymonero 15:45:57 which was awesome btw endogenic! :) 15:47:00 gingeropolous Perfect. Doing that right now. Thanks! 15:51:52 For reference, here's the library I'm looking at: https://github.com/mymonero/mymonero-core-js 15:52:15 Seems like it'd be perfect if I can just figure out how to use it properly. 16:02:50 hello, i'm new to monero. Now i have synced daemon. and i want to try to configure solomining. what is the best option to do that? should i use rpc bind? or its unnesessary for mining blocks? 16:05:46 You do not need anything extra. Just run start_mining ADDRESS NTHREADS. 16:07:56 monican_agent: https://github.com/moneromooo-monero/monero-wallet-generator is probably a good introduction, it's based on mymonero source (from a few years back) and creates keys/addresses. 16:08:37 You'd likely not want to use it, just as a starting point for how to use the current mymonero source. 16:09:17 moneromooo: but i want to get some hashrate from outside. (not shure now, directly or through xmrig-proxy). at this moment i think i need something like 16:09:38 monerod --max-concurrency=2 --public-node --data-dir=/root/.bitmonero --prep-blocks-threads=4 --p2p-bind-ip=0.0.0.0 --p2p-bind-port=18080 --rpc-bind-port=18081 --rpc-bind-ip=127.0.0.1 --rpc-login user:password --confirm-external-bind --start-mining AdDrEsS 16:10:02 Sorry I thought you said solo mining. I misread then. 16:10:34 might be solo but wants to point multiple rigs at it i presume 16:10:40 maybe its not solo, but , i mean... many workers to one address 16:10:53 Odd definition if solo but OK ^_^ 16:11:38 Some pool miners support a daemon+tcp scheme. 16:11:53 Not sure it's appropriate for many miners though. 16:13:30 at this time, question is - what is the right syntax for command line to restart daemon. is my example contains something unneeded or something missing? 16:14:18 --public-node and --rpc-login seem contradictory. 16:15:02 Especially with --rpc-bind-ip=127.0.0.1, unless you have some proxy from outside. 16:15:17 Otherwise it looks sensible. 16:15:24 do i need rpc for mining? 16:15:37 moneromooo Thanks. I'd actually come across this implementation in my search. I was a little intimidated by the size of the code but I'll have another look. 16:15:41 If you want to start/stop it from RPC, yes. 16:17:15 monerod --max-concurrency=2 --public-node --data-dir=/root/.bitmonero --prep-blocks-threads=4 --p2p-bind-ip=0.0.0.0 --p2p-bind-port=18080 --start-mining AdDrEsS 16:17:35 mining port is 18080. am i right? 16:17:40 I wonder if we should publish a sample monerod config file for running on a smartphone 16:17:50 enable pruning, limit number of peers, limit bandwidth 16:18:57 There is no mining port. 16:19:03 hyc: :) maybe add some code to turn bluetooth on and syncing over it with nearby nodes? :) 16:19:14 That'd be nice. 16:19:43 syncing over bluetooth native? hmm. I'd consider just using bluetooth's IP layer and not worrying about it 16:20:02 BTW, with your new line, you're allowing anyone to mine on *their* address. 16:20:19 If you want to make your node both a public node and mine for you, add --restricted-rpc. 16:20:29 moneromooo: so as there is no mining port , then i need some proxy on the same server? or i need to add some option for mining port? 16:20:51 No idea what you're asking here. 16:21:22 What would a mining port do ? If it's "you submit new blocks to it", then it's the RPC port. 16:21:37 And it's 18081 by default. 16:21:48 you would want to set both a rpc-port and restricted-rpc-port and make them separate 16:22:16 moneromooo: there's a usability issue here, we need to add a feature to specify the rpc-restricted-bind-ip 16:22:41 so that the rpc-bind-ip can still be set to 127.0.0.1 and the rpc-restricted-bind-ip can be set to 0.0.0.0 (or something) 16:22:57 obviously 0.0.0.0 will conflict address-in-use with any other IP 16:24:12 i understand,that i should read 0.0.0.0 as "external ip" 16:24:17 right 16:24:42 I'd consider changing these options to -bind-addr and specify bot address and port in one option. 16:25:06 and allow specifying them multiple times, in case of a machine with multiple public addresses 16:25:28 hm, this is probably more of a -dev topic, sorry 16:25:33 what is zmq? 16:25:39 18082 16:25:52 what it used for? 16:26:14 it's supposed to be the next generation RPC protocol, supposed to be more efficient 16:26:21 and more widely used 16:26:30 ahh, ok, thanks 16:26:33 lookup ZeroMQ 16:37:14 is that ok, or there is mistakes? (i want to avoid downtime while restarting node to fix params) 16:37:16 monerod --max-concurrency=2 --public-node --data-dir=/root/.bitmonero --prep-blocks-threads=4 --p2p-bind-ip=11.22.33.44 --p2p-bind-port=18080 --rpc-bind-port=18081 --rpc-bind-ip=127.0.0.1 --rpc-login user:password --confirm-external-bind --start-mining AdDrEsS --restricted-rpc --rpc-restricted-bind-port=18888 --rpc-restricted-bind-ip=11.22.33.44 (--confirm-external-bind will be added if daemon asks it) 16:40:31 < moneromooo> --public-node and --rpc-login seem contradictory. 16:42:13 so, for mining i dont need rpc-login (as i'm not planning to stop it) 16:43:51 if you use --start-mining do you need the unrestricted rpc at all? 16:44:35 not shure, i think it will bring me the port for hashrate from outside 16:46:12 sorry , something happens, need to check ups. AFK for about 1 or 2 hours, i will read your replys later. thanks 16:48:00 currently there is no such monerod option for --rpc-restricted-bind-ip - this is a missing feature 16:54:47 are mix-ins still a thing? 17:00:52 Yes. 18:18:48 yes but now we call them mix-outs 18:25:54 cuz mixons are best reserved for ice cream 18:26:00 mixins* 18:43:23 in simple terms what is the difference between the daemon rpc and wallet rpc? 18:43:55 or rather what is their function 18:44:35 basically i installed monerod for stagenet as i'm tetsing and i'm trying to wrap my head around what does what 18:45:01 The daemon RPC controls the daemon. The wallet RPC controls the wallet. If you're asking what's the difference between the node daemon and the wallet daemon, the node keeps track of the blockchain, the wallet daemon keeps track of wallets. 18:45:48 makes sense, ty 18:46:24 can i fully use the walletrpc while still syncing? 18:46:35 Yes. 18:46:41 sweet 18:46:51 i wanna say no though 18:47:16 the json-rpc http server doesnt start listening until the wallet has synced afaik 18:47:22 it seems that it started re-syncing when i switched to stagenet and it's a lot slower, which is why i wonder 18:47:34 ah 18:48:09 It'll certainly be much slower till the dewmon's synced, yes. 18:48:42 Access to the db is currently guarded by a main mutex even when not technically needed. 18:49:07 thats my experience with it, i remember fucking around for an hour or so wondering why the FUCK isnt my wallet-rpc listening until i just waited patiently to see the "server listening on 0.0.0.0:18081" in the wallet-rpc 18:49:40 That's only till it's refreshed from the node. 18:49:59 true, daemon sync =/= wallet sync so there's that 18:50:28 monerod 15087 monero 10u IPv4 229833 0t0 TCP *:38080 (LISTEN) 18:50:28 monerod 15087 monero 14u IPv4 228884 0t0 TCP *:18081 (LISTEN) 18:50:45 you have the mainnet and the stagenet both on 18:50:52 likely explains the slowness 18:50:54 oh, that was not intentional 18:51:00 Same PID. 18:51:11 also weird, iunno lol 18:51:26 lol 18:51:27 It's the same daemon, just using non defualt ports. 18:51:30 great start 18:51:59 https://bpaste.net/OW5Q 18:57:32 took out port argument to prevent more confusion lol 19:01:01 https://www.reddit.com/r/Monero/comments/fdhtqh/request_for_proofreading_zero_to_monero_second/ 19:04:44 i hope you're not suggesting that as material to get started lol 19:05:34 sorry not directed at you 19:24:26 is there a public stagenet daemon i can use instead of waiting for sync? 19:24:39 and will it allow me to create wallets and subaddresses and all that stuff 19:25:25 I believe xmr.to might have one. But testing using random stranger's servers is often a bad idea since it introduces uncontrollable behaviour. 19:25:47 The wallet does not need the node to create wallets/subaddresses. 19:27:47 i'm considering using https://github.com/monero-ecosystem/monero-javascript and in its sample code it shows opening a wallet 'on the server' 19:27:53 that sounds like something i'd want 19:29:26 would help if it showed me how to create one to begin with lol 19:30:25 Stealthy: https://www.reddit.com/r/Monero/comments/f5ncyo/cli_trouble/fi1tq61 19:31:29 not exactly what you want tho 19:31:29 yea i should probably start reading to get the basic picture 19:32:23 Stealthy you can find a stagenet remote node here: https://community.xmr.to/nodes.html but as mentioned not necessarily relevant for you 19:32:46 ty 19:38:27 that helped @UkoeHB_ 19:48:16 method not found, i guess this api lib is just incorrect 19:48:37 the others are 2-4 years old lol 19:49:03 anyone recommend a nodejs lib 19:49:59 all i want to do is create a wallet, create temporary subaddresses for endusers and monitor transactions 19:50:38 You can check out the functional_tests directory, they exercise those RPC. 19:51:46 bunch of python 19:52:30 are you suggesting i should reverse engineer those and utilize json calls directly :P 19:53:37 Kinda :) 19:54:09 The python calls are direct raw calls to the RPC. 19:54:44 maybe the way to go 19:58:30 Stealthy: https://web.getmonero.org/resources/developer-guides/wallet-rpc.html 19:58:43 a little out of date but it shows what you want :D 19:59:24 yep, think that's the route to go 20:02:33 fucking firefox calling home again, and I've got all telemetry and stuff disabled. 20:02:44 And they claim to be pro privacy, the little shitty cunts., 20:02:49 * moneromooo rages 20:03:04 I so hope someone makes a good browser I can switch to soon... 20:03:06 big marketing image 20:03:19 the moment they started with their dumbass 'suggestions' was the first bad omen 20:04:03 do an rms and get web pages emailed to you that you view in emacs gnus 20:04:32 calling home? 20:05:01 they have a support article that tells you how to disable it iirc 20:05:19 you disable it and then the next update adds something new to disable 20:05:34 wish javascript wasnt required for 90% of the web 20:06:00 and all those video codecs and what not 20:06:06 then you can make a secure browser 20:06:51 moneromooo: qutebrowser is quite minimal with no telemetry, but you have to like vim keybindings 20:06:56 wen mooobrowser 20:07:25 mooozilla 20:07:31 Big beasts. Firefox's source was hard to get into last I looked :/ 20:08:06 you can build chromium 20:08:17 I'm not going to trust that. 20:08:25 rid of all the crap 20:08:30 sudo apt install links 20:08:41 links getmonero.org 20:08:48 That's text, wich is not always enough. 20:09:13 reading the dirty sites isn't the same as watching the dirty sites ;) 20:09:17 there's eww in emacs which is a worst of both worlds :D 20:09:25 * camthegeek finds his way out. 20:09:35 they should enforce no remote resources for images and what not, no more cookies 20:09:38 'they' 20:09:57 getting retarded all these long fingers everywhere 20:32:57 "create_wallet" method not found ok 20:34:06 Stealthy: what version are you using? 20:34:10 create_wallet should exist 20:34:12 https://github.com/monero-project/monero/blob/3b224bb99db27971f4fc02b77390340c54bb6c99/utils/python-rpc/framework/wallet.py#L130 20:35:09 im guessing that its monerod running on that port not the wallet rpc? 20:35:41 i guess its a separate service that i should run 20:36:12 monero-wallet-rpc? yes 20:36:30 you probably don't need to call create_wallet. you start the wallet-rpc server with one that already exists, and then just make a subaddress (create_address) for each user 20:37:01 that could be an alternative 20:37:21 i guess i don't really need to my app to create one for me 20:37:34 for my* 21:14:28 languages: [ German', English', Spanish', French', .... 21:14:31 there we go 21:26:57 lol now the xmr.to stagenet faucet is throwing an internal server error 21:28:07 ok, tomorrow 21:32:02 you need stagenet coins? paste address 21:32:45 address: '47TdXb9UVdV525NESDwEYqY8sqs3GBNZb1ZMLzTg364qbj15ZQGc4qE3GqvprCPVCAPrKJxmuJhLv6Z4DPGCv1EUD1Tuhjm', 21:32:47 stagenet yea 21:32:52 that's a mainnet address 21:33:06 lol did i mess up again 21:33:16 that might explain the error :) 21:33:28 the wallet rpc is set to connect to local instance of monerod which has stagenet=1 21:33:48 you also need to run the wallet with --stagenet 21:33:48 then i used 'create_wallet' 21:33:58 oh.. well that was dumb xD 21:34:27 a bit surprised the wallet doesn't complain about that, actually 21:34:53 note that if you run it with --stagenet, it will use the 3808x ports by default, so you don't need to also specify those 21:35:34 configured it to use a specific port because it was giving me a headache 21:35:59 55FpdJEotvYcqULvajajkoNEoWZnmNKJTbTPzbsHcuUtRNMgoGETAo6GkqazQThNDQTQszcbRbzuxCqKQAdgk1j9C2R9i7o 21:36:31 community.xmr.to server throws an internal server error so cant test any address 21:37:00 i'll send you a few 21:37:29 awesome, thank you, then i can continue tonight :) 21:39:09 sent 21:40:00 how fast do you think stagenet will confirm 21:40:26 the big question is, make coffee or later xD 21:41:06 make coffee :) 21:41:16 it varies, you can `start_mining` to speed it up 21:41:18 wise 21:41:41 thats the cli right? it can mine? 21:42:08 the daemon does the mining, you can use the command in the wallet or directly in the daemon (but have to specify address explicitly then) 21:43:37 so in my case i'd open_wallet and start_mining 21:44:04 you would. this tx is confirmed now though 21:44:13 ah 21:46:31 result: { 21:46:31 balance: 0, 21:46:32 blocks_to_unlock: 0, 21:46:32 multisig_import_needed: false, 21:46:32 unlocked_balance: 0 21:46:32 } 21:46:36 i must be doing something stupid 21:48:04 see what i don't get is, when i call open_wallet, does the rpc server, like.. maintain a session or something? when i call get_address or getbalance does it know i want info for the previously opened wallet? 21:48:36 i pass account_index 0 21:48:47 been a while since i used rpc, but IIRC, yes 21:49:15 what's get_height say? 21:49:31 our tx is in block 530387 21:50:35 id: '84a3cbd5-5231-4562-b069-695c127effb7', 21:50:35 jsonrpc: '2.0', 21:50:36 result: { height: 10001 } 21:50:49 lol. yeah that's only a few years behind 21:50:54 what's the daemon's get_height say? 21:51:01 oh is it because my monerod is not done yet 21:51:30 82% 21:52:16 you might also have to call the `refresh` endpoint in the wallet once that's done 21:52:51 aah i see 21:54:58 things are starting to make sense lol 23:33:04 How to buy Monero ? 23:35:36 romainpradier: there are a ton of resources for learning how to get your hands on some Monero. Please read through some of these Reddit posts: https://www.reddit.com/r/Monero/search?q=buy&restrict_sr=1