oipwg / trinity Goto Github PK

When user changes password, success message doesn't clear.

If user has any profiles, please select one

Trying to get bitcoin balance , too many times quickly resolves in 429 - Too Many Request.

Maybe, store the last BTC balance in DB or State?

Tried to start an auto rent with 0.001% of network, it went into a spastic loop

After i killed the backend i was able to finally see the message it was trying to put into the Messages area:
"In order to mine with the given token of .001 must increase your percent to 36.61% , and try renting again."

Terminal reads:

NetworkhashrateFlo:  0.0876173328384 MarketPriceMrrScrypt:  0.01620375 Duration:  3 Percent:  0.15 PriceBtcUsd:  9760.905 Margin:  0.05 ProfitReinvestmentRate:  0.05
EstRentalBudgetPerCycleUSD: 7.354846581693375
msg: undefined
MSG:  {
  update: true,
  client: '7.35',
  db: 'dailyBudget',
  dailyBudget: '7.35'
}
err: TypeError: Cannot read property '0' of undefined
    at new Timer (/Volumes/2TBT5/GitHub/trinity/backend/helpers/timer.js:8:48)
    at Emitter.<anonymous> (/Volumes/2TBT5/GitHub/trinity/backend/routes/rent.js:251:13)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
POST /rent 500 1036.737 ms - 10

I receive the following error after
npm install then npm start:

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node ./bin/www
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Is this an issue with the script?

I had a rental going from one trinity account.

i registered a new one and did not import my wallet so it generated a new one. i then made a new set of API keys in my same MRR account. I then started a new rental, and they all are using the same worker address as the previous rental was.

When user Auth's with coinbase and is redirected back. The page keeps re-rendering.

If the switch is turned off and then back on, it shouldn’t do the same the rental - it should check how much of the network it is actually mining and if there’s a difference between that and how much the user wants to be mining, rent more (if doing so would meet minimums, if not, do nothing)