4709 entries in 0.588s
MolokoDesk: ok. uh, where does that happen, just a report from
deedBot?
deedBot:
deedBot BTC available balance: 0.00275000 in wallet 1NTSD9jVvumurTotaW7Crqe5DfRxBrJzqu
deedBot:
deedBot BTC available balance: 0.00275000 in wallet 1NTSD9jVvumurTotaW7Crqe5DfRxBrJzqu
MolokoDesk: we're still trying to break
deedBot, but I think it passes.
deedBot:
deedBot BTC available balance: 0.00275000 in wallet 1NTSD9jVvumurTotaW7Crqe5DfRxBrJzqu
deedBot:
deedBot BTC available balance: 0.00275000 in wallet 1NTSD9jVvumurTotaW7Crqe5DfRxBrJzqu
MolokoDesk: it's likely that
deedBot degrade gracefully. if any process in the chain stops things still get set up for the next bundle.
MolokoDesk: the logic for handing an ;;eauth challenge is already in. when it logs on and identifies to freenode it issues an ;;eauth
deedBot to gribble and picks up any challenge response, decrypts the item and does the ;;everify
MolokoDesk:
deedBot is resonably terse and bulletproof now.
MolokoDesk: (you won't see
deedBot in other chan without an invite or join directive)
MolokoDesk: (ok. I have
deedBot installed to re-start on server reboots or
deedBot terminations, it's home channel is set to #bitcoin-assets)
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=1200 (no pending deeds.)
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=1200 (2 deeds 1201 bytes in next bundle)
deedBot: (switching DEEDBOT_CHAN from #cex-squawk to #bitcoin-assets)
deedBot: DEEDBOT_CHAN=#cex-squawk ERROR_CHAN=MolokoDesk INTERVAL=3600 (no pending deeds.)
deedBot: (switching DEEDBOT_CHAN from #cex-squawk to #bitcoin-assets)
deedBot: DEEDBOT_CHAN=#cex-squawk ERROR_CHAN=MolokoDesk INTERVAL=3600 (no pending deeds.)
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600 (no pending deeds.)
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600 (9 deeds 4005 bytes in next bundle)
assbot:
deedBot/test deed at master RagnarDanneskjold/
deedBot GitHub
assbot:
deedBot/test deed at master RagnarDanneskjold/
deedBot GitHub
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600 (9 deeds 4005 bytes in next bundle)
deedBot:
deedBot BTC available balance: 0.00297000 in wallet 1NTSD9jVvumurTotaW7Crqe5DfRxBrJzqu
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600 (6 deeds 4005 bytes in next bundle)
assbot:
deedbot test 9.26.14 - Pastebin.com
assbot:
deedbot test 9.26.14 - Pastebin.com
deedBot:
deedBot BTC available balance: 0.00297000 in wallet 1NTSD9jVvumurTotaW7Crqe5DfRxBrJzqu
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600 (no pending deeds.)
MolokoDesk:
deedBot is ready for another stress test. if someone wants to /invite
deedBot we can give it a go.
MolokoDesk: oh, are you going to register
deedBot with WoT or should I do that or, leave it indeterminate. I can export the keys and give you a copy.
MolokoDesk: ok. I need to tighten a few things up in
deedBot. It's possible that's going to run into October.
MolokoDesk:
deedBot is sniffing the top block once 60 seconds. if a freakishly fast block mining event happens back to back it could miss the inclusion in the block.
mircea_popescu: MolokoDesk ok. if gribble can grant
deedBot unlimited requests thats the solution. << that's not the solution yet. it wil be the solution once we process a lot of volume. atm the soluition is to queue.
deedBot: rename(,): No such file or directory
deedBot.php LINE 1634 Sat 2014-Sep-27 15:02:16 UTC (6 errors)
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600
MolokoDesk: ok. if gribble can grant
deedBot unlimited requests thats the solution.
MolokoDesk: gribble bans anyone for 5 minutes if they make more than 12 requests in a 60 second interval. that probably happened while
deedBot wasn't voice.
deedBot: rename(,): No such file or directory
deedBot.php LINE 1634 Sat 2014-Sep-27 14:59:57 UTC (3 errors)
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600
deedBot:
deedBot unconfirmed sent: -0.00011000
deedBot:
deedBot BTC available balance: 0.00118000 in wallet 1NTSD9jVvumurTotaW7Crqe5DfRxBrJzqu
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600
MolokoDesk: still wondered what
deedBot actually saw
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600
deedBot:
deedBot BTC available balance: 0.00129000 in wallet 1NTSD9jVvumurTotaW7Crqe5DfRxBrJzqu
MolokoDesk: checking to see if
deedBot meets the "it has to work" criterion.
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600
MolokoDesk: and didn't get an acknowledgement from
deedBot about the first one ... 3WT0JW5
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600
MolokoDesk: this is verbose
deedBot. nothing but a terse summary of what it decided about the contract in your pastebin bundle at the beginning, and an announcement of where it publishes the hourly bundles will show eventually/soon/next
punkman: best to minimize the number of lines
deedbot prints
punkman: ;;rate MolokoDesk 1 made
deedbot deedBot:
deedBot unconfirmed sent: -0.00011000
deedBot:
deedBot BTC available balance: 0.00140000 in wallet 1NTSD9jVvumurTotaW7Crqe5DfRxBrJzqu
MolokoDesk:
deedBot needs to be.. ok. yeah, told that it's now operating in this channel using .dump
deedBot: (switching DEEDBOT_CHAN from #cex-squawk to #bitcoin-assets)
deedBot: Undefined offset: 2
deedBot.php LINE 1860 Sat 2014-Sep-27 08:31:53 UTC (1 errors)
deedBot: DEEDBOT_CHAN=#cex-squawk ERROR_CHAN=MolokoDesk INTERVAL=3600
MolokoDesk: ok. one scenario I was talking about a few minutes ago was someone vandalizes the bot and has their rating lowered below access threshold, but they're still trusted by
deedBot and
deedBot keeps getting vandalized.
assbot:
deedbot test 9.26.14 - Pastebin.com