Dual Core 4

i05ts.png (600×600)Dual Core 4, or DC4, is the newest polyphasic schedule in the Dual Core family. It was a creation of the Polyphasic Discord community. Similar to Dual Core 3, it also has 2 core sleeps of one-cycle length each, with the addition of a fourth nap. The total sleep is 4 hours and 20 minutes, which hovers around the very bare minimum amount for adaptability.

Mechanism

As a typical Dual Core schedule, Dual Core 4 inherits all the characteristics from Segmented sleep; this includes the following:

  • The repartitioning of SWS and REM into respective core sleeps. Both core sleeps provide the most sleep possible around night hours while utilizing the sleep peaks.¬†
  • The last nap around 6 PM intends to provide more alertness.
  • While looking very similar to DC3, the purpose of DC4 is to transition to Uberman sleep. Both core sleeps will eventually be forced to shorten down to 2 20m naps. To prepare for the transition, all sleep blocks on DC4 look equidistant in scheduling to resemble the wake gap between each nap on Uberman; each gap is approximately ~3h40m to 4h.
  • The remaining naps provide REM sleep to keep a healthy balance of homeostatic pressure. The first nap should be teemed with REM sleep, thanks to its position in REM peak. Other naps provide potentially less amount of REM sleep, as well as some NREM2.

Adaptation

Despite looking more “reasonable” than DC3 with an extra nap, there has been no successful adaptation to Dual Core 4 as of now. Similar to E5, it goes to show that adding more segments to a polyphasic schedule may not make things any easier.

DC4 attempts are also extremely rare, let alone successful adaptations. Because both cores only have 1 full sleep cycle, a very daunting adaptation should be expected. 

Cold turkey

There has been a very close success from this adaptation method. The sleeper was in late Stage 4 before quitting medications cold turkey knocked him off the rhythm.

If one would want to attempt DC4, cold turkey method would be ideal; this especially applies to naturally segmented sleepers. 

Gradual adaptation

From Segmented sleep

9aqbe.png (600√ó600)
Segmented
91ef5.png (600√ó600)
DC4

As an alternative, one can transition to DC4 from an adapted Segmented or any Dual Core schedules (bar DC3). The entrained split core sleep habit should enable an easier adaptation to DC4. However, while looking realistic on paper, there has been no success with method, either. 

From Tri Core sleep

ycnjs.png (600√ó600)
Tri Core 1
awxms.png (600√ó600)
DC4 with 3h gap between 2 cores

Transitioning from a Tri Core schedule, like TC1 is also possible. The first core starts at the same time (e.g, 9:30 PM above) to ease the transition process. The wake period from the first to the second core is also 3 hours long just like on TC1. The third core of TC1 now simply breaks down into several short naps. 

While this method looks feasible on paper, no one has been successful at this transition. 

Reverse gradual adaptation

In contrast with gradual adaptation, one can also fall back on DC4 after failing Uberman. The rhythm of 6 sleep blocks of Uberman should align with that of DC4. Notwithstanding, no one has resorted to this method to adapt to DC4, either. 

Difficulty

Dual Core 4’s true difficulty may even be more than that of DC3, because of the extra nap that may stagnate sleep onset. It will likely take longer for all naps on this schedule to stick. The other sleep blocks closely resemble DC3, so this adaptation will be along the lines of E3/Bimaxion, if not more difficult.

SWS and REM wakes during the cores will be intense during stage 3, and extensive alarm setup is a requirement. The sharp repartitioning of sleep stages at first may induce SWS into the 2 afternoon naps, causing a lot of grogginess upon awakening.

With a fourth nap on the schedule, DC4 now has a total of 6 chances for oversleeping each day; the immense sleep pressure can lead to oversleeping in any sleep blocks. 

Alternate Variants

It may be possible to extend a core sleep on DC4. However, doing so will become largely redundant; this may result in the removal of a sleep block. The schedule would then become DC3 to facilitate sleep onset issues.

The wake period between the cores can be shorter, but it is questionable if this would be productive. 

Lifestyle Considerations

The wake gap between each sleep is too small for a lot of real-life activities, with the comprehensive forfeit of social life. While posing a Uberman-rhythm between each sleep and the total sleep appears to be sustainable for an extended period of time, the clumsiness in scheduling just adds to the burdens. DC4 is vastly inferior to DC3, and the transition to Uberman can take several months.

So far, it remains a hypothetical polyphasic schedule that has been far from being fully tested. Notably, no one has adapted to Uberman from this schedule, either.

With all the downsides, DC4 can still have some uses:

uzgzj.png (600√ó600)
DC4 as a less hostile Naptation method
  • Learning to nap in 20m is optimistic with the high number of naps per day. Like E5, it is also a less extreme form of Naptation thanks to 2 core sleeps. Sleepers can choose to start this schedule temporarily as a way to learn the short naps. Then, recover on monophasic, and start a polyphasic attempt anew. This includes Uberman or any other schedules with at least one 20m nap.
  • DC4 may also act as a fallback schedule if Uberman or E5 happens to fail, but no one has pulled this off so far. With everything being mostly hypothetical, there is little to no use in attempting this schedule. Other dual core schedules would be a better choice.
  • During short-term emergency situations (e.g, new parents), it is possible to sleep in shorter chunks if a 3h core is impossible. Having 2 core sleeps of 90m each can help sustain performance with some SWS. A second core is an advantage over E5.¬†

Main author: GeneralNguyen

Page last updated: 16 February 2021